Jira limits
The Limits tool counts what Jira caps in each space and on the site, shows how close each count is to its cap and when it would get there at the current pace, and says what was added and removed. It reads Jira and changes nothing.
Before you start
Limits is for Jira admins. A Jira admin turns on its background checks in Limits settings. A daily pass reads the site's totals, lists the spaces, and counts again the spaces whose work items changed since the last reading, the spaces never counted and those at half a cap or more. A weekly pass counts every space, each permission scheme's grants and the locked fields.
What Limits counts
| Count | Cap |
|---|---|
| Custom fields in a space | 700 (not counted yet in team-managed spaces) |
| Work types in a space | 150 |
| Security levels in a space | 50 |
| Releases in a space | 15,000 (archived ones are not counted) |
| Components in a space | 10,000 |
| Grants of each permission in a permission scheme | 50 |
Jira refuses to add more once one of these is reached. Work items and spaces on the site have guardrails instead. Atlassian advises staying under them, but passing one blocks nothing.
The Limits page lists the counts by the share of their cap used, worst first, as a bar with the count, the cap and the share written beside it. Each count has its forecast (estimated), its history and a link to Jira's own screen. Jira's own admin screens stay the reference. Locked fields are part of the fields count, and their number is shown beside it.
These numbers are measured by TuneCraft's readings, from what Jira's API answers. Work items on the site are Jira's approximate count.
Options per field, workflows per workflow scheme, statuses per workflow and priorities per space need permissions TuneCraft does not ask for yet, so they are not counted. Role actors and roles per person are left out because they are about people.
The forecast
The forecast is a straight line through each day's count over the last 90 days. It needs 14 days of readings and a count that grows. Otherwise the page says so. It is an estimate.
Alerts
A count alerts a Jira work item when it passes 80% of its cap, when its forecast reaches the cap within 30 days (whatever its share), and when it reaches the cap. Each alerts once, and again only after the count went back under 75% of its cap and its forecast no longer reaches the cap within 45 days. The alert settings are shared with the usage alerts: see Run health, governance and usage.
The other pages
- Added and removed: how many custom fields, statuses, permission schemes, releases and components were added or removed between two readings, over the last 30 days and this week.
- Work items near caps: the work items that Jira's report says are over or near its per-work-item limits: comments, attachments, links, worklogs, watchers and the size of rich text. TuneCraft reads the report as the Jira admin who opens the page, at most once a day, within this hour's points for work you start. Work items that are Done are left out.
- API quota: TuneCraft's own Jira points per day, and Jira's refusals. It is also on App cost.
Beside each cap, and beside releases, components and work items on the Limits page, are the flows that add to it, with about how many a month: what each run adds, times its runs (estimated).
What it keeps
Each count's latest value, a row for each day a count changed, and how many were added and removed each day, for 400 days. Ids and numbers only. Names are read from Jira, as you, when you open a page.
Questions about the app? Write to info@plugincraft.ca.