Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

If/Else block condition failing

Moazzam Faisal June 27, 2023

I am trying to implement If/Else block for our service catalog but the condition is not meeting the criteria and failing. Need some guidelines to fix the issue. See the images below:

Screenshot 2023-06-27 105605.pngScreenshot 2023-06-27 1056411.png

3 answers

3 votes
Kathy Hart
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 27, 2023

First, and very important question, is the "Does the issue require internal support?" field a Required field?

Or does it have a default value? 

If that is a Radio button, or Select List field, and it is not required, then there will be a None option that would not meet your conditions listed above and would cause the entire rule to fail. 

If you do not want that field to be required, then you will have to add a final Else action which tells the rule what to do if the ticket does not match either of those conditions. 

Moazzam Faisal June 27, 2023

@Kathy Hart "Does the issue require internal support" is a Select list field, how do I make it a required field?

Tim Perrault
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 27, 2023

@Moazzam Faisal 

 

If company-managed

Go to project setting --> Issues --> Fields --> edit field configuration and require the field needed

 

if team-managed Go to project setting --> Issue types --> select the needed issue type --> find field and check the Required box

Like Kathy Hart likes this
0 votes
Sam Harding
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 27, 2023

Hi @Moazzam Faisal 

It sounds like the other answers in this thread have got you on the right track, in looking into whether the field has been set or is empty at the time of the rule execution.

It seems like perhaps the trigger is not the right one for what you are trying to achieve. At the time of the rule creation, the selection seems to be empty, and after the issue is created the user then goes and selects an option.

If that is the case, then updating the trigger to be "Field value changed" and selecting the "Does the issue require...." field in the configuration would be better suited. That way the rule will fire once the user has selected an option, and should not be blank at that time

Hope that helps
Sam

0 votes
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
June 27, 2023

Hi @Moazzam Faisal

Welcome to the community!

The only thing I could think if is that the value is empty.  Is it a single select and are you making sure that is always entered?

Moazzam Faisal June 27, 2023

@Fabian Lim its a select list field with the option of Yes or No, once the user selects one of these option, i want automation to kick in and follow the of condition.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events