Setting up an Automation to deny a Field Change based on Roles

[Justin Görmez]

Hey,

i am trying to set up an automation to basically deny setting a specific property to the Issue Type "Bug". This Property shall only be set by someone with a Specific Role, and all other Roles should not be able to set this Property, but it should be visible at all times. I tried with an Automation that basicly checks for the Role of the Initiatior of the Field Change, but then i can only solve this problem half. If i activate one rule, so that the Field will not change in one direction it works just fine, but as soon as i activate the second automation so it cannot be changed in any direction, those 2 Automations get into an Automation Loop and i end up with it completely not working again.  

[Aaron Geister]

@Justin Görmez 

Welcome to the community. 

If you are looking to set a condition or validator for a custom field, it is best to do so with in the workflow. 

Would you have access to edit the workflow. I would add the condition or validator to the field, and this should work. I do lack some of what you are trying to do so specifics would help. 

Please tell us more and or give us a screenshot to see if we can help more. 

[Marc - Devoteam]

Whenever you ask for help with an Automation Rule it will help us to help you if you provide:

1. screen images that show your entire rule.

2. screen images showing the details of the step(s) that aren't generating the result you expect.

3.screen images showing the Audit Log details for the rule execution.

4.screen images showing the relevant data in an image that is part of the rule execution.