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

How do I prevent a status change if a field is empty using Automation rules?

Sigrid Schoepel

I am in a nextgen project. I check three fields and for each one if it's empty I set the status to the same status loop and I've tried setting it to the specific status where it should stay. Neither work. I can march it through the workflow. I also had a last step where it allowed the transition and I took that out but it didn't change anything.

I am an admin and started this project so I don't think it's a permission issue. What am I doing wrong?

Accepted answers

Jack Brickey

With NG you cannot use the traditional means of a Validator or Condition. With Automation you could transition the issue back to the previous status but this is an after-the-fact event. If you do this I recommend adding a comment as part of the automation rule so that users have a clue what happened and why and what to do to successfully transition.

All comments

Florian_8erf7n

I am not familiar with next-gen as we use a server installation. However I think you do not need automation at all. Try to use a condition on the transition instead. The condition is actually checked before the transition is executed. When the condition does not match the user cannot initiate it at all.

Jack Brickey

Sigrid Schoepel

I am trying that in the automation but it's not working if you look at the screen grab. Are you saying do an "if in status X and fields are empty then move to status Y"?

Jack Brickey

from what I can tell the automation should work but that depends on the details. I would suggest you try to simplify the rule just to get started. Try removing all but one condition, i.e. like this...

when: issue transition from in progress to done

if: severity_segnextgen is empty

then: transition issue to in progress

testing:

create a new issue and, assuming your workflow is To Do -> In Progress -> Done, then move the issue to In Progress
before moving to done let's test that your if jql displays expected results...
in the Advanced search for issues enter project = xxx and and severity_segnexgen is empty and status = "in progress". Does the new issue appear in the results? Assuming so proceed to 4)
execute the transition to Done
check the status after 5s. if not back to In Progress go to Automation and check the logs for that rule
share results here

Sigrid Schoepel

Thanks. I can get it to work if I make a separate rule for each field, which bloats my rules, but it works.

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-cloud

jira-cloud

automation