Feature #2678
Search and stats on workflow transitions
Status: | New | Start date: | 2009-02-05 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | - | |||
Target version: | - | |||
Resolution: |
Description
- How many (and what) issues passed "Queue to Backoffice" workflow-step (for a specific category or some other filter)?
- What issues was tested by [insert tester] (show really as the member who change status from "Queue for test" to some of the new statuses indicating test passed or failed).
- Who is our "best" tester (as defined in 2 above)
- How many (and what) issues are at or have passed workflow-step "Approved by customer". First part of question is easy, the second is not.
I would assume most people solve this with (redundant) extra custom fields tracking the above information (like tester or a checkbox for apprived by customer). Well, i do that too, but it's not all that good. I cannot handle retest and worst case i does contain the wrong info (i did the test and updated the issue but forgot to set the field).
I know the tables and i do take some of this info via SQL (some joins) but would love to get it via GUI (and in summary).
Is this a need for the rest of you as well?
/T
History
#1
Updated by Eric Davis over 13 years ago
Is this a need for the rest of you as well?
I don't have a need for it because my workflow is really open (anyone can change an issue to any status) but it might be useful to others.
#2
Updated by Dipan Mehta about 9 years ago
+1. It would be good to have essentially having filtering and sorting based on journal data!