Limits and known limitations¶
Limits¶
| Area | What | Limit |
|---|---|---|
| Link rules | Entries (roles, groups and users together) for one link type | 30 |
| Link rules | Different groups in one project's configuration | 30 |
| Link rules | Different users in one project's configuration | 30 |
| Link rules | Issue types with their own rules | 50 |
| Link rules | Allowed target projects | 50 |
| Link window | Links added before saving | 100 |
| Links field | Links chosen on the create screen | 100 |
| Links field | Text shown on the issue view | 100 characters |
| Picker fields | Length of the JQL filter | 2,000 characters |
| Picker fields | Issues picked in one field | 100 |
| Picker fields | Links remembered by one picker on one issue | 300 |
| Activity log | Entries shown on one issue | 100 most recent |
| Activity log | Database for the whole site | 1 GB (Atlassian's limit for an app on one site) |
| Technical account | Projects checked when looking for projects that share a permission scheme | 200 |
Known limitations¶
- Jira's built-in linking is not restricted by the app. The rules apply to the app's side panel and fields. To stop users from linking around the rules, remove their "Link Issues" permission and turn on the technical account.
- Links chosen on the create screen are created by the app's account. They are created a few seconds after the issue is saved, so in the issue's History their author is the app; the person who created the issue is shown in the activity log. If a link cannot be created, the reason is shown in the activity log of the new issue, not in the create dialog.
- The issue page reloads after a change made in a field. Jira lets only some app modules refresh its "Linked work items" section, and custom fields are not among them. To show the new links, the page reloads once when you close the field after saving.
- A picker shows only its own links. Links of the same type made elsewhere are visible in Jira's "Linked work items" section, not in the picker. See Picker fields.
- The activity log covers the app only. Links made through Jira's built-in section are listed in the issue's History, not in the activity log.
- Fields appear only on the project's screens. Creating a custom field is not enough; it must be added to the screens the project uses.
- The side panel is off by default. A project administrator turns it on per project.
- Team-managed projects. The app cannot add its permission entry to a team-managed project's permissions, because Jira does not allow it. The app's account normally has its permission through the app role.
- Shared permission schemes. Removing "Link Issues" in a scheme affects every project that uses the scheme.
- Issue search matches whole words and the beginnings of words. Jira's text search finds "front-end fix" when you type "front" or "end", but not "ront" or "frontend". Search by issue key for an exact match.
- New custom fields. A custom field created less than five minutes ago may not be picked up yet when the first issues are created with it.