Set work item security level automatically with Jira Automation

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

See how to automatically set security when assigning issues to specific users.

Solution

Prerequisites

Before we create the rule, we'll want to make sure all these requirements are met.

  • At least 1 security scheme is associated with the project.

  • The rule Actor is a member of the target Security Level (if keeping Automation for Jira as actor, add the atlassian-addons-project-access role to the security scheme).

  • The Actor has the Browse Projects, Edit Work Items, and Set Security Level permissions.

  • The Security Level field is on the Edit and View screens.

For full details on configuring work item security, please refer to our documentation.

Automation rule to set the security level based on the Assignee

Our example rule triggers when a work item is assigned to a user or list of users, but the automation trigger can be exchanged for any other trigger that matches your requirements.

  1. Visit your space, and select Space Settings > Automation > Create rule.

  2. Use the Work item assigned trigger.

  3. Select IF: Add a condition.

  4. Choose a Work item field condition.

    1. Select the Assignee field.

    2. Leave the condition as is one of (default).

    3. Choose the user(s) that should trigger this rule.

  5. Add an Action component to the rule.

  6. Select the Edit work item component.

  7. Select the Security level field.

  8. Choose the appropriate security level.

  9. Save and turn on the rule.

  10. Trigger the rule on a test issue and confirm the Security Level field is set as expected.

If you follow this rule outline, remember to choose assignees who belong to the security level you're setting. Otherwise, the assignee may not be able to see the work once the security level is set.

If the rule runs but security isn't set, the Actor almost always lacks Set Security Level or isn't a member of the target level — check the audit log for a permission warning.

Related article

Updated on August 11, 2026

Still need help?

The Atlassian Community is here for you.