Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Search for issues, navigate to your work, use advanced search, and work with your search results.
Plan and view work across multiple teams, projects, and releases using Plans.
This page refers to the advanced planning features that only available as part of Jira Software Cloud Premium and Enterprise.
We have a separate section for documentation about the project timeline that’s included in all Jira Software projects. Go to the documentation for project-level roadmaps in Jira Software.
To prevent Jira Software from timing out, there are limits on how how much data your plan can include. Some limits can’t be exceeded, like the issue limits, while others negatively impact your plan’s performance or usability. Learn how to improve the performance of your plans.
A single plan can load up to 5,000 issues At that point, you’ll begin to see warnings that your plan performance will be affected.
For larger projects, consider spreading the work across multiple plans.
While there is no enforced limit on the number of teams that can be included in your plan, we recommend adding no more than 50 teams. If you add more, some teams won't display on the Teams tab and you’ll need to enter the team name in the search box.
Limits on 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. However, your plan can only span 100 projects, including those that are pulled in as part of boards and filters.
If you hit the project limit in your plan, try adjusting your board or filter’s JQL to include fewer projects. 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.
Was this helpful?