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; } } }

Parent story to bugs - what is the industry standard?

Virgo Admin

Hey everyone
I started using jira and I have a question about something im kinda stuck with:
When we have a sprint, as part of the QA some stories that are statused as "developed" are failing the tests because of a bug. So i'm adding the bug to the sprint backlog because i want it to be fixed as fast as possible, but what do i do with the parent story? do i flag it? if the story has 3 different bugs? how do i make sure the 3 child bugs are documented under the parent story? how do i change the status of the parent story to "done" after the 3 child bugs are changed to "done"? What is the industry standard for this situation?(I'm sure many scrum masters are facing it)

Accepted answers

Ste Wright

Hi @Virgo Admin

I'd suggest there are recommendations, rather than best practices. I've seen it done multiple different ways - but this what I would recommend:

Link the Bugs to Stories using linked issues. You should use a linked issue type most relevant to how you work as a team - for example, do the Bugs block the Story? Are they caused by the Story? Etc.
If the Bug blocks a Story from being delivered, I like to "flag" the Story. You can do this by right-clicking on an Issue on the Board and selecting Add flag, turning it yellow, so it's clear it has an impediment during stand-ups, etc.
When a Story can be moved to "Done" depends on your Definition of Done, and the priority/urgency of the Bug. Not every Bug will need to be fixed prior to completing the Story - perhaps it's a low priority? Perhaps the Story is only "Sprint Done" and not released? Etc
If the Bug is blocking the delivery of a Sprint, I would decide if it needs to be included as additional scope. Sprints/Teams should not be overloaded to a point where any issue or blocker could stop completion, so there should be some buffer to take into account these unexpected situations.

---

As a side-note, I also like to encourage the use of Automation in these scenarios - to help expedite the retesting or unblocking of Stories. For example, Automation rules could...

Flag/Unflag blocked Stories automatically
Notify a user when a Bug is ready for retesting
Notify a user when a Story can continue - i.e all Bugs are fixed
...etc

---

Let us know what you think

Ste

All comments

Ste Wright

Hi @Virgo Admin

I'd suggest there are recommendations, rather than best practices. I've seen it done multiple different ways - but this what I would recommend:

Link the Bugs to Stories using linked issues. You should use a linked issue type most relevant to how you work as a team - for example, do the Bugs block the Story? Are they caused by the Story? Etc.
If the Bug blocks a Story from being delivered, I like to "flag" the Story. You can do this by right-clicking on an Issue on the Board and selecting Add flag, turning it yellow, so it's clear it has an impediment during stand-ups, etc.
When a Story can be moved to "Done" depends on your Definition of Done, and the priority/urgency of the Bug. Not every Bug will need to be fixed prior to completing the Story - perhaps it's a low priority? Perhaps the Story is only "Sprint Done" and not released? Etc
If the Bug is blocking the delivery of a Sprint, I would decide if it needs to be included as additional scope. Sprints/Teams should not be overloaded to a point where any issue or blocker could stop completion, so there should be some buffer to take into account these unexpected situations.

---

As a side-note, I also like to encourage the use of Automation in these scenarios - to help expedite the retesting or unblocking of Stories. For example, Automation rules could...

Flag/Unflag blocked Stories automatically
Notify a user when a Bug is ready for retesting
Notify a user when a Story can continue - i.e all Bugs are fixed
...etc

---

Let us know what you think

Ste

Virgo Admin

Thank you so much for the informative answer. Thats more or less what i thought i should do but i wanted to get the affirmation
I will try to automate the process of moving stories that have linked bugs to "Done" automatically after the linked bugs are "Done".

Thank you!
Roi

Ste Wright

Awesome!

If you do need any assistance with creating the Automation Rules, please feel free to reach out on the Community - we'd be happy to help!

Ste

Nicolas Gondard

As another side note, provided you have ScriptRunner extension but not Automation, you may filter the stories according to the status of their child tests, e.g. :

issueFunction in linkedIssuesOf("type = <your test type> and project = <your project> and status = 'Closed'") and type = "Story" and status != 'Closed'

HTH

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud