Set work item security level automatically with Jira Automation

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

Summary

For sensitive projects, you may want all work to automatically set a security level to prevent data within it from being accessed by unauthorized users. Jira Automation can be used to set the security level of your work based on various conditions.

We'll provide an example where security is automatically set if an issue is assigned to a specific list of users.

Solution

Prerequisites

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

  • There needs to be at least 1 security scheme associated with the project

  • The Actor of the Automation Rule needs to be a member of the target Security Level

    • By default, Automation for Jira will be set as the Actor

    • If we want to keep Automation for Jira as the actor, the Project Role atlassian-addons-project-access must be added to the security scheme

  • The Actor of the automation rule needs to have the following permissions:

    • Browse Project

    • Edit Work Items

    • Set Security Level

  • The Security Level field needs to be added to the Edit and View screens for the project

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

Automation rule to set security level based on 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 project, and select Project Settings > Automation > Create rule

  2. Use the Work item assigned trigger

  3. Select IF: Add a condition

  4. Choose a Work item fields 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

If following this rule outline, remember to choose assignees that 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.

Updated on April 22, 2025

Still need help?

The Atlassian Community is here for you.