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

IF Condition running despite not fitting condition

Erica Robinson_ls2zxv

I've been working on building out an automation that will generate a set of subtasks for teams based on the number of employees selected within a form on JSM.

As of right now, I have been able to build the subtasks with no issues, the values are coming in from the form as they should. The issue I'm running into is that when I'm trying to have an IF/ELSE condition run based on the number of employees selected, the IF/ELSE runs even if the value isn't met. For example, if the submitter selects 3 employees, only the first 3 IF/ELSE conditions should run, the other seven shouldn't. What's currently happening is all of them are running.

Here's the condition for the first set of subtasks:

IFELSE Condition.png

The condition is the same for the others with the "Second value" increasing to 3, 4, 5, etc.

The end goal is that if a user selects a number of employees, example: 4, then the subtasks for 1, 2, 3, and 4 are created, but 5-10 are not.

I've had a comment added to the main ticket that adds the value in plain text to confirm that jira is reading the value as expected:

I've also attempted to make the value a variable and the results were the same.

Any assistance with this would be appreciated.

Accepted answers

Bill Sheboy

Hi @Erica Robinson

For a question like this, context is important for the community to help. Please post the following:

an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution

Until we see those...

The if / else block does not process each block that matches...The assumption is the rule-writer ordered the blocks to be mutually exclusive, in the desired order of testing.

And thus if I am guessing your rule structure correctly, you were thinking it would process each one where the number matched your greater than criteria, correct? Seeing your entire rule will confirm this.

There are several ways to solve this, such as using branching with conditions or using separate if / else blocks for each condition test, or perhaps even using an Advanced Branch. Again, seeing what actions your rule takes will determine how to proceed.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Erica Robinson

For a question like this, context is important for the community to help. Please post the following:

an image of your complete automation rule in a single image for continuity
images of any relevant actions / conditions / branches
an image of the audit log details showing the rule execution

Until we see those...

The if / else block does not process each block that matches...The assumption is the rule-writer ordered the blocks to be mutually exclusive, in the desired order of testing.

Kind regards,
Bill

Erica Robinson_ls2zxv

Hey Bill,

Apologies for not including those. Here's the full rule, it's a bit long so I've split it into two columns:
FullTerm Rule.png

Here's the most recent audit log:

I removed the action to create the comment from the automation as it already confirmed the value was coming across as expected, but it can easily be added back in.

Correct, we need each section to run when a value higher than itself it selected since the users have the option to add up to 10 values in the form.

Thanks,

Erica

Bill Sheboy

Thanks for that information!

Have you tried writing the form field to the audit log to confirm it contains what you expect?

What is the type of your form field?

I notice the first two conditions both test a value greater than 2. Is that correct?

Erica Robinson_ls2zxv

I hadn't tried writing the form field to the audit logs, but I did have the field written out to a comment at one point and it was returning the values I was expecting. I can test again using the audit log instead.

The type is a dropdown.

Ah, good catch! That first one should be a value greater than 1. I've adjusted it.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud

jira-service-management-cloud

jira-service-management