• Products
  • Documentation
  • Resources

Performance recommendations for your plan

your plan loads in three steps:

  1. Jira reads the data stored in your issues.

  2. It compares that data to any unsaved changes held in your plan.

  3. Then it runs calculations (such as capacity planning and dependencies) to generate your plan.

The larger and more complex your plan is, the more effort it takes to load your plan. So while we’re constantly optimizing the load times of plans, the best way to speed up your plan’s performance is to keep it as focused as possible.

Optimize your JQL

All JQL queries are not created equal. JQL uses a strict logic that does exactly what you tell it to do, whether or not it’s the most efficient way. These inefficiencies can add up, causing performance issues in your plans.

If you’re using a JQL query as part of your plan (whether it’s as part of a filter or custom field), make sure that it’s written in a way that’s not causing more churn in your plans. Learn more about how to optimize your JQL queries.

Remove issue sources

your plan can handle up to four issue sources with no problems. The impact of issues sources beyond this depends on their complexity. Alternatively, if you only need a handful of issues from an issue source, consider moving those issues to a different project or using exclusion rules to only pull in the relevant issues.

Learn how to add or remove issue sources from your plan.

Limits on number of issues

All plans have a soft limit of 5,000 issues. You can exceed this number, but the performance of your plan will begin to suffer. For this reason, we recommend that you remove unnecessary issues, or consider breaking larger roadmaps into two separate plans.

Learn how to set an exclusion rule on your plan.

Remove issues belonging to old releases

By default, your plan adds all releases and fix versions in a project regardless of when they’re scheduled to happen. These extra releases might technically be relevant to your plan, but realistically slow down your plan’s performance. This is why we recommend that you either delete old releases in Jira, or use exclusion rules to focus on issues belonging to specific releases in your plan.

Learn how to set an exclusion rule on your plan.

Remove excess sprints

As mentioned at the start of the page, capacity planning calculations are done entirely in your plan when you load it. The more sprints that are included in your plan, the more effort required, leading to longer load times.

To remove old sprints from your plan, use the Exclude any completed issues after field in the exclusion rules, or delete old sprints from your boards in Jira.

Additional Help