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

Move a subtask relative to its parent's move

Marcelo Ignacio Cid Abud

Hello community ,

I need your help for the following automation:

I want the child subtasks of a story to move according to the movement of their parent.

Ex: If my story is in progress and goes to the discarded state, all the issues that this story has should go to the discarded state.

Accepted answers

All comments

Sam Nadarajan

Hello @Marcelo Ignacio Cid Abud

In your automation rule, I'd consider the following configuration:

Trigger: Issue Transitioned (specify to and from statuses at this level)

Condition: Specify that you only want to look at non-subtasks (standard issue types)

Branch Rule/Related Issues: Subtasks

Action: Transition the issue (Copy from Trigger Issue) so that the sub-tasks match the movement.

Screen Shot 2022-08-10 at 11.02.41 AM.png

You'll want to make sure that your subtasks have the same transitions available as your parent issue types, otherwise you'll get an error.

Also, you could actually avoid specifying a status in the trigger: Issue Transitioned and leave it blank so that any transition is picked up by the automation rule.

Not sure how active your instance is, but if you have a lot of issues you may run into execution limits for automation rules unless this rule only needs to run within a project. Just something to consider.

Hope this helps

Marcelo Ignacio Cid Abud

Hi @Sam Nadarajan

Thanks for the speed in responding to my question.

I tried the automation and it works perfectly now I have 2 queries:

1.- If I want to add 2 conditions to this automation: 1 If the subtasks are in the backlog, they must be removed from the project, 2 if they are in progress they become discarded as the parent.
2.- The idea of this automation is that it can be executed in approximately 15 projects, would I have to do a data refresh before executing the action?

Sam Nadarajan

1 - I would add your conditions inside the "For Sub-tasks" branch in your automation rule. You can add conditions inside this branch (hover over somewhere within the branch) and either add a condition or an if/else block which would give you more flexibility. That would cover the first condition, for the second condition if you're referring to sub-tasks again I am not sure what you mean by "become discarded as the parent"

2 - You'd want to do a data refresh (re-fetch issues) if you have actions earlier in your automation rule that later conditions or actions in your automation rule reference. If you are on the premium plan, you can configure your automation rules to span multiple projects so you don't have to duplicate the same rule 15 times.

Hope this helps

Marcelo Ignacio Cid Abud

@Sam Nadarajan Thanks again.

I have a problem with delet issue (subtask)

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