Multi-stage ticket closure
Page: 1, 2
Recent posts in this topic
A workflow for ticket closure would be nice that globally enables multiple ticket status'. For example:
Ticket Open > Ticket Closed > Ticket Closed and Verified
Ticket Open > Ticket Closed > Ticket Closed and Verified
I second this idea! This would be a very nice feature to have. Right now we are using categories to keep track of the ticket flow.
Our current ticket flow looks like this: Open -> In progress -> Waiting Review -> Closed, but it's extra work to remember to move the tickets to the right categories, and you can't see all the active tickets on one page. It should be nice if the tickets were grouped based on their status.
Our current ticket flow looks like this: Open -> In progress -> Waiting Review -> Closed, but it's extra work to remember to move the tickets to the right categories, and you can't see all the active tickets on one page. It should be nice if the tickets were grouped based on their status.
I'd also like to see (could be handled in status) task and milestone status including:
Tracking - on track
Blocked - Blocked task (a task that is temporarily blocked by lack of information, completion of another task, etc..)
Frozen - Frozen Task (a task that cannot be taken further)
Completed - a variant of closed
Non-Problem - a variant of closed
Tracking - on track
Blocked - Blocked task (a task that is temporarily blocked by lack of information, completion of another task, etc..)
Frozen - Frozen Task (a task that cannot be taken further)
Completed - a variant of closed
Non-Problem - a variant of closed
andrewCharron
on Feb 7. 2008. 1:40 pm
Or maybe a setting in the admin panel allowing you to specify your own status'? Maybe someone should look into a modification.
Ditto: my previous suggestion was multiple authorities to close ticket: assignee can close, but "manager" (we don't really have that-- "project lead" or such-- must review and do final close.
What we tend to get is over-zealous project assignees closing tickets without even knowing the full extent of the ticket (hello Rudy!).
What we tend to get is over-zealous project assignees closing tickets without even knowing the full extent of the ticket (hello Rudy!).
kthomas, that yeah would be a great idea, it would really make the ticket system powerful! Maybe we can get these ideas included with version 1.1?
isaiah,
I don't think it's on the 1.1 horizon. Just wanted to be "squeeky wheel" here and on a few other issues...
I don't think it's on the 1.1 horizon. Just wanted to be "squeeky wheel" here and on a few other issues...
Ilija Studen
on Mar 24. 2008. 9:16 am
isaiah:Any chance we will get this added to 1.1?
This feature is not present in v1.1.
Just a though I had yesterday regarding this feature - would it make any difference if only person marked as responsible can close ticket? This way you can set multiple assignees who can work on a ticket, but only one of them is responsible for verifying if ticket is really done and can mark it as completed.
activeCollab team member
