Summary
Keychain - Delegation for Jira custom fields can be used in Jira Permission Schemes using the User Custom Field Value option.
Permissions
Keychain custom fields should only be used with permissions marked as Supported below.
Permissions marked as unsupported either rely on Jira search indexes or they are not bound to field values of an issue. Using Keychain custom fields for unsupported permissions might produce unpredictable results.
|
Permission |
Supported ? |
Details |
|---|---|---|
|
Project Permissions |
|
|
|
Administer Project |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Browse Project Archive |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Browse Project |
No |
Keychain custom fields successfully control this permission and determine who can open an individual issue's view screen. On the other hand, Jira searches are performed on indexed values and searches will return inaccurate results if a Keychain field is used for this permission. Issue Security Schemes behave similarly so more details can be found in: Using Keychain Custom Fields in Issue Security Schemes |
|
Edit Sprints |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Manage Sprints |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Service Desk Agent |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Start/Complete Sprints |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
View Development Tools |
Supported |
|
|
View Readonly Workflow |
Supported |
|
|
Issue Permissions |
|
|
|
Archive Issues |
Supported |
|
|
Assignable User |
Supported |
|
|
Assign Issues |
Supported |
|
|
Close Issues |
Supported |
|
|
Create Issues |
No |
This permission is not bound to a single issue's field values so any kind of user custom field (Keychain or other) should not be used on this permission. |
|
Delete Issues |
Supported |
|
|
Edit Issues |
Supported |
|
|
Link Issues |
Supported |
|
|
Modify Reporter |
Supported |
|
|
Move Issues |
Supported |
|
|
Resolve Issues |
Supported |
|
|
Restore Issues |
Supported |
|
|
Schedule Issues |
Supported |
|
|
Set Issue Security |
Supported |
|
|
Transition Issues |
Supported |
|
|
Voter and Watcher Permissions |
|
|
|
Manage Watchers |
Supported |
|
|
View Voters and Watchers |
Supported |
|
|
Comment |
|
|
|
Add Comment |
Supported |
|
|
Delete All Comment |
Supported |
|
|
Delete Own Comment |
Supported |
|
|
Edit All Comment |
Supported |
|
|
Edit Own Comment |
Supported |
|
|
Attachment |
|
|
|
Create Attachments |
Supported |
|
|
Delete All Attachments |
Supported |
|
|
Delete Own Attachments |
Supported |
|
|
Time Tracking |
|
|
|
Delete All Worklogs |
Supported |
|
|
Delete Own Worklogs |
Supported |
|
|
Edit All Worklogs |
Supported |
|
|
Edit Own Worklogs |
Supported |
|
|
Work on Issues |
Supported |
|
If you can't see Keychain fields in Permissions Schemes
Only Jira custom fields that have a Search Template and that are indexable/searchable can be used in Jira Permission Schemes.
To use these fields in Permission Schemes, make sure that there is a Search Template set for the field, as described in Using Keychain Custom Fields for Search.