Get Started

Learn how to access the Permission Editor.

Accessing Permission Editor

The Customfield Editor for Jira enables normal users to edit options of a customfield without beeing part of the jira-administrators group. Therefore the Jira administrator needs to grant permissions on customfields via the Permission Editor to normal users. To access the Permission Editor, follow the steps below:

Note: The app is not intended to create custom field contexts. Please setup your fields and contexts via the Jira admin interface in the top right corner: Settings > Issues > Custom Fields.

  • Select in the Jira top navigation bar Expand Sidebar > Apps > Customfield Editor for Jira.

  • The App page will appear and show you a list of customfields.

Note: Atlassian has introduced a new navigation in 2025. See how you can access the Permission Editor in the Jira navigation pre 2025 .

  • Select in the Jira top navigation bar Apps > Customfield Editor for Jira.

  • The App page will appear and show you a list of customfields.

Note: Atlassian has introduced a new navigation in 2025. See how you can access the Permission Editor in the new Jira navigation .

  • Now you can click on the  usergroup icon to open the Permission Editor slider.

Note: For all actions described in this Administrator Guide you need Jira administrator privileges. Normal users will not see the  usergroup icon.

Supported Field Types

Currently the app supports the following Jira built-in field types:

Select List (single choice)
Represents a list of options. Has a single default value.

Select List (cascading)
Represents a list of options. Each option can have childoptions. Has a single compound default value consisting of a parent option and a child option.

Select List (multiple choices)
Represents a list of options. You can select multiple options. Has multiple options as default value.

Checkboxes
Represents a list of options. You can select multiple options. Has multiple options as default value.

Radio Buttons
Represents a list of options. You can select one single option. Has a single option as default value.

Rate Limits

Since the Cloud app is written in Forge we have to work with limited execution time and limits on how many API request we can make. Therefore the following limits are currently in place to avoid timeouts and slow response times of the App:

User view:

  • list customfields:
    • pagination without filter: Maximum number of 150 fields will be displayed. (=max 3 API request per page, ordered by field name)
    • pagination with filter: Maximum number of 150 fields will be displayed. (=max 3 API request per page, ordered by field name, filter via memory)
  • list contexts of field:
    • pagination without filter: max 300 contexts will be displayed. (=max 3 API request per page, order implicit)
    • pagination with filter: max 300 contexts will be displayed. (=max 3 API requests, order implicit, filter in memory)
  • list options of context:
    • Maximum number of 1,000 options displayed per context. (=max 10 API requests, ordered by internal order)
    • Maximum number of 150 default option values per field are displayed (only for multi select, radio field types) are displayed (=max 3 API requests)
  • Note that this applies to fields and contexts the user has permissions granted to

Admin view:

  • list customfields:
    • pagination without filter: All fields will be displayed. (=1 API request per page, ordered by field name)
    • pagination with filter: All fields will be displayed. (=1 API request per page, ordered by field name, filter via API)
  • list contexts of field:
    • pagination without filter: All contexts will be displayed. (=1 API request per page, order implicit)
    • pagination with filter: max 300 contexts will be displayed. (=max 3 API requests, order implicit, filter in memory)
  • list options of context:
    • Maximum number of 1,000 options displayed per context. (=max 10 API requests, ordered by internal order)
  • permission editor:
    • Maximum number of 2,000 users/groups can be granted on a single field context (=context permission) or to a field (=global permission).
    • Maximum of 15 users/groups will be displayed with pagination (=1 API request per page)

Permissions and Storage:

  • group index:
    • The groupIndex can store max 10.000 unique groups with assigned permissions overall (currently two forge storage kvs entries with max 240KB each)
  • user groups for permission checks:
    • A single user can have max 100 groups. If he is assigned to more than 100 groups only the first 100 will be used to perform the permission checks and the rest will be cut off. Why? Permission checks will get slow if user has more groups and all these groups have to be queried for and checked againt permissions for every user interaction.
  • permission storage:
    • A single global or context field permission can consist of max 2000 userIds and 2000 groupIds. (<240kb of one storage API KVS entry)
    • A single global context user permission or group permission can consist of max 2000 overall fieldIds/conxtextIds (Other way round) → Meaning: one group can be assigned to max 2000 custom fields; one user can be assigned to max 2000 custom fields; (<240kb of one storage API KVS entry)

We plan to increase this limit once we see there are no performance or rate limit problems in production. But keep in mind that we can also lower these limits anytime should we see degraded performance in production.

Note: Should you experience problems with these limits, please reach out to our support and we try to work out a solution.

User Guide - Previous
Field Editor
Next - Administrator Guide
Permission Editor
 
Data Center