I just ran into an issue that is going to make my artists crazy. It goes like this:
When an artist finishes a task, he changes the status to Closed. The task then disappears from his list of To Dos, unless he clicks "Include Closed Tasks."
I use a list of all Closed tasks to see what needs to be billed. Because sometimes a single project might have many tasks, I need a way to keep track of which tasks I have already billed, and which ones are new to my to-bill list. Therefore, I created a new Task Status called "Billed." After billing, I change the task status to this.
Enter the problem. Changing the status from Closed to Billed causes the task to reappear on the artists' To Do lists. This makes them cranky. Cranky artists are to be avoided at all costs.
So here, at last, is my question: Is there any way to make custom Task Statuses mimic the built-in Closed status, so that items marked "Billed" would be listed (or not listed) the same as regular Closed tasks?
I haven't found the solution I want (different levels of Closed-ness), but here is a solution I found that is working for the meanwhile (in case anyone cares):
Instead of artists marking their projects Closed, I am having them mark them Ready To Bill, a new status I just created. I then bill from that list and mark the projects closed once the billing is done. It isn't a perfect solution because the tasks still stay on the artists To Do lists until I have billed them, but it's better than batting tasks around.
I'd still love to know if I can have several task statuses that all function like Closed.
I think what you're looking for is similar to what I'd like--a way to use filters to exclude tasks. For instance, if I want to sort on priority but not see all the low priority items, an exclude filter would let me do that. Maybe it's a checkbox next to each filter pulldown to change the function from include to exclude.
Regarding modifying the attributes and triggers for a customized task status, unfortunately there is not a way to do this right now. The closed status is somewhat unique in nature. Regarding excluding items, we do have customized selection of items within drop downs on our list of features to develop. Here is a quick screenshot:
When this is complete you will be able to create customized task filters that include or exclude certain items so that you only see what you are looking for. In the example above someone could create a task filter that includes everything except for "Ready to Bill". The task counts and daily email would still count the tasks until they are closed, but at least you would be able to filter around the tasks.
We do have plans to add additional flexibility into invoicing so that you can âinvoice by moduleâ or âinclude detailed task informationâ, etc. but we do not have plans to mark individual time entries as billed. The flexibility should help connect the time data with the invoice in greater ways. We currently do this with reports, but it has come up enough in support that we plan to layer in more invoicing flexibility.
When we first developed Intervals (circa 2003) as an internal tool it included the ability to mark tasks as billed. Our experience doing this convinced us it was the wrong way to go for us. Intervals is flexible and task status can used for this as described above. For our workflow the problem was that our tasks are very volatile with a lot of close, reopen, work on it more, close again, etc. and the rigidity of locking time as billed created additional work. Also, marking time chunks or tasks as billed introduces scenarios that can be complex to navigate:
I have a situation similar to LauraEDG which was never really answered here.
After a resource completes a task, it's changed to "close and verify". When I review it and see it's acceptable for client review, I'll change it to "client review". Then when I hear back from the client, I'll close the task.
The issue is that during either of those statuses, it still shows as as an open task to the resource in their e-mails, and as overdue task on the overdue task list.
Is it possible to tweak this so that the resources do not see these as open tasks?
How about automatically closing tasks that are in "client review" within x number of days of changing to client review?
1 to 10 of 10
Comments are closed.
For more Intervals help documentation, please visit help.myintervals.com