Performance recommendations for your plan

When you open a plan, Jira loads work-item data then combines it with unsaved plan changes. The amount and shape of that data affect loading and interaction times.

The steps below can help keep a plan focused.

Review the work included in your plan

A plan can load up to 10,000 work items. See limits on plan size for work-item, space, and team guidance.

Review your work sources and exclusion rules to include the work you need for planning. Removing irrelevant work may help responsiveness. Splitting a large plan into multiple smaller, more focused plans can help with performance and keeping under the work item limits.

Review queries and work sources

Check that the boards and filters used by your plan select the intended work. Review JQL optimization recommendations and narrow queries where that fits your planning needs. A source’s complexity matters as well as its size.

Focus on relevant releases and sprints

Historical work and its associated releases and sprints can add bloat and slow down your Plan, if it is not data you want to currently see. Review exclusion rules, including the setting for completed work, to focus on the period you need. Choose exclusions carefully so that work needed for planning remains available.

Start with changes to plan scope rather than deleting releases or sprints used elsewhere in Jira.

 

Still need help?

The Atlassian Community is here for you.