You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Is there an easy way to get issues that were rejected after testing and returned to “To do” status? Our QA manager needs to collect this information every month. Our SaaSJet team want to share this use case and how our PM track rejected issues with help of Issue History for Jira.
From this use case, you will find out:
The first thing you should check is your workflow and what statuses it includes. To do this, go for Project Settings ▶️ Workflows.
Here you will see the scheme of your workflow. In our case, it looks the next way.
So, if no problems are detected while testing, the issue goes to “Ready to release” status. Otherwise, it goes back to “To do”.
The other way is simply to check your board, and you will see all statuses: ToDo → In Progress → On Review → Ready for Testing → Testing → Ready to Release → Done
*Your workflow may be different depending on your business processes.
When you know what statuses are in your workflow, you need to check what issues were moved from testing back to “To do”. In our example, it’s Testing → To do.
🔶 One way to achieve this is to use advanced issue search (JQL). It can look like this if you need to check status transitions for some project after some date:
Project = QA and status CHANGED FROM "Testing" TO "To do" AFTER "2023-03-01"
If you need to check status transitions for some assignee after some date:
status CHANGED FROM "Testing" TO "To do" DURING ("2023/02/01", "2023/03/01")
With these queries, you will get basic information about what issues were transitioned, when and by who.
🔶 The second way is to create a report with Issue History for Jira. Here you can customize everything according to your needs. And it’s easy to filter issues by different options and choose dates from the drop-down menu.
So, you will get:
1. Select project, assignee, sprint or other option for which you want to get rejected issues. We will take project here.
2. Also, you can choose dates.
3. Choose appropriate statuses, in our example: Testing → To do.
You will receive all transition from Testing → To do statuses. In our case, we have only one rejected issue for this month.
4. Export the report to CSV or Excel if you need to count the amount of rejected issues or analyze the data deeper.
How many rejects did you have this week or month? Would you like to find it out? You can try to follow this instruction with a free trial of Issue History for Jira. Hit the like button if the article is interesting to you 😉
41 accepted answers