During a sprint, QA team identified a defect for a Story. In our current setup, we have QA to create a subtask under the Story with Story Bug(Custom field). Using the current process, the Story cannot be completed until all the subtasks(QA defect is fixed). We want to have that control in place.
We want to move away from the above process instead use the Bug as Label for all future defects. In this process, someone can mark the story to be complete even though the defect is not fixed. I followed the below mentioned process:
Step 1: Create an issue
Step 2: Issue Type - Bug
Step 3: Linked Issues : I tried all combination ( is Blocked by, blocks, is a child of, is child of)
With all the above mentioned(Step 3) permutation, I am still able to mark the story as Done, without fixing the defect.
I want to know if there is any other condition I can use to ensure that the story cannot be marked as Done until the defect is fixed.
Thanks for your help
Sub-tasks is the most foolproof way out of the box. Your other choice is permission (role or group) based but that isn't ideal.
If you have Jira Suite Utilities you could restrict closure to admins for stories and use the Linked Transition postfunction on the close transition of the sub-task.
Other solutions such as Scriptrunner exist as well, but I think you're looking at add-ons if you're moving away from sub-task blocking conditions on stories.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs