Branching Logic in workflow conditions

Nicole Pomponio May 15, 2023

We have a scenario where we only want certain people to move an issue to a certain status, and we have them in a Project role

I would like to allow for exclusions, based on a field value. 

How can I group the workflow conditions for this?

 

If Exclude from Controls is true, all users can transition the issue

If Exclude from Controls is false, only this role can transition the issue

 

Thanks!

1 answer

1 accepted

1 vote
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Hello @Nicole Pomponio 

Welcome to the community.

Are "true" and "false" the only values available for "Exclude from Controls"? Is that field always set to one or the other value and is never null/none?

If so then your workflow transition conditions would look like this:

Screen Shot 2023-05-15 at 6.10.13 PM.png

Nicole Pomponio May 16, 2023

Yes, and my initial testing has passed. Ill be testing with someone else later today and will confirm solution!

Thank you!!

Nicole Pomponio May 16, 2023


@Trudy Claspill Hi! This had the opposite effect of what I was hoping for. I set the rule up as shown above and the results are as follows - 

With Exclusion True, they did not have the option to move to Ready to deploy

With Exclusion Null/Empty, they were able to move to Ready to Deploy

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 16, 2023

Can you please provide an image of what you set up?

And please explain who "they" is. Does "they" mean "all users" or does "they" mean "users in the specified role"?

Also, what type of field is Exclude from Controls? Is it required to always be set to "true" or "false", or is it allowed to have no value?

Nicole Pomponio May 17, 2023

@Trudy Claspill Apologies, clarifications below

They would be a User, basically anyone who is not assigned the Project Role in the conditions.

Users should not be able to move the issue to Ready to Deploy unless the Exclude from Controls = Exclude. 

Deployment Manager Role should be able to move the issue to Ready to Deploy under any conditions. 

Exclude from Controls can be blank. Its a checkbox field. 

Below is how I have the settings

Screenshot 2023-05-17 at 9.12.32 AM.png

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 17, 2023

Hello @Nicole Pomponio 

I think I overcomplicated it.

I think that this will work for you, but I recommend that you try it in a test project first.

Substitute values accordingly

Trudy Claspill Checkbox >> Exclude from DC

Administrators >> Deployment Manager

Option 1 >> Exclude

Screen Shot 2023-05-17 at 4.30.33 PM.png

This should work such that

- anybody can transition the issue if Exclude from DC is set to Exclude

- users in the Deployment Manager role can transition the issue always.

Nicole Pomponio May 17, 2023

I’ll test this out! For now, I have it working just by switching my Exclude conditions so that Deployment Manager and Exclude = blank are grouped, Exclude = True was separate, and it worked

Thank you!!

Like Steven Hill likes this

Suggest an answer

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

Atlassian Community Events