Is there a concept of AND or OR concept in the new model of workflow restrictions

[Mahanth Prudhvi P]

Hi,

I do not understand the concept of AND or OR conditions in the new model. Can somebody guide me here.

Thanks!

Mahanth

[Ajay _view26_]

Hi @Mahanth Prudhvi P 

Welcome to the Atlassian Community.. Can you provide context? is it the workflow conditions you are referring to? .. 

Below is an example of usage of AND / OR conditions

• AND: All conditions/validators within the group must pass (e.g., User is in 'QA' AND Issue is 'High Priority').
• OR: Any condition/validator within the group must pass (e.g., User is 'Admin' OR User is 'Project Lead'). 

[Mahanth Prudhvi P]

Hi @Ajay _view26_ Thank you so much for your quick response . I got confused with the new UI ....haven't made any changes(Workflow restrictions) since the new update. Hence the confusion. Played around the feature for some and now I have got some idea about it.

Thanks!

Mahanth

[Trudy Claspill]

Hello @Mahanth Prudhvi P 

Here is an example.

Let us say you want to restrict a transition so that only the Reporter or Assignee can execute it. First, add that restriction.

It appears in the panel on the right. By default the system assumes you mean AND so only a user who is both the Reporter AND the Assignee could execute the transition.

If you want it to be an OR condition, pull down the MUST BE ALL and change it to Can be any of the following

You can combine different types of restrictions with an AND or OR condition by adding rules to the group.

You can combine multiple rule groups with an OR condition by adding child groups.

For instance in the old editor here is an example where the restriction is:

User must be the Reporter AND Assignee
OR
User must be in the Administrators project role.

Here is what it looks like in the new editor