...
- Individual users
- Groups (including 'Anyone' group (e.g. to allow anonymous access)Any logged in user' and 'Anonymous')
- Project roles
- Issue roles such as the 'Reporter', 'Project Lead' and 'Current Assignee'
- 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.
...
Field Permissions | Explanation |
|---|---|
View Field Value | A permission Permission to view the current field value. |
Edit Field Value | A permission Permission to update the field value. |
View Field History | A permission 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 | A permission Permission to delete field change history. |
| Read masked field | A permission 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?
...
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, Reporter, Project Lead, Project Role, and Jira Permission.
...