Hello,
I am trying to create automation for security levels for a particular request type.
After creating the automation thread, and then testing, the error message I get in the automation audit log is:
"No fields or field values to edit for issues (could be due to some field values not existing in a given project):"
I have added "Security Level" to the screen scheme my project uses - to "create issue," "view issue," and "edit issue" screens.
I've verified that the "Security Level" field is appearing on the project by looking under "Find Your Field."
What am I missing? Why should I receive the error message above if the field is added to the project?
Thank you!
Thank you Fazila, that's it! I set myself as the actor and it worked perfectly. Really appreciate your help here, I was banging my head against a wall.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Happy to help! The issue security scenarios are tricky indeed :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Fazila - I realized this hasn't quite been resolved, as assigning myself as the actor means that only tickets I submit will face the desired automation.
If the desired outcome is for tickets entered by any / all employees go through the automation and be assigned the security level, does that mean that any / all employees need to be added to be able to edit issue security permissions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can disregard the above! I added 'Automation for Jira' as a single user to the security level I'm automating for - and it worked! Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to great meetings, with less work. Automatically record, summarize, and share instant recaps of your meetings with Loom AI.
Learn moreOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.