Linked Issues with User Story

[Hizkeel Khan]

Hi,

I have a user story to which I have linked 2 story bugs. If linked issues are in progress then the story shouldn't move to Code review which is the next transition because the linked issues are still in progess. 

When linked issues are moved to testing (No code review) then the story should move to Code Review because all the linked issue are now moved to testing. 

I have figured out the first part where the story is not moving to code review as long as there are linked issue in progress. The problem i'm facing is when the linked issues moved to testing, I cannot move the story to code review, it reverts back.

@Bill Sheboy @Stephen_Lugton 

[Trudy Claspill]

Hello @Hizkeel Khan 

How have you achieved this configuration? Have you customized the workflow? Have you created automation rules? Please provide screen images that show what you have configured blocking the transition of the story to code review as long as there are linked issues in progress.

[Hizkeel Khan]

Actually, the automation rules was not working correctly. It was transitioning to In progress irrespective of the status. I was doing some R&D and it turned out I cannot achieve this without using third party tool like script runner. 

I haven't tried the script runner yet myself but I'll look into it. Meanwhile, if you have any solution for my query then please let me know. 

[Trudy Claspill]

Breaking down your original post

I have a user story to which I have linked 2 story bugs. If linked issues are in progress then the story shouldn't move to Code review which is the next transition because the linked issues are still in progess.

The native workflow capabilities don't have a method to check the status of linked issues and block the transition of the primary issue. A work around would be to have a custom field in the primary issue that keeps track of whether or not all the linked are "In Progress". You could then set a Workflow Condition for the transition based on that custom field and prevent the primary issue from transitioning based on the state of that custom field.

When linked issues are moved to testing (No code review) then the story should move to Code Review because all the linked issue are now moved to testing. 

This is possible with an Automation Rule that is triggered by Issue Transitioned for the project that contains the linked issues. The rule would then find the linked primary issue, check if all the issues linked to the primary issue are in the required status, and then transition the primary issue.

Your post tags note that you are on the Free subscription. On the Free subscription you are limited to 100 rule executions in a month, so you would have to consider how many times the above rules might run and how that would affect the total number of rule executions for your Jira instance.