So, how do I do the processing of >activities that can be processed later.
|Reported by:||yoheeb@…||Owned by:||hasienda|
|Severity:||normal||Keywords:||needinfo search TracForm fields content|
A couple of examples could be very helpful here. I see at least 2 use cases of the bat:
Test case/run tickets, this would be awesome me thinketh!
and to list resultant activities. I was looking to write a workflow/blackmagic based plug to generate master/slave tickets based on a check box type answer when accepting a ticket (user manual update required? Code review Required? Validation Plan Changes?) which would generate blocking tickets. This would be superior in my mind. especially since I can create form templates for common activity "types" bring up the ticket, see what has been done, what hasn't
but how do I, process tickets to identify the ones that have the "required" checked, but the completed not (some may want this as part of the work flow, me, more of an informational) at some point. Say, show me all tickets requiring user manual updates, which don't have user manual updates completed.
Change History (12)
comment:8 Changed 5 years ago by rharkins
- Priority changed from low to high
- Severity changed from trivial to major
comment:9 in reply to: ↑ 6 Changed 3 years ago by hasienda
- Keywords search TracForm fields content added
comment:11 Changed 3 years ago by hasienda
- Keywords needinfo added
- Trac Release changed from 0.10 to 0.11