Hello,
I'm hoping someone can help provide some guidance. I am new to Jira and automation.
I am attempting to build out a process flow for a new board.
I am creating a series of sub-tasks when the Parent Story/Bug is added to a sprint: DEV, Code Review, QA, UAT, Deploy, Validation.
I want to automate moving the sub-tasks to the appropriate status when the previous task is completed.
I've created the following rule:
When the DEV sub-task is transitioned to "Done" > Update the Parent to "Code Review." Then update the "Code Review" sub-task to Code Review as well.
The first step is working, the parent is moving to Code Review after the "Dev" sub-task is moved to done. The Code Review sub-task however is not updating.
Any guidance or tips would be greatly appreciated!
Hi @Stacey Jones -- Welcome to the Atlassian Community!
Yes, and...to the suggestion from @Trudy Claspill
You could use a single branch to both the parent Story and the sibling sub-task for the "Code Review". Assuming the trigger issue is a subtask, the JQL for the branch would be this:
key = {{triggerIssue.parent}}
OR (
parent = {{triggerIssue.parent}}
AND issueType = "Sub-task"
AND summary ~ "\"Code Review\""
)
Then perform the issue transition action.
Kind regards,
Bill
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
CCT-87 is the parent
The code review sub-task that is not updating is CCT-90, which isn't mentioned in the log.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The subtask is not being referenced because your branch is for the parent issue (CCT-87) so when you run your JQL conditional statement it is checking if the "Issue matches JQL" that issue at this point being the parent issue.
What you can do is that if your if condition regarding subtasks of the parent issue being present is true, then create a branch for those subtasks and check to see if they meet your JQL condition, if they do, then transition them to "Code Review"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@john_monteith It is not possible to create a Branch inside of another Branch. Notice that FOR is not available at this point.
Welcome to the Atlassian community.
You will need to add a separate branch to your rule to change the focus to the "sibling" sub-task:
Use the For: Related Issues: JQL option and a JQL to find the desired sibling subtask. Make sure that you uncheck the box indicated by the arrow in the image above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Trudy, you are absolutely correct, apparently my brain took off early for the weekend. Stacey, my profound apologies.
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.