nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the best or fastest way to identify User Stories with all Story Bugs in Done status?

Daniel Martínez_t4kfhp

In our backlog, there are 75 User Stories, in several statuses, including "QA". Per our internal process, all bugs are created as Story Bugs, and only after all Story Bugs are Done do move a User Story to the next status in the workflow, so that the next team continues the work (e.g., UAT, Production Release, etc.). However, due to forgetfulness or any other reason, we might have User Stories which are ready to be moved to the next status (i.e., all of their Story Bugs are closed or Done) yet are still in "QA" status. As a Scrum Master, I need to quickly be able to identify such User Stories, so that they are promptly updated by our QA team and our team's effectiveness is kept at a maximum.

Accepted answers

Karan Sachdev

Hey Daniel,

Can you please clarify how are these User Stories linked to the Story Bugs? Are these Story Bugs created as "subtasks" (child issues) of the User Stories?

If yes, you can consider using the below automation rule to update the status of the Parent issue once all its child issues are moved to Done status:

If there's another link type between the user stories and story bugs, you may try to tweak the Branch and the JQL condition to meet your use case.

(Please be mindful of your monthly execution limit: How is my usage calculated?)

I hope this helps.

Thanks,

Karan

All comments

Karan Sachdev

Hey Daniel,

Can you please clarify how are these User Stories linked to the Story Bugs? Are these Story Bugs created as "subtasks" (child issues) of the User Stories?

If yes, you can consider using the below automation rule to update the status of the Parent issue once all its child issues are moved to Done status:

If there's another link type between the user stories and story bugs, you may try to tweak the Branch and the JQL condition to meet your use case.

(Please be mindful of your monthly execution limit: How is my usage calculated?)

I hope this helps.

Thanks,

Karan

Daniel Martínez_t4kfhp

Hi Karan,

Thanks for such a quick and informative response. Yes, the Story Bugs are created as "subtasks" (child issues) of the User Stories. Regarding your response, I have two questions or doubts:

I am trying to implement an automation that notifies us when the conditions are met, but am having trouble with one JQL query (see screenshot). What would be the correct syntax for this?

Again, thanks for the help!

Karan Sachdev

Hey Daniel,

If you would like to include multiple status values in your JQL using the IN operator, you need to include them in parenthesis. If there's a space in a status name, include it in double quotes.

Example: status IN (Done, "In Progress", "Ready for Release")

Thanks,

Karan

Daniel Martínez_t4kfhp

Hi Karan,

Thanks for the clarification! I have enabled the rule as shown below and am crossing my fingers that it works as expected. I'll keep you posted.

For now, thank you so much for helping me, and have a great day!

P.S. The title of the rule should be "Notify when all Story Bugs of a User Story are closed bue the User Story is still with Devs or QA".

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud