How to restrict editing of an issue in a specific status
プラットフォームについて: Cloud のみ - この記事は クラウド プラットフォームのアトラシアン製品に適用されます。
要約
This article provides the steps to allow only users belonging to specific groups or project roles to edit the issue at a given status.
For example, we want only the admins to be able to edit an issue once its moved to In Progress status.
A bug currently impacts the use of much of this functionality.
JRACLOUD-77632 - Getting issue details... STATUS
環境
Jira Cloud
ソリューション
This can be achieved using the workflow properties. Please follow the below steps:
- Go to Project --> Project settings --> Workflow --> Edit.
- Select the required status which has to be set as uneditable.
- Click on Properties. (Make sure to edit the status property and not the transition property).
- In the new window that comes up, set one of the following:
- To limit the edition based on Project roles:
- Property key = jira.permission.edit.projectrole
- Property value = ID of the target_role
- To limit the edition based on Groups:
- Property key = jira.permission.edit.group
- Property value = target_group
- To limit the edition for a specific user:
- Property key = jira.permission.edit.user
- Property value = target_user
- To limit the edition based on Project roles:
- If required, you can restrict all users (including admins) from editing the issue using the following property values:
- Property key = jira.permission.edit.denied
- Property value = leave empty
- Then publish the draft workflow.
How to get the ID of a project role:
When using the project roles in the above configuration, the actual names of the project roles won't work and you need to provide the ID of the project role.
To retrieve the ID, please navigate to Settings (cogwheel icon on the top right) > System > Project roles and click Edit against the project role whose ID you're looking for. The ID can now be copied from the URL.
Important information about using usernames in the above configuration
When using a username, jira.permission.edit.user might not work as expected. This is because the usernames were deprecated from the Jira UI due to privacy restrictions. The issue is that the "jira.permission.edit.user" property still expects usernames. We have an open bug to rectify this behaviour.
As a workaround, you may add the required user(s) to a group and use the group property stated above.