History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: CHD-567
Type: New Feature New Feature
Status: Open Open
Assignee: Unassigned
Reporter: Joe Geck
Votes: 6
Watchers: 1
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerberus Helpdesk

[Tasks] Couple of new features to support two way ticket / task integration

Created: 11/Mar/08 04:57 PM   Updated: 01/Aug/09 09:09 PM
Fix Version/s: Sea of 1000 Wishes

Original Estimate: 4 hours Remaining Estimate: 4 hours Time Spent: Unknown
Issue Links:
Related To
This issue is related to:
CHD-1169 Allow View Of Number of Tasks Still N... Resolved
 

Value: 2 - Significant Value


 Description   
Summary:
http://www.cerb4.com/forums/showthread.php?t=676

I've been trying to take advantage of the task stuff, but it's a little cumbersome. I generally add 1 or more tasks based off a ticket, close the ticket, then work on the tasks and hopefully remember to reply to the ticket when I've finished the last one.

It would be much nicer if the tickets and tasks were a bit more two way. Specifically, I'd like to do the following:

1) Notify the ticket owner when a particular task is complete
2) Set a ticket to "closed pending task completion"
3) Automatically close the ticket (with a message) when the final task is complete

Also, it would be awesome if I could highlight some text from a ticket and convert it to a task with one click. I don't use any task fields except the Title, which makes it pretty easy to ask for something like that.

 All   Comments   Work Log   Change History      Sort Order:
Comment by Matt Shields [07/May/08 10:38 AM]
I would like to see the ability to add tasks independent of tickets. I should have to have a ticket to create a task and assign it to someone.

Comment by Dan Hildebrandt [WGM] [08/Jul/08 03:16 PM]
Jeff:

We definitely want notifications on new task assignments (though it's also the point of Seer, it's fine in email for now)
And that other task said things like non-ticket tasks and such too, which we talked about yesterday

Comment by Joe Geck [08/Apr/09 08:52 PM]
Some of the comments in CHD-1169 match up with the description in CHD-567, e.g. the idea of not fully closing a ticket until all tasks are completed.