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

Automate parent transition based on subtasks multiple states

gmastrandrea

Hello everyone!

we have project with a kanban board with many columns:

- backlog

- selected for development

- in progress

- done

we're using a parent/subtask structure for every issue in the board. What we want is to make multiple controls on the siblings subtasks to control the transition on the parent.

Basically what we'd love is, whenever a subtask transitions from a status to another one:

- if there is at least one sibling task in "in progress" the parent task will move to (or stay in) "in progress"

- else if there is at least one sibling task in "selected for development" then the parent will move to (or stay in) "Selected for Development"

- else if there is at least one sibling task in "Backlog" then the parent will move to (or stay in) "Backlog"

Please note that "In progress" takes precedence over "Selected for Development" and "Selected for development" takes precedence over "Backlog".

Right now we're able to make just one of these controls but we're struggling to make all of these controls whenever a transition of a subtask occurs.

Any ideas?

Accepted answers

Bill Sheboy

Hi @gmastrandrea -- Welcome to the Atlassian Community!

For a question like this, please consider posting an image of your current rule and of the audit log from an execution. That will provide context to the community to offer ideas. Thanks!

You probably can do this with related issues conditions, yet I have seen challenges with those...so...

Instead you could use Lookup Issues, JQL, and created variables to capture the count of issues (sub-tasks) in each condition, and then use if/else to find the correct path, and then branch on the parent to perform the update transition.

Best regards,
Bill

All comments

Bill Sheboy

Hi @gmastrandrea -- Welcome to the Atlassian Community!

For a question like this, please consider posting an image of your current rule and of the audit log from an execution. That will provide context to the community to offer ideas. Thanks!

You probably can do this with related issues conditions, yet I have seen challenges with those...so...

Best regards,
Bill

gmastrandrea

Hello Bill! Thanks for your interest. Here's the main rule that we use.

The main problem we're struggling with is that we can't find a way to use an if/else structure in the "Parent" branch rule.

I'd like to investigate, though, your suggestion about creating variables to count the issues in each condition. Where can i read more about this topic?

Schermata 2021-07-14 alle 17.56.13.png

Bill Sheboy

Hi!

Yup, that nesting issue is why I suggested gathering the information first, use if/else on the results, and then branch inside the if/else clauses. The opposite is not supported, as you note.

To learn more about created variables, please look here:

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Createvariable

To learn more about lookup issues, please look here:

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues

If you get stuck, please let me know. Thanks!

gmastrandrea

@Bill Sheboy thanks for the docs links!

I gave a try to the approach you suggested, and i think i'm pretty close to what we want to achieve. Here's our rule. It's a bit long, but the custom variables i created with lookup issues do work well and in the parent comment i have the right numbers.

Apparently, though, something is not working properly with the "if" statements. The task execution simply won't enter the if conditions and the parent won't be transitioned nor commented.

Any suggestion?

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

transition

atl-gruland

automation

sub-task