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

Auto transition a sub task

darren.johnson

Hi,
I have set up a rule to auto recreate a task and sub task within the parent task, I would like the sub task status to transition to planned in line with the Parent task how do I do this please ? I am using Team Managed next gen.

Accepted answers

Bill Sheboy

Hi @darren.johnson

I believe you do this with the same technique of branching on created issues, but alter your rule to guarantee the sub-task(s) are created first by changing the first branch. For example:

trigger: same as you note
condition: same as you note
action: create task issue, same as you note, and also setting the epic link in this step
branch: on JQL of key = {{createdIssue.key}} This branch will have one-and-only-one issue, and so execute in-line
- action: create sub-task, same as you note
branch: on all created issues (this will now include the task and sub-task
- action: transition to Planned

Kind regards,
Bill

darren.johnson

@Bill Sheboy you cracked it Thank You, it was the hyphen in Subtask that was causing the issue.

All comments

Bill Sheboy

Hi @darren.johnson

I believe you do this with the same technique of branching on created issues, but alter your rule to guarantee the sub-task(s) are created first by changing the first branch. For example:

trigger: same as you note
condition: same as you note
action: create task issue, same as you note, and also setting the epic link in this step
branch: on JQL of key = {{createdIssue.key}} This branch will have one-and-only-one issue, and so execute in-line
- action: create sub-task, same as you note
branch: on all created issues (this will now include the task and sub-task
- action: transition to Planned

Kind regards,
Bill

darren.johnson

Followed those steps and afraid it does not work, it falls over on the JQL step, is there another way of doing this without using the JQL step ?

Bill Sheboy

Darren, when you note it falls over on the JQL step, what do you observe happening and what do you see in the audit log? Thanks!

Bill Sheboy

Sorry; my bad...it appears to be a bit more complicated as I just discovered...

{{createdIssue}} and {{createdIssues}} do not appear to return sub-tasks created in a rule!

So here is the work-around for this which I tested and believe works as you asked:

trigger: issue transitions to Completed
condition: check if summary contains your value
condition: check if issue type is Task
action: add the new task, copying the fields you wish
action: transition the issue to Planned
branch: on Most Recently Created Issue
- action: add your sub-task
branch: on JQL with issuetype = Sub-task and parent = {{createdIssue.key}}
- action: transition the sub-task to Planned

darren.johnson

@Bill Sheboy you cracked it Thank You, it was the hyphen in Subtask that was causing the issue.

Bill Sheboy

Awesome! I am glad to learn you got it to work.

__Bill

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