Set security level on current issue

Overview

The Set security level on current issue post function allows you to set the issue security level defined in a security scheme associated with the project on the current issue when a workflow transition is executed.

Configuration

  1. Provide the ID number of a security level defined in a security scheme associated with the project in the ID field (e.g. 10000)

  2. Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)

    1. If you have selected Current user option, the post function will be executed by the user making the workflow transition

    2. If you have selected Another user option, provide a user in the User field, so that the post function will be executed by this user

  3. Activate the JQL condition option and define the JQL query that has to be met by the issue in order to execute the post function (e.g. “type = Bug and Priority = Blocker”)

  4. Activate the Executor condition option if you want the post function to be executed only if the user is or isn’t in a certain Jira user group or project role

    1. Select if The executor has to be or can’t be a member of a certain Jira user group or project role

      1. Select a Jira user group in the Group field if Group was set in the member of a field

      2. Select a project role in the Project role field if Project role was set in the member of a field

  5. Activate the Fire event option if you want Jira to fire the ISSUE_UPDATED event

  6. Activate the Send notification option if you want Jira to send the notification according to the configured notification scheme. The option requires the Fire event option to be enabled in order to send the notification

User Permissions

The user set as Action executor in point 2 needs to have the Browse Projects and Set Issue Security permissions in the project of the issue in order to execute the post function.

Use cases

  • The issue is transitioned to the stage in which it should have restricted access e.g. invoicing, pricing, etc.