Automation | Set "Issue Security Level" via Automation for JIRA

Still need help?

The Atlassian Community is here for you.

Ask the community

robotsnoindex

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

Summary

This KB covers how we can set issue security level using Automation for JIRA.

Prerequisites 

The below requirements need to be met before we can setup a rule to set "Issue Security"

  • There needs to be at least 1 security scheme associated with the project.
  • The Actor of the Automation Rule (By Default: Automation for JIRA) needs to be a member of the target Security Level. The Automation for Jira is not a general user as we see in the "User Management" page. Hence, we need to add the "Project Role (atlassian-addons-project-access)" to the security scheme.
  • The Actor of the automation rule needs to have the below permissions:
    • "Browse Projects" Permission
    • "Edit Issue" Permissions
    • "Set Security Level" Permission
  • The "Security Level" field needs to be added to the "Edit" and "View" Issue Screens from the Screen configuration of the Project.

In the solution part, there is a simple automation rule demonstrating how we can set the issue security scheme every time "Assignee" changes to a "Specific User"

Environment

  • Jira Cloud
  • Project Type ("Company Managed Software Projects", "Company Managed Business Projects", "Company Managed Jira Service Management")

Solution

Automation Rule Demonstrating the automatic association of Security Level on issues based on one condition.

Last modified on May 30, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.