Jira Automation Fails to Set Security Level Field During Issue Transition From Jira Automation

[Ahmad Saleem]

I've created a jira service management project and I'm trying to use Jira Automation to set the Security Level field during a transition, but the automation rule fails with the following error:

The fields set during transition aren't available. Fields ignored:

Security Level (security)

Here’s what I’ve tried so far:

1. I’ve confirmed that the Security Level field is accessible and editable on the issue screens.
2. The automation user (or actor) has the Set Issue Security permission.
3. The desired security level is valid for the issue and included in the Issue Security Scheme.
4. I attempted to use the Advanced JSON Editor in automation to set the field like this:
   
   
   

{ "fields": { "security": {"name": "Level2"} } }

Despite these steps, the rule still fails to set the Security Level field. Is there something specific about the Security Levelfield in Jira Automation that I might be missing?

[Rilwan Ahmed · Accepted solution]

Hi @Ahmad Saleem ,

Welcome to the community !!

You can try the inbuilt action  Edit issue fields --> Security level  in automation rule to set it.

Please note: Issue-level security isn't editable on the Free plan. Upgrade for advanced access control.

[Ahmad Saleem]

thanks this worked for me

[Sebastian Krzewiński]

Hi @Ahmad Saleem 

Please check if rule actor is able to set security level and is able to see all levels or at least levels that you want to set. By default security level has own permission in permission scheme and Jira allows changing sec level to levels that are available for user.

Regards,

Seba