Limits
This page lists the limits you can reach in FieldCraft, and what you can do when you reach one.
Every limit applies to one Jira site, unless the row says otherwise. You can't change any of them in the app.
Calculationβ
| What | Limit | What you can do |
|---|---|---|
| Background work | 10,000 Jira API points per site in each UTC hour. Work that doesn't fit waits for the next hour, and nothing is lost | Give a reindex a narrower JQL scope so it finishes sooner. Opening a work item never waits for this budget. See Hourly calculation budget |
| Calculation while you open a work item | 10 seconds per field. A slower field shows its stored value and finishes in the background | Open the work item again a little later |
| Space recalculation by a space admin | Once an hour after the last finished one, and at most 2 spaces waiting on the site | Wait, or ask a Jira admin: Jira admins aren't limited |
| Parent values after a child changes | 20 seconds after the last change to its children, and at most 5 minutes after the first one | Wait for the children to settle. Rollup and parent counts follow on their own |
| Children updated after a parent changes | 500 work items per change, for Parent Field types | Recalculate the other children with a reindex |
| Fields that read other work items | Read again on the work item view at most every 15 minutes. This applies to Parent Field types, Jira expression types, Rollup, and Calculated Metrics that count watchers, votes or open links | Run a reindex to update search and lists at once |
Recalculationβ
Hourly refreshβ
| What | Limit | What you can do |
|---|---|---|
| Hourly refresh of values that still count | Every hour while a value has counted under 7 days. Every 6 hours from 7 to 30 days. Once a day after 30 days, or while the work item is in a Done status | Open the work item. Its view always shows the current value. See How values stay current |
| Countdown in the hourly refresh | Every hour within 7 working days of the deadline, less often further away | Open the work item for the exact value |
| Failures of an hourly refresh | Up to 50 per run, kept for 7 days | Run the hourly refresh again to see current failures |
Reindex and the activity logβ
| What | Limit | What you can do |
|---|---|---|
| Reindex jobs | 1 running and 5 waiting per site | Wait for one to finish, or remove a waiting one on the Calculation tab |
| Reindex scope | JQL of up to 10,000 characters | Split a long query into two reindexes |
| Failed work items of a reindex | Up to 1,000 per reindex, kept for 30 days | Select Retry N failed on the Calculation tab |
| Runs on the Activity tab | The 50 newest runs. Hourly refreshes stay for 7 days, reindexes for 90 days | See Follow runs on the Activity tab |
| Suggested updates | Work items created in the last 90 days, or still open | Select Change scope to reindex other work items |
Work calendarsβ
| What | Limit | What you can do |
|---|---|---|
| Calendars per site | 10 | Share one calendar between teams with the same hours, or delete calendars no field uses |
| Calendar name | 128 characters | Use a short name, for example 8/5 Berlin |
| Time zones | 1 per calendar | Create a calendar for each team's time zone |
| Working hours | One span per day, with any number of breaks | For a night shift, use 00:00 to 00:00 with a break from the shift's end to its start |
Field typesβ
| Field type | Limit | What you can do |
|---|---|---|
| Rollup | 10,000 children per work item, one level down | Split the work across several parents, for example smaller epics |
| Rollup | 3 source fields per field. The first one with a value counts on each child | Create a second Rollup field for other sources |
| Rollup | A day of time tracking is 8 hours | Store the value in Hours instead of Days |
| Parent Field types | Up to 4 work items up when you read from a level, such as the epic | Read from The parent or The grandparent (two levels up) |
| Parent Field types | 50 linked work items per value | Pick a link type with fewer links per work item |
| Comment Date, Commenter, Last Comment From | The first 1,000 comments of a work item | See Known limitations |
| Calculated Metrics | People who commented reads the first 1,000 comments | Count Comments instead |
| Previous Value | 255 characters. Longer text ends with β¦ | Use Previous Value for short values, such as a status or an assignee |
| T-Shirt Size | 7 sizes, on the slots XXS to XXL | Leave out sizes you don't need |
| T-Shirt Size | Labels of up to 12 characters, and points of 0 or more | Use short labels, such as Medium |
| Every field type | A name of up to 255 characters when you create it from a recipe | Put details in the description instead |
AI assistantsβ
| What | Limit | What you can do |
|---|---|---|
| A planned change | Expires after 15 minutes, and works once | Ask the assistant to plan the change again |
| Details in a field list | Contexts, screens and calculation state show only when 25 or fewer fields match | Ask about fewer fields, for example by name or type |
| Fields in one recalculation request | 20 | Ask for the other fields in a second request |
| Screens in one list | 100 | Ask for the screens of one space |
| A draft configuration to preview | 20,000 characters | Preview a smaller change |
Relatedβ
-
Known limitations: what FieldCraft doesn't do, and what to do instead.
-
Hourly calculation budget: how the 10,000 points an hour work.
-
Recalculate existing work items: fill in or update older values.
-
AI assistant tools: what each tool does and who can use it.