In the JIRA workflow there is progress tracking but what about when a JIRAs status is returned to the previous status? For example if a developer advances a JIRA to Pending QA Testing but fails testing and is returned to Pending Development.
Is there a way to track how many times an assignee (developer) has his JIRAs returned to him for recoding. Can this be reported for a single assignee (developer) and as a group of assignees (all assignees). Then can this be reported by a specified period of time by YTD or by percentage of total JIRAs.
JQL returns the current status of issues. You can use the "Was" operator in JQL to get issues that were in certain status in certain historical time.
Like
Status was in "In Progress" by john
This will return you the issues which were in status "In progress" by the user John.
But your requirement is something different as you want to perform reporting and create metrics based on issue history. There are couple of reporting plugins which can help you
"eazyBI" and "Dataplane" should be able to create the reports which you are looking for. Question similar to your has been discussed many times on this forum, here are some links
https://community.atlassian.com/t5/Jira-questions/count-of-status-change/qaq-p/444573
https://community.atlassian.com/t5/Jira-questions/Count-Status-History/qaq-p/225434
Thanks for the quick response, I will look through the resources you have provided. I appreciate the information.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Tarun Sapra, Thank you for suggesting eazyBI as a possible solution!
@Timothy Williams, here is an example report in eazyBI showing Transitions by Transition Author and Assignee.
Let me know if you are interested in eazyBI and have some further questions about the report you wish to build!
Lauma / support@eazybi.com
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please accept the answer/upvote if your satisfied with the solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.