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

Jira automation

Anette Noll

Hi all,

could please someone bring me on the right track how to proceed with the automation described in the annex.

Your advices and ideas are really appreciated.

Thank you, Anette

Accepted answers

Bill Sheboy

Hi @Anette Noll

What problem are you trying to solve? That is, "why do this?" Knowing that may help the community better understand the need to offer better suggestions.

Until we know that...

What type of project is this: company-managed, team-managed, JPD, etc.?

What is the triggering event for your scenario as your rule seems to be checking the incorrect issue type: the Story rather than the Sub-tasks?

For example, is it this:

GIVEN a Story of Issue Type A
AND the Story is not in Status Z
AND the Story has a zero-to-many Sub-tasks of Issue Type B
AND the Story has a zero-to-many Sub-tasks of Issue Type C
AND the Story has a zero-to-many Sub-tasks of Issue Type D
WHEN one of the Sub-tasks of any type transitions status
AND any (all?) of the Issue Type B Sub-tasks are now in Status X
AND any (all?) of the Issue Type C Sub-tasks are now in Status Y
AND any (all?) of the Issue Type D Sub-tasks are now in Status Y
THEN transition the Story to Status Z

Kind regards,
Bill

All comments

Carol Lage

Hi Anette,

Looking about your problem, I don't know if I understand the different scenarios you have with your sub-tasks, but you can try this:

1. You can add a branch for each situation you have different denominations that will proceed with different outcomes. If you have different status doing the same thing on rule, you can use the JQL to group the status you want like Status in (Status1, Status2), like in the screenshot.

subtask rule example01.png

2. To set the rule for all projects, click on Rule details > Scope, and change the field to global (you have to be an admin to choose it) > Turn it on/Update.

subtask rule example02.png

Also, check this documentation about branching that can be useful in your case - Jira automation branches | Cloud automation Cloud | Atlassian Support

I hope this helps, and please let me know if it works or if you need to discuss it further.

Regards,

Carol

Anette Noll

Hi Carol,

thanks for your reponse.

I will try it today or on Monday and will let you know if it works as needed.

Best regards, Anette

Anette Noll

Hi Carol,

just tested what you described and serveral other ways as well, but parent does not transition.

In the screenshot below I described what I did. Would be great if you could have another look at it, what may be wrong with this.

Thank you!

Regards, Anette

Screenshot 2025-04-15 094144.png

Bill Sheboy

Hi @Anette Noll

What problem are you trying to solve? That is, "why do this?" Knowing that may help the community better understand the need to offer better suggestions.

Until we know that...

What type of project is this: company-managed, team-managed, JPD, etc.?

What is the triggering event for your scenario as your rule seems to be checking the incorrect issue type: the Story rather than the Sub-tasks?

For example, is it this:

Kind regards,
Bill

Anette Noll

Hi @Bill Sheboy ,

thanks for reminding me to be more precise.

Project-type
= company-managed

This is to be achieved
= if parent is in a certain status and all subtasks are in defined status, parent transitions automatically to next status

Initial Conditions:

parent work item is of Issue Type A

parent work item is in Status Z0 (status before Status Z)

The parent work item has zero-to-many sub-tasks of Issue Types B, C, and D

Trigger:

One of the sub-tasks of any type transitions status …

Conditions:

And all sub-tasks of Issue Type B are in Status X

And all sub-tasks of Issue Type C are in Status Y

And all sub-tasks of Issue Type D are in Status Y

Action:

Then transition the parent work item to Status Z

I hope this explanes better what I am trying to achieve.

Thanks for your time.

Best regards, Anette

Bill Sheboy

Thank you for clarifying the scenario. There is a template in the rules list you could start with named:

When all sub-tasks are done → move parent to done

With that as a starting point, you could change the Related-Issues Condition to use JQL (rather than just checking the subtasks), and then copy it so both subtask cases are covered.

As an example, and assuming the rule branches to the parent, the JQL for the first condition could be:

parent = {{issue.key}} AND issueType = "Type B" AND status != "Status X"

Please note I inverted the condition to test the status is not equal, and then the rule condition would check that None Match Specified JQL. Do the same thing with another condition for testing the other sub-task types.

Please try creating that rule and let us know what you find. Thanks!

Anette Noll

Hello @Bill Sheboy

Thank you for your response.

To be honest I don't quite understand your approach with the inverted condition, due to my little experience with automation.

What I have done is to start with the template you recommended and tried a lot of combinations.

It works for one sub-task type, but not for more. What is wrong with this?

Screenshot 2025-04-22 152418.png

Best regards, Anette

Carol Lage

Hi Anette,
Glad that Bill was able to understand and support you.
Hope that setting the rule as global also worked.
Regards,
Carol

Anette Noll

Hi Carol,

finally problem is solved.

Also thanks to you to advise me with the rule as global!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud