要約

Workflow properties in Jira allow for you to limit which users can edit work items once they reach certain statuses.

In our example, once work reaches the Complete status, we want to limit which users can make changes.

Restrict editing based on user's role, group membership, or ID

There are three workflow properties that you can choose from to limit editing capability. Each accepts an ID, respective to the property type you choose. They are:

• jira.permission.edit.projectrole
• jira.permission.edit.group
• jira.permission.edit.user

Regardless of the property type you choose, the process for adding the property is the same:

Set workflow property to restrict editing

1. Visit your project
2. Select Project settings
3. [ワークフロー] を選択します。
4. Select Edit workflow for the relevant workflow based on work item type
5. Choose the Diagram editor, then select the status where you wish to restrict editing
   1. In our example, we select the Complete status
6. Select Properties
   1. Property key: jira.issue.edit.<your_choice>
   2. Property value: <ID matching your property choice>
7. Select Add
8. Return to the workflow editor and select Publish Draft

After publishing, only users that match your chosen to the project role, group, or single user ID can edit work items in the Complete status.

Other users will receive an error message if they attempt any edits, and the change won't be saved.

Retrieve IDs needed to set workflow properties

If you don't have the respective IDs readily available, they can be retrieved easily.

Retrieve project role ID

From inside Jira:

1. Visit  Settings > System
2. Select Project roles
3. Select View usage for your chosen project role
4. In your browser's address bar, the project role ID will be listed
   1. For example: https://<your_site>.atlassian.net/secure/project/ViewProjectRoleUsage.jspa?id=<project_role_id>

Retrieve group ID

1. Visit admin.atlassian.com
2. Choose your Organization if you have more than one
3. Select Directory
4. Select Groups
5. Choose the group you'd like to have editing capabilities
6. In your browser's address bar, the group ID will be listed
   1. For example: https://admin.atlassian.com/o/<org_id>/groups/<group_id>
   2. You can ignore the organization ID for the purposes of this article

Retrieve individual user ID

1. Visit admin.atlassian.com
2. Choose your Organization if you have more than one
3. Select Directory
4. Select Users
5. Search or scroll to find the user and select the linked text for their name
6. In your browser's address bar, the user's ID will be listed
   1. For example: https://admin.atlassian.com/o/<org_id>/users/<user_id>

Allow for multiple project roles, groups, or users to edit

If we want to allow multiple sets of users to be able to edit work items in a given status, we need to add multiple properties.

For example, if we want two project roles, we'd use these two properties:

• • Property 1:
    • Property key = jira.permission.edit.projectrole
    • Property value = <project_role_1_ID>
  • Property 2:
    • Property key = jira.permission.edit.projectrole.2
    • Property value = <project_role_2_ID>