Everyday we get a little closer to starting this piece of work... but we're not there yet.  We know it would add value so we won't forget!

Daryl voted for this

Great suggestion Ryan.  Though we hadn't uncovered this use case (thanks for doing so) we have been thinking bout document management (photos and docs) for some time.  Its quite a big piece of work though and we don't yet have the right software infrastructure in place to execute the plan. Part of the trick to all of this is to build the capability without increasing the complexity of use - its an ongoing struggle to find the right balance.

Hi Carol, as you'll see Ryan has also asked for an 'on the fly' task so I've added your vote to that suggestion.

As usual you're on the money Ryan.  When we moved from the old Scheduler to the new one we lost some functionality in the form of the resources view.  Its always been our intent to re-instate this functionality and its in our development plans for later this year (hopefully).

How would it be if we were to show resource workloads in a calendar format for today, tomorrow and this week?  

One further thought we've had is that this view may also be able to be used for ordering of tasks so that job(task) cards can be printed in the correct order.  This might allow us to merge the resources and queue views.

Another good idea Ryan.  The job cards area is one we've been looking at again over the past few weeks.  Though we've yet to settle on the best approach to this going forward, its definitely on our minds (well Di our BA is definitely thinking about it :-)).  We're not sure yet when this will be worked on but the change from job based scheduling to task based scheduling means we need to look at it again. Watch this space.

Great idea Ryan.  Its also one we've heard from others.  Its unlikely that this suggestion will make it into the first release of the mobile offline app but its certainly on our radar for a follow-up release.

On review we've decided that for the moment we will leave this function as it is.  The reason for this is that there is some benefit to allowing JobFlow to update the customer details in Xero.  These benefits are:

• If a JobFlow customer  decides to move to Xero from another package their Xero customer list gets built up automatically (ie on invoice creation JobFlow creates a customer in Xero if one doesn't exist already)
• We believe that our customers (admins) spend more time in JobFlow than in Xero so its likely that they will be updating customer information (notes) in JobFlow in preference to Xero.

What we will do is be more clear with customers about the behaviour of JobFlow though and we've already taken the step of updating our Xero documentation so that this is clearly pointed out.