Documentation for JIRA 4.1. Documentation for other versions of JIRA is available too.
Please note that the following instructions do not provide a complete solution to Field Level Permissions, but allow to control who can edit particular fields. This is achieved with the help of Transition Conditions in a Workflow.
These instructions do not provide a solution for restricting who can see the values of fields. Users who have permissions to view an issue, will be able to see the values of these fields for that issue, search by them, receive notifications when these fields change, etc.
Before you read these instructions, it is important to have a good grasp of how Workflows fit into JIRA. A good source of information on Workflows can be found in JIRA's documentation: Configuring Workflow
You should also familiarise yourself with how Screens work in JIRA: Configuring Fields and Screens
Please note that the ability to edit some System Fields is already protected by a permission:
System Field |
Permission |
---|---|
Fix Version |
Resolve Issue |
Assignee |
Assign Issue |
Due Date |
Schedule Issue |
Reporter |
Modify Reporter |
Security Level |
Set Issue Security |
The easiest thing to do for the above fields is to use Permission Schemes to control who can manipulate them. For more information on permissions please see: Managing Project Permissions
However, if the field you are trying to protect is not already protected by a permission, e.g. a custom field, you can use a workflow transition. This transition will allow certain users to only edit certain items of an issue without transitioning to another step of the workflow.
Please follow these instructions:
Please note that the above setup will not allow the protected fields to be populated when issues are created or edited.