Jira automation to set security level not working: 'Failed to retrieve selections [...]'

Gabriel Aklin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2025

Hi 

In my jira project, we have a security scheme in place and we can already manually set security levels on individual issues. I am now trying to add a new automation rule to  my project: whenever i create a new issue, i want to have a specific security level assigned to it. 

When i select the automation element 'Set issue security level' and want to configure it, the dropdown to select the security scheme fails to load my security schemes. The error message below says: 'Failed to retrieve selection, please refresh the page and try again'.

Refreshing the page does not help. Does anyone have an idea what could be the problem?

I am a project admin. I can manually set the security level, create issues and overall administrate the project. I am not a jira administrator for my organisation nor have i created the security scheme myself. But i would assume that this does not have to be the case for me to be able to set the automation as described above.

Thanks for any help in advance!
Gabriel

2 answers

1 accepted

0 votes
Answer accepted
Benjamin Črnjak
Contributor
January 24, 2025

Hi @Gabriel Aklin

I'm not 100% sure on this, but I've run a quick test on my test site.

Within new automation rule, when I add Set security level action, here are two scenarios I'm facing:

 

1. Using Admin account - Jira ORG, Product and Project admin:

I'm able to select any security scheme, and facing no issues at all.

 

2. Using test account - only Project admin (no ORG or Product admin permissions)

In this case, I'm facing the same error you've explained in your post.

 

Screenshot_2025-01-24_14-20-53.png

 

As you're only a Project admin, that means you don't have access to all security schemes. Maybe it's a bug that rule won't show at least security scheme that's used in your project, but given that the menu loads all security schemes, including those you don't have access to, probably that's the reason why you get this error.

 

Hope that helps.

Benjamin

Gabriel Aklin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2025

Hi @Benjamin Črnjak 
Thanks for the quick response! I didn't think this could actually be the problem but in this case i will reach out to our organizational admin.

In my opinion, it should at least load the schemes which are already being used in my project. I can already use it manually, so I should be able to add it to my automation.

Thanks a lot for the help!

Gabriel

Like Benjamin Črnjak likes this
1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 24, 2025

Hi @Gabriel Aklin -- Welcome to the Atlassian Community!

This is a known limitation for rules, and here is a suggestion to allow Project Admins to see the security levels for the rule action:

https://jira.atlassian.com/browse/AUTO-1055

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events