Hi everybody, In my jira i have five types of tasks, and ten types of subtasks, Each task have a different order of subtasks when they are created. When i change the type of task, i created a automation for to eraser all subtasks and to create new subtasks in correct order, but i need of more precision in this action. The same subtask is in different subtask and I want it to: * When to change type of task excluded the subtasks, that will not be used; * When havent the subtasks that was need, create it; * Put the new subtasks created in a correct order with the others. For exemple: Task 1: * Registration * Production * Revenues * Send * Instalation * Measurement Task 2: * Negotiation * Registration * Production * Revenues * Send * Measurement When i change Task 1 to Task 2 : * Negotiation (Created and put in order) * Registration (Keeps) * Production (Keeps) * Revenues (Keeps) * Send (Keeps) * Negotiation (Excluded) * Measurement (Created) Somebody know how i can create this automation? The most problem is to put the subtasks in a new order.

Hi @Douglas Oliveira Short version: I do not believe that is possible with out-of-the-box automation Longer version: * There are several open defects and suggestions related to ordering of sub-tasks, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42231 * My understanding is that sub-task ordering within the parent is based upon the create date/time...unless you change it with the UX * I haven't tried this: A possible work-around for automation would be to introduce delays and attempt to add them in your order. For example, add each sub-task, one-by-one, with separate actions followed by a re-fetch action. That will dramatically slow down the rule (eating up your automation time limits) but it may fix the ordering. Kind regards, Bill

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

Change order of subtasks.

Douglas Oliveira_a3xjuk

Hi everybody,

In my jira i have five types of tasks, and ten types of subtasks, Each task have a different order of subtasks when they are created.

When i change the type of task, i created a automation for to eraser all subtasks and to create new subtasks in correct order, but i need of more precision in this action.

The same subtask is in different subtask and I want it to:

When to change type of task excluded the subtasks, that will not be used;
When havent the subtasks that was need, create it;
Put the new subtasks created in a correct order with the others.

For exemple:

Task 1:

Registration
Production
Revenues
Send
Instalation
Measurement

Task 2:

Negotiation
Registration
Production
Revenues
Send
Measurement

When i change Task 1 to Task 2 :

Negotiation (Created and put in order)
Registration (Keeps)
Production (Keeps)
Revenues (Keeps)
Send (Keeps)
Negotiation (Excluded)
Measurement (Created)

Somebody know how i can create this automation?

The most problem is to put the subtasks in a new order.

Accepted answers

Bill Sheboy

Hi @Douglas Oliveira

Short version: I do not believe that is possible with out-of-the-box automation

Longer version:

There are several open defects and suggestions related to ordering of sub-tasks, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42231
My understanding is that sub-task ordering within the parent is based upon the create date/time...unless you change it with the UX
I haven't tried this: A possible work-around for automation would be to introduce delays and attempt to add them in your order. For example, add each sub-task, one-by-one, with separate actions followed by a re-fetch action. That will dramatically slow down the rule (eating up your automation time limits) but it may fix the ordering.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Douglas Oliveira

Short version: I do not believe that is possible with out-of-the-box automation

Longer version:

There are several open defects and suggestions related to ordering of sub-tasks, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42231
My understanding is that sub-task ordering within the parent is based upon the create date/time...unless you change it with the UX
I haven't tried this: A possible work-around for automation would be to introduce delays and attempt to add them in your order. For example, add each sub-task, one-by-one, with separate actions followed by a re-fetch action. That will dramatically slow down the rule (eating up your automation time limits) but it may fix the ordering.

Kind regards,
Bill

Douglas Oliveira_a3xjuk

I @[deleted], Thanks for the anwser.

Well... I imagined that to put the subtasks in order was the most dificult, the organization of the subtasks have some limitetions in the Jira.
But is very interessant your understanding, I thought that the Jira organize the order of subtasks only by key numer.
By the way do you know a way for the automation to search a subtasks when i change the type of task and if doesnt to find them, creat them?

Best regards,
Douglas

Bill Sheboy

Regarding ordering, as sub-tasks are created over time the issue keys will increase. So key order matches created order.

For your next question, would you please explain a bit? Are you asking how to find if a sub-task exists with some criteria, and when not found add one with that criteria?

If so, you could use Lookup Issues with JQL, and if the resulting count of issues is zero, create the issue. The JQL would be something like:

project = myProject AND issueType = Subtask AND parent = parentIssueKey AND some other criteria

And the condition check would be {{lookupIssues.size|0}} equals 0

Douglas Oliveira_a3xjuk

@Bill Sheboy

For exemple, i have this standarts of tasks and subtasks:

Task1:

Registration
Production
Revenues
Send
Instalation

Task 2:

Negotiation
Registration
Production
Revenues
Send
Measurement

Task 3:

Negotiation
Registration
Production
Revenues
Send
Instalation

When i change the type of issue, the automation should to create the subtasks for keeps the standart but cant to have duplicate subtasks. Not necessarily in the same order, i can change this after.

Douglas Oliveira_a3xjuk

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