The Set security level on current issuepost 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.
Provide the ID number of a security level defined in a security scheme associated with the project in the ID field (e.g. 10000)
Select if the post function should be executed by the current or another user in the Action executor field (see User Permissions below)
If you have selected Current user option, the post function will be executed by the user making the workflow transition
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
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”)
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
Select if The executor has to be or can’t be a member of a certain Jira user group or project role
Select a Jira user group in the Group field if Group was set in the member of a field
Select a project role in the Project role field if Project role was set in the member of a field
Activate the Fire event option if you want Jira to fire the ISSUE_UPDATED event
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
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.
The issue is transitioned to the stage in which it should have restricted access e.g. invoicing, pricing, etc.