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

Why is my Rule to transition a parent when all subtasks are completed not working?

Phil Bustin_7fmhjs

In the sandbox, I have a working automation that creates one or more sub-tasks (Issue Type = Dev Task) when a particular transition is run.

I modeled the automation after one I found in:

https://community.atlassian.com/t5/Automation-questions/How-can-I-transition-the-parent-when-all-subtasks-are-resolved/qaq-p/159407

The automation log shows NO ACTION PERFORMED when I complete the only sub-task I created.

I tried sub-task instead of Dev Task as the {{issue.issuetype}}, and {{issue.issuetype.name}} = Dev Task. (I don't think I tried {{issue.issuetype.name}} = sub-task.)

Note in the screenshots below that my rule branch contains "If:", but the community post rule contains "And:". How was "And:" obtained?

My rule

Rule from Community post

Accepted answers

Bill Sheboy

Hi @Phil Bustin

Would you please post an image of the audit log details, showing the rule execution? That may provide more context for this symptom. Thanks!

Regarding your comment about the "And" in the old screen image (from that post), I believe that is just the evolving UX of the rule editor, over time, changing.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Phil Bustin

Would you please post an image of the audit log details, showing the rule execution? That may provide more context for this symptom. Thanks!

Regarding your comment about the "And" in the old screen image (from that post), I believe that is just the evolving UX of the rule editor, over time, changing.

Kind regards,
Bill

Phil Bustin_7fmhjs

Rule log.jpg

Bill Sheboy

Thanks for that information.

I think this is both a smart value name/case-sensitive and default attribute thing. Please try changing your advanced compare condition to check this:

first value: {{issue.issueType.name}}
condition: equals
second value: Dev Task

And...if that does not help, try writing this to the audit log before the condition to confirm the case/spacing/name of the issue type:

Phil Bustin_7fmhjs

That didn't work; nor did it when I tried it before. See screen shot below for confirmation.

I'm not aware of a way of writing to the audit log, but I tried adding it in a comment in a Log work action. After that the automation showed success twice, although I wasn't aware of that at first, but then showed errors. It did not transition the parent. I'm not sure what the comment display signifies, although I think it shows that the issue type name syntax is correct.

success followed by errors.jpg

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