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 ProjectNoThis 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 ArchiveNoThis 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 ProjectNo

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 SprintsNo

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 SprintsNoThis 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 AgentNoThis 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 SprintsNoThis 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 ToolsSupported
View Readonly WorkflowSupported
Issue Permissions

Archive IssuesSupported
Assignable UserSupported
Assign IssuesSupported
Close IssuesSupported
Create IssuesNo

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 IssuesSupported
Edit IssuesSupported
Link IssuesSupported
Modify ReporterSupported
Move IssuesSupported
Resolve IssuesSupported
Restore IssuesSupported
Schedule IssuesSupported
Set Issue SecuritySupported
Transition IssuesSupported
Voter and Watcher Permissions

Manage WatchersSupported
View Voters and WatchersSupported
Comment

Add CommentSupported
Delete All CommentSupported
Delete Own CommentSupported
Edit All CommentSupported
Edit Own CommentSupported
Attachment

Create AttachmentsSupported
Delete All AttachmentsSupported
Delete Own AttachmentsSupported
Time Tracking

Delete All WorklogsSupported
Delete Own WorklogsSupported
Edit All WorklogsSupported
Edit Own WorklogsSupported
Work on IssuesSupported


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




  • No labels