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

Automaton rule to update the 1st sub-task status upon Parent Status change

vincenzo.spatafora

Dear ALL,

being trying to set a rule up such that when the status of a Parent changes for example to "In Progress", the associated first sub-task status is set also to "In Progress".

I know usually it's the way around but I need this case.

The sub-tasks are for example 3 but I need a rule to change the status only of first sub-task.

Is this feasible in Jira DC.

Attached what I've done so far but the rule changes the status of all the sub-tasks.

Thanks in advance.

Accepted answers

Bill Sheboy

Hi @vincenzo.spatafora

For this scenario, you could branch on JQL to the specific issue, using the key, rather than branching on all of the subtasks.

Kind regards,
Bill

John Funk

Hi Vincenzo,

How are you identifying which subtask is the first one? Is there some value for that sub task that could be used in a condition?

All comments

Bill Sheboy

Hi @vincenzo.spatafora

For this scenario, you could branch on JQL to the specific issue, using the key, rather than branching on all of the subtasks.

Kind regards,
Bill

John Funk

Hi Vincenzo,

How are you identifying which subtask is the first one? Is there some value for that sub task that could be used in a condition?

vincenzo.spatafora

Hi @John Funk,

thanks for your reply.

I understand the first sub-task should be identified by {{issue.subtasks.get(0).key}}.

Kind Regards, Vincenzo.

vincenzo.spatafora

Hi @Bill Sheboy, happy to see you again.

Do you mean like the one I have attached.

If so, I get performance issues now as there are a lot of sub-tasks on my Jira Project and the limit has been execeeded.

Thanks in advance and have a nice week.

Kind Regards,

Vincenzo.

Bill Sheboy

I was suggesting to add to your branch JQL (or replace it with):

key = key of the desired subtask

That will ensure you only get the one you want.

vincenzo.spatafora

Thanks @Bill Sheboy

Is it possible to make it more general?

I wouldn't know the key sub-task for the up-coming/next triggering issues which will be created.

Above, @John Funk was suggesting to place a condition.

Kind Regards, Vincenzo.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-data-center

data-center