Creating and deleting plans

A plan contains your issues, teams, and releases, and allows you to calculate the schedule of your projects. You can create any number of plans, which can be accessed by different users and groups.

Before you begin

There are loading limits to take note of when using plans in Portfolio for Jira. Loading limits essentially restrict the number of issues that can be loaded into a plan. 

Loading limits prevent the schedule of a plan from becoming too large for Portfolio for Jira to calculate. If a plan becomes too large, this can cause your Jira instance to time out. To prevent this, you can consider creating multiple plans and spread the work across these plans, or you can exclude certain issues from the sources that you're connecting to your plan.

Absolute issue limit
  • The amount of issues you can load into a plan.
  • The absolute issue limit is 5000.
Hierarchy issue limit
  • The amount of issues that can be displayed per hierarchy level.
  • The hierarchy issue limit is 2000.
Project issue limit
  • The amount of projects you can load into a plan.
  • The project issue limit is 100.
Team limit
  • The amount of teams that you can access via shared team settings.
  • The team limit 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.

(info) Note that these limits do not apply to classic plans. For classic plans, see Limits.

Creating a plan

  1. In your Jira application, go to Portfolio (in header) > Create. The 'Create' page will be displayed.
  2. Select  Create a plan, then click  Create plan.
  3. Give your plan a name, and choose one of the privacy options:
    • No restrictions (default option) – every Portfolio for Jira user will be able to access the plan
    • Private – only the creator of the plan has view and edit permissions

Note that if you select private, only you will be able to see or access the plan. The plan will not be viewable by any other users, including Jira administrators and system administrators. If necessary, you can change the privacy option at any time.

Connecting to the work of your teams

  1. Select the sources that you'll be connecting to your new plan. We recommend that you use boards as your issue source, as when boards are chosen, and it's a Scrum board, then Portfolio for Jira can use the velocity of the past few sprints to pre-fill the Team Velocity box. The team velocity box, in particular, assists in ensuring realistic calculation of the work.

    Sources Description
    Board

    A board displays issues from one or more projects, giving you a flexible way of viewing, managing and reporting on work in progress. There are two types of boards in Jira Software:

    Scrum board — for teams that plan their work in sprintsMore about Scrum
    Kanban board — for teams that focus on managing and constraining their work-in-progress. More about Kanban

    Project

    A Jira project is a collection of issues that is defined according to your organization's requirements. For example, it could be a software development project, a marketing campaign or a website enhancement request system.

    Filter

    Your board's filter is a Jira issue filter (a JQL query) that specifies which issues are included on your board. For example, your board may include issues from multiple projects, or from only one project, or from a particular component of a project. Only the administrator of a board or a person with the 'Portfolio for Jira Administrators' global permission can configure a board's filter.

  2. Select your estimation method.

    If all of your issue sources are boards using story points, the estimation method is automatically set to story points.

    If you have multiple issue sources with varying estimates, you'll need to configure the conversion ratio for how these varying estimates are converted. See Configuring issue sources for more details.

  3. Click Next.

Selecting relevant releases

Select the releases that you want to work with and click Next.

  • For any releases not selected, the issues assigned to that release won't be included in the plan.
  • For projects that have the fix version field hidden, any issues from those projects will not be sourced into the plan. This is due to a issue in Portfolio for Jira — watch JPOSERVER-1283 - Issues in projects with hidden fix version field are not imported into Live Plans Verified for updates.

Defining your teams

You can accept the suggested teams, or you can customize them by following these steps: 

  1. Choose the agile method for the team:
    • Scrum — if your team is working in fixed iterations
    • Kanban — if your team is working in a continuous flow
  2. Select the weekly capacity of your team.
    Note that for plans that have boards as issue sources, Portfolio for Jira 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.
  3. Click Next.
  • To delete a team, click more () > Delete.
  • You can also add, configure, delete teams from within a plan. See Adding and removing teams for more details.

Confirming the scope

You can refine the list of issues to be included in your plan. To remove any issues you don't want to include in your plan, clear the checkboxes for these issues, and click Next.

 

Renaming a plan

Click the name of the plan name and enter a new name for it.

 

Deleting a plan

  1. Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
  2. Click more () next to the plan name > Delete.

 

Related topics

Last modified on Oct 17, 2017

Was this helpful?

Yes
No
Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.