Reference

Limits and performance

What the app handles and how fast, measured on a real Jira Cloud site. Narrow the filter when a plan reaches a limit; the chart tells you when it does.

A plan of 1,923 issues over sixteen months: the whole plan zoomed out, epics with their stories and subtasks, dependency arrows, releases and sprints — 1,923 issues in one plan, zoomed out to the whole of it; only the rows on screen are drawn.

Plans

	Limit or figure
Issues in one plan	10,000 (the chart says when a filter finds more)
Loading 1,000 issues	About 5 seconds after the page opens
Loading 10,000 issues	About 10 to 15 seconds; a bar shows how much has arrived
Scrolling	Smooth with 10,000 issues: only the rows on screen are drawn
JQL filter	2,000 characters
Refresh	When you come back to the tab after a minute away; the dashboard gadget every 15 minutes

Saved things

	Limit
Views per project (and on the Gantt page under Apps)	30
Baselines per project	20
Issues in a baseline	10,000
Holidays in the working calendar	500
Dependency link types	20
Milestone issue types	10

Changes

	Limit
Undo history	The last 50 steps, until you leave the page
Lag of a dependency	−365 to +365 working days
Issue name	255 characters
Import from MS Project	2,000 tasks per file
Exported image (PNG, SVG)	1,000 rows
Dashboard gadget height	240 to 900 pixels

Rovo agent

	Limit
Issues looked at for one answer	2,000
Issues in a drafted plan	30
Issues listed per point in an answer	15

Large moves are saved in parts and a busy Jira is retried, so a cascade of a hundred issues still finishes with an answer per issue. If something stops part-way, the chart reads back what Jira saved; see Troubleshooting.