Goal:
When a ticket is created, automatically change the security level according to issue type.
Problem:
When creating the rule in automation, the "Security Level" field under "Edit issue fields" is not showing the proper security levels from the Issue Security Scheme that is set for the project, so I cannot set the appropriate security levels with automation.
The only options I see are "All users" or "Default"
I have followed the steps laid out in this knowledge base article:
I have an issue Security Scheme called "HR Scheme".
"HR Scheme" has three security levels:
1. "Default" (is set as the default security level)
Access to: Reporter, Group (HR), Project Role (atlassian-addons-project-access)
2. "Equipment recovery"
Access to: Reporter, Group (HR), Group (Systems), Group (Ops), Project Role (atlassian-addons-project-access)
3. "Offboarding tickets"
Access to: Reporter, Group (HR), Group (Systems), Project Role (atlassian-addons-project-access), Single User (myself)
The actor for the rule is "Automation for Jira".
Under Project Settings>Access>Issue Security, I see the above Security Scheme and Security Levels, as intended.
I added myself to one of the Security levels to see if that was part of the problem.
Under Project Settings>Access>People and Access, I am listed as the Administrator of the project.
Under Project Settings>Access>Project Permissions, "Automation for Jira" and "atlassian-addons-project" is added to the "Browse Projects" Permission, "Edit Issue" Permissions, and "Set Security Level" Permission
Under Project Settings>Request Management>Screens, the field "Security Level" is added to all screens.
I would appreciate any assistance or ideas.
Thanks
Oh, I figured it out...
I just needed to type in the Security Level name manually.
It doesn't automatically appear in the drop down until you start typing the name.
Online 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.