Custom field permissions Fields Permission Schemes are created within Field Configuration Custom Fields Permission Schemes, which are then assigned to specific projects.Project permissions are able to be granted based oncustom fields within each field configuration separately.
Secure Custom Fields Permissions may be granted on the basis of:
- Individual users
- Groups (including 'Any logged in user' and 'Anonymous')
- Project roles
- Issue roles such as the 'Reporter', 'Project Lead' and 'Current Assignee''Anyone' (e.g. to allow anonymous access)
- JIRA Permissions inherited from JIRA Permission Schemes
- A (multi-)user picker custom field.
- A (multi-)group picker custom field. This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.
The following table lists the different types of project permissions and the functions they secure. Note that project permissions can also be used in workflow conditions.
Field Permissions | Explanation |
|---|---|
View |
Field Value | Permission to |
Edut Restrictions
Permission to be assigned issues. (Note that this does not include the ability to assign issues; see Assign Issue permission above).
History View Restrictions
Permission to close issues. (This permission is useful where, for example, developers resolve issues and testers close them). Also see the Resolve Issues permission.
Create Issues
Permission to create issues in the project. (Note that the Create Attachments permission is required in order to create attachments.) Includes the ability to create sub-tasks (if sub-tasks are enabled).
Delete Issues
Permission to delete issues. Think carefully about which groups or project roles you assign this permission to; usually it will only be given to administrators. Note that deleting an issue will delete all of its comments and attachments, even if the user does not have the Delete Comments or Delete Attachments permissions. However, the Delete Issues permission does not include the ability to delete individual comments or attachments.
Edit Issues
Permission to edit issues (excluding the 'Due Date' field — see the Schedule Issues permission). Includes the ability to convert issues to sub-tasks and vice versa (if sub-tasks are enabled). Note that the Delete Issue permission is required in order to delete issues. The Edit Issue permission is usually given to any groups or project roles who have the Create Issue permission (perhaps the only exception to this is if you give everyone the ability to create issues — it may not be appropriate to give everyone the ability to edit too). Note that all edits are recorded in the Issue Change History for audit purposes.
Link Issues
Permission to link issues together. (Only relevant if Issue Linking is enabled).
Modify Reporter
Permission to modify the 'Reporter' of an issue. This allows a user to create issues 'on behalf of' someone else. This permission should generally only be granted to administrators.
Move Issues
Permission to move issues from one project to another, or from one workflow to another workflow within the same project. Note that a user can only move issues to a project for which they have Create Issue permission.
Resolve Issues
Permission to resolve and reopen issues. This also includes the ability to set the 'Fix For version' field for issues. Also see the Close Issues permission.
Schedule Issues
Permission to schedule an issue — that is, to edit the 'Due Date' of an issue. In older versions of JIRA this also controlled the permission to view the 'Due Date' of an issue.
Set Issue Security
Permission to set the security level on an issue to control who can access the issue. Only relevant if issue security has been enabled.
view the current field value. | |
Edit Field Value | Permission to update the field value. |
View Field History | Permission to view previous secure field values. |
| Set field value on Create issue screen | The name is so long, it's self-explanatory  |
| Delete history | Permission to delete field change history. |
| Read masked field | Permission to read the value of the masked field. |
| Decrypt field value | Permission to decrypt the value of the password field. |
What is a Permission Scheme?
A permission scheme is a set of user/group/role assignments for the field permissions listed above. Secure custom fields differ from any other custom fields in having permission schemes. One permission scheme can be associated with multiple custom fields.
Why Permission Schemes?
With permission schemes, you do not have to set up permissions individually for every custom field. Once a permission scheme has been set up, it can be applied to all custom fields that have the same type of access requirements.
Notice: While choosing "Set issue field value on Create issue screen" permission, take under consideration that it will only work for a Single User, Project Lead, Project Role, and Jira Permission.
Creating a Permission Scheme
- Log in as a user with the 'JIRA Administrators' global permission.
- Choose
> Issues. Select Custom Fields Permission Schemes to open the Permissions Schemes for Custom Fields page, which displays a list of all permission schemes in your JIRA system and the custom field that use each scheme.
Tip Keyboard shortcut: 'g' + 'g' + start typing 'customs fields permission schemes' - Click the 'Add Scheme' link.
- In the 'Add Scheme' form, enter the name for the scheme, and a short description of the scheme. Click the 'Save' button
- You will return to the 'Permissions Schemes for Custom Fields' page which now contains the newly added scheme.
Adding Users, Groups or Roles to a Permission Scheme
- Log in as a user with the 'JIRA Administrators' global permission.
- Choose > Issues. Select Custom Field Permission Schemes to open the Permissions Schemes for Custom Fields page, which displays a list of all permission schemes in your JIRA system and the custom fields that use each scheme Tip Keyboard shortcut: 'g' + 'g' + start typing 'custom field permission schemes'
- Locate the permission scheme of interest and click its name (or click the 'Permissions' link in the 'Operations' column) to show a list of permissions.
Screenshot: Custom Fields Permissions
- Click the 'Add' link in the 'Operations' column, which displays the 'Add Permission' page.
- After selecting one or more permissions to add and who to add the selected permissions to, click the 'Add' button. The users/groups/roles will now be added to the selected permissions. Note that project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimize the number of permission schemes in your system.
Screenshot: Add New Permissions - Repeat the last 2 steps until all required users/groups/roles have been added to the permissions.
Deleting Users, Groups or Roles from a Custom Field Permission Scheme
- Log in as a user with the JIRA Administrators global permission.
- Choose > Issues. Select Custom Field Permission Schemes to open the Permissions Schemes for Custom Fields page, which displays a list of all permission schemes in your JIRA system and the custom fields that use each scheme. Tip Keyboard shortcut: g + g + start typing custom field permission schemes
- Locate the permission scheme of interest and click its name (or click the Permissions link in the 'Operations' column) to show the list of 'Custom Field Permissions'.
- Click the Delete link in the "Users / Groups / Roles" column next to the name of the user, group, or project role you wish to delete.
Associating a Custom Field Permission Scheme with a Custom Field
- Log in as a user with the JIRA Administrators global permission.
- Choose >Issues>Custom Fields. Tip Keyboard shortcut: g + g + start typing custom fields
- Select the field of interest and then choose one to open the dropdown menu and later on go to the Configuration page
- Click the Edit Permission Scheme to list available permission schemes, select the permission scheme you want to associate with the custom field.
- Click the 'Done' button to submit the form.
Another way:
- Log in as a user with the JIRA Administrators global permission.
- Choose >Issues>Custom Fields Permission Schemes Tip Keyboard shortcut: . start typing custom fields permission schemes
- Select the field of interest and choose the scheme you want to associate with the custom field.
Deleting a Permission Scheme
- Log in as a user with the JIRA Administrators global permission.
- Choose > Issues. Select Custom Field Permission Schemes to open the Permissions Schemes for Custom Fields page, which displays a list of all permission schemes in your JIRA system and the custom fields that use each scheme. Tip: Keyboard shortcut: g + g + start typing custom field permission schemes
- Click the Delete link (in the Operations column) for the scheme that you want to delete.
- A confirmation screen will appear. To delete click Delete otherwise, click Cancel.
- The scheme will be deleted and all associated custom fields will be automatically associated with the Default Permission Scheme. (Note that you cannot delete the Default Scheme for Permission.)
Copying a Permission Scheme
- Log in as a user with the JIRA Administrators global permission.
- Choose > Issues. Select Custom Fields Permission Schemes to open the Custom Field Permission Schemes page, which displays a list of all permission schemes in your JIRA system and the custom fields that use each scheme. Tip: Keyboard shortcut: g + g + start typing custom field permission schemes
- Click the Copy link (in the Operations column) for the scheme that you want to copy.
- A new scheme will be created with the same permissions and the same users/groups/roles assigned to them.