Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why doesn't this workflow transition Conditions rules work correctly.

Danno
Community Champion
December 15, 2021

I am trying to understand why this workflow transition doesn't work as expected. The person making the transition has the Supervisor and Dept. Manager roles assigned to them, the custom field has been set to Requisitioner, although it is a Select List (cascading) custom field where I am only querying the top level of the field, and the Expense Total ($) field is set to a valid number (I wish Atlassian would make a currency field available). I'll include a screenshot of the transition as well as the latest issue that didn't allow the transition to be available.Screenshot 2021-12-15 135611.gif

Screenshot 2021-12-15 135900.gif

3 answers

1 accepted

0 votes
Answer accepted
Rodney Nissen - ReleaseTEAM
Community Champion
December 15, 2021

If I had to guess - the cascading select is what is messing you up.  I'm not 100% sure how that evaluates for the purposes of a condition, but everything else appears to be good. 

Danno
Community Champion
December 20, 2021

@Rodney Nissen - ReleaseTEAMI thought of that after I posted my question and added the extra possibilities that would be selected in the cascade second field but that didn't allow it either.

I think I will try backing out some of the conditions until I get it to work again and then strat adding them back in. I have a feeling it is one of the two nested conditions (Any of the following) that might be causing it to fail.

0 votes
Danno
Community Champion
August 26, 2022

LOL! @Rodney Nissen - ReleaseTEAM and @John Funk I just had an Atlassian "Facebook memory-like thing" come up. I got an email from them about this issue as if there was a new answer but they were really just bugging me to accept something.

Thanks to both of you again. I don't even remember what I did to fix it but I'll give this one to Rodney.  

John Funk
Community Champion
August 26, 2022

Haha - Glad it is working for you.  :-)

0 votes
John Funk
Community Champion
December 16, 2021

Hi Danno - when you say it isn't working, do you mean that the condition is not allowing the transition to show up for the user to select? 

Have you tried combining that information together in a JQL to see if the issue comes up for it? Something like: "Expense Total ($)" < 999.99 and "Intended Purchaser" = Requisitioner

Danno
Community Champion
December 20, 2021

Hi John, your first assumption is correct. It doesn't make the transition visible to the user. All the permissions are correctly set and the required fields have the correct info. The issue does exist. I have the exact same rule in place for a different transition except for the "Intended Purchaser Field". I got to thinking that since that field is a cascading one that I might have to add the possible secondary selections in it to allow the transition but that didn't seem to work either.

John Funk
Community Champion
December 21, 2021

So you actually put the above JQL into a filter and the search showed the issue? 

That would tell me that it should work for the condition. Can you share the condition that you have (a screenshot)?

Like Danno likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events