Creating plans

Still need help?

The Atlassian Community is here for you.

Ask the community

If you're using the improved planning interface, this page is for you. If you're using live plans, head to Live plans (legacy).

Any plans you create in Advanced Roadmaps will have the improved planning interface enabled by default. Sample plan, with the improved interface

If you prefer to use the layout of live plans (any version from 2.0 to 2.27), you'll need to disable the improved interface in each of your plans. See Setting up the planning environment to know more.

There are loading limits to take note of when using plans. Loading limits restrict the number of issues that can be loaded into a plan, thereby preventing the schedule of a plan from becoming too large to process.

If a plan becomes too large, this can cause Jira Software to time out. To prevent this, you can consider creating multiple plans and spreading the work across these plans, or you can remove certain issues from the issue sources that you've connected to the plan.

Note the following loading limits in a plan:

  • Absolute issue limit: The number of issues you can load into a plan, which is 5000.
  • Hierarchy issue limit: The number of issues that can be displayed for each hierarchy level in the plan, which is 2000. This limit only applies when you're creating a plan; you will not be able to create a plan if the total number of issues exceeds 2000 for any of the hierarchy levels.

  • Project limit: The number of projects you can load into a plan, which is 100. This limit only applies when you're creating a plan; you will not be able to create a plan if the total number of projects in the plan exceeds 100.
  • Team limit: The number of teams you can access via shared team settings. The limit for the number of teams that a plan can directly display is 50. If you have more than 50 teams, some teams won't be displayed directly in the shared team settings page. To find teams that are not displaying, enter the team name in the search box.

Creating a plan

  1. In Jira Software, go to Plans (in header) > Create. The 'Create' page will be displayed.
  2. Select Plan Create.
  3. Give your plan a name.
  4. Select one of the privacy options from the privacy drop-down:
    • No restrictions – all users can view and access the plan
    • Private – only the creator of the plan can view, access, and edit the plan
    If you select private, only you can view, access, and edit the plan. No other user can view or even search for the plan, including Jira Software admins and system admins. You can change the privacy option as necessary.
  5. Click Next.
  6. Choose the issue sources (boards, projects, filters) that you want to use for your plan.
    • Out of the three (3) issue sources, we recommend that you use Scrum boards. This gives you the ability to manage sprints from those boards, plan the capacity of future sprints, and assign issues to sprints — all directly from your plan.
    • If you choose a Scrum board as one of the issue sources in your plan, you'll also be asked to choose how you want to estimate your issues. We recommend that you use story points.
    • See What is a plan to know more about issue sources.
  7. Click Next.
  8. Choose the releases that are relevant to your work, then click Next.
    You'll only need to choose releases if there are existing releases in Jira Software, that are associated with the selected issue sources. By choosing the relevant releases, the issues assigned to these releases will display in your plan.
  9. You can choose to accept the suggested teams that you want to include in your plan, or you can do either one of the following:
    • Configure the settings of the teams: agile method (Scrum or Kanban) and weekly capacity
      Note that for plans that have boards as issue sources, Advanced Roadmaps will suggest the velocity for the team. The suggested velocity will be based on past performance, i.e. if the team previously completed any sprints in the corresponding boards.
    • Delete a team that you don't need to include in your plan, by clicking more () > Delete.
  10. Click Next.

  11. Confirm the issues that you want to include in your plan by selecting the corresponding checkboxes.
    By default, all the issues are selected. Filter the issues by project, issue source, issue key, or issue summary as needed.
  12. When you've marked all the issues you need, click Done.


Updating the settings of a plan

You can update any of these settings at any time.

Rename a planHover over the name > enter a new name > click Enter.
Configure issue sources

Before you update the issue sources of a plan, note that changing the issue sources will affect the scope, releases, and teams in your plan. See Issue sources for more details. Any releases that have been created and saved to Jira will be also selected by default.

  1. In your plan, click settings () > Configure > Issue sources.

  2. Click Edit issue sources. This will display the 'Create plan' wizard.

  3. Select your issue sources from existing boards, projects, and filters, and then click Next.

  4. Select the releases to include in your plan, and then click Next.

  5. Select the issues to include as the scope of your plan, and then click Done.


Delete a plan

Click settings () > Delete.

Last modified on Jun 12, 2020

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.