6.0.0-git
2019-10-23

[#7040] Automatic cost object completion
Summary Automatic cost object completion
Queue Hermes
Queue Version HEAD
Type Enhancement
State Assigned
Priority 1. Low
Owners wrobel (at) horde (dot) org
Requester wrobel (at) horde (dot) org
Created 2008-07-07 (4125 days ago)
Due
Updated 2008-11-06 (4003 days ago)
Assigned 2008-11-06 (4003 days ago)
Resolved
Milestone
Patch No

History
2008-11-06 02:23:57 Chuck Hagenbuch Assigned to Gunnar Wrobel
State ⇒ Assigned
 
2008-07-07 09:14:17 Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
I like the idea, though I personally rarely close a cost object after 
submitting time. Bonus points if you raise another notification after 
completing an item with a link to the cost object.

It's indeed more complicated in Whups though, since there are several 
states possible that mean "Resolved". We'd have to come up with a 
solution for that.
2008-07-07 06:27:38 Gunnar Wrobel Comment #1
Type ⇒ Enhancement
State ⇒ New
Priority ⇒ 1. Low
Summary ⇒ Automatic cost object completion
Queue ⇒ Hermes
Milestone ⇒
Patch ⇒ No
New Attachment: HK-GW-Cost_object_completion.patch Download
Reply to this comment
For my personal workflow stopping a hermes stop watch often means that 
the associated cost object has been completed. So I'd consider it nice 
if entering the time slice could optionally also trigger completion of 
the cost object.



The attached patch is a hack demonstrating the feature for interaction 
between hermes and nag.



I assume that the work flow looks different for others and cost-object 
completion might also work different in other horde apps (like whups). 
So I'm currently just asking for comments. But I'd be willing to 
prepare a real patch if there is a chance of integrating this feature.

Saved Queries