Every time a bug is created and that bug relates to an issue on the active sprint, then that issue is flagged and only can transition into done once the bug is fixed (status = Done).
Is there a way to automate the flagging of an issue with a related bug to it?
Maybe... How do you know a defect (bug) is related to another issue within Jira?
If it is a sub-task type or is linked to the "parent" issue then you should be able to use an automation rule to detect the condition and then flag it. You would also configure your workflow to check for the blocking item before allowing a parent to transition to done.
Best regards,
Bill
We link bugs (issueType = Bug) with the related user stories (issueType = Story).
But I can't find a way to do it on automation yet!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are manually linking when you create the Bug, you can then use automation to set the flag (edit issue, setting the Flagged field to True).
If you are looking for a way to automatically link the Bug to the Story, using automation, you would need some way to uniquely identify the Story for the link to the Bug. Otherwise, there would be no way for automation to do this.
__Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bill,
That's exactly what I want to do. Flagged automatically a story which has a bug related to it. But I'm trying to automate it but without success.
Do you have any ideas on how to do it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying. Okay, I will assume when you create a bug, that you link it to a story before saving. If so, this will do it:
If you are using a specific link type (such as blocked), you can add that to the branch check.
If you create a bug and later add the link to the story, you could copy this to another rule, with a trigger of Issue Linked.
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.
Bill,
This is how I created the automation. The audit log shows that it worked. But the Flag was not added to the related Story.
Maybe the problem is on the last part of the automation. I'm not sure which one to select.
What do you think?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You almost have it done... you want to set Flagged to TRUE in the Edit Issue.
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.
Hmmm... I just recreated that rule, and I found it. Try this. Delete the edit, save your rule, publish, disable it (just in case...) and then try to re-add the Edit Issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bill,
Do you think I need to do some editing on advance filed section? Because I can't find the "true" option. The only options are the following ones:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please try to just type TRUE, and tab off the field. That worked for me.
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.
Argh! That is unfortunate... At some time in the past, I typed in TRUE and it has just worked since then, becoming available in the drop-down list.
Updated: the JSON advanced edit does not appear to work for the Flagged field. I'm still experimenting with it to understand why...
Something's up and it may be time to submit a support ticket:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey, @Luiz Alves Filho
One more thing to try: select Impediment from the dropdown for edit of Flagged.
I found an older post where TRUE worked for some people and Impediment worked for others. Odd that both work for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It worked with the impediment!
Thanks a lot @Bill Sheboy
Next Automation will be to remove the flag when the linked bug transitions to "Done". Let's see if I can handle it! haha
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.