If you're using the improved planning interface (3.0 and later), this page is for you. If you're using live plans (2.0 to 2.27), head to Portfolio for Jira live plans.
Portfolio for Jira provides you with a single source of truth into the current and future health of your initiatives. Using Portfolio for Jira, you can create reliable forecasts of the work of your teams in Jira, while keeping track of current work across realistic schedules in an ever-changing agile environment.
Before you begin
Before deep-diving into how to use Portfolio for Jira, you first need to be able to distinguish between the types of Portfolio plans. With the release of Portfolio for Jira 3.0, we've removed support for classic plans. So whether you're new to Portfolio for Jira, or you're already using Portfolio for Jira for some time, it's important to familiarize yourself with the types of Portfolio plans.
Classic plans are supported in any version earlier than Portfolio for Jira 2.0. They have the timeline positioned at the bottom of your planning work space.
If you're currently running Portfolio for Jira 3.0 or later, you will no longer be able to access any classic plans. Check out this Migration guide if you need to keep using classic plans.
Live plans are fully supported from version 2.0 to 2.27 in Portfolio for Jira. They have the timeline positioned at the top, and the issues within the plan scope below the timeline.
Live plans make use of what we call a scheduling algorithm, to calculate a realistic schedule for your teams across multiple projects. The resulting schedule is displayed in the timeline.
Plans with the improved interface
Plans with the improved interface are supported in Portfolio for Jira 3.0 and later. The timeline is positioned at the right of the scope section. This provides a more intuitive experience, where you can view your roadmap directly beside the data that corresponds to it.
The main difference with this interface is you have more control over your planning. You can drag and drop issues to manually schedule them, and you can auto-schedule the issues into a resulting, realistic schedule — while having the option to either accept or discard the suggested auto-scheduled changes.
What can I do in the improved interface?
Take the get started tour straight from your Portfolio plan, and quickly see the improved interface in action.
To do this, go to your plan, click settings () > Get started tour > follow the steps to complete the tour.
With the redesigned planning interface, we've improved the following functionality:
- Planning and viewing work: You now have a timeline right next to the issues in your plan. Beside each issue in your plan, line by line, is a corresponding schedule bar, which displays when an issue starts and ends in your roadmap. To schedule work, you can manually set the dates for the issues, or manually drag and drop the bars in your timeline accordingly.
- Auto-scheduling your plan: Aside from setting dates and manually scheduling issues, you can also choose to auto-schedule the work in your plan. Portfolio will consider some factors, and then prepare a schedule of the work items for your teams. You can then choose to accept or discard the suggested changes as needed.
Note the following details when using the interface:
|Managing plan permissions|
As a Portfolio administrator, you can choose the users who can make changes in a plan, and the users who can only view a plan.
Sample plan permissions
Note that plan permissions are plan-specific, so you'll need to make any necessary changes in each plan. See plan permissions for more details.
|Viewing and managing your work|
In the improved interface, plans have three (3) views, which let you focus on specific aspects of your plan.
See What is a Portfolio plan to know more.
|Planning your work|
The improved interface has been redesigned to be interactive and more intuitive interface. This helps you view and manage the issues in your plans faster and more efficiently.
In the roadmap view of your plan, you have the following sections:
You can also filter the issues in your plan, so you can view only the work you need to focus on. You can filter your work by projects, releases, assigned teams, and even by the timeframe during which these issues are scheduled.
See What is a Portfolio plan to know more.
|Creating and assigning issues|
The improved interface provides more obvious and intuitive ways to create issues.
When assigning issues, note that you now assign issues to assignees, and not team members anymore. You can also assign an issue to only one assignee.
See Creating issues for more details.
By default, target start and target end dates are used when scheduling and auto-scheduling issues in a plan. You can choose to use due dates and other custom dates (date picker type) to schedule issues, which helps you align your plan with how your teams work.
For a custom date to be available, make sure the custom date field is added to the schemes of all the projects associated with the issue sources of the plan. Once selected, the custom dates will be displayed with the date lozenge ( ).
You can now interact with the timeline itself to schedule issues:
You can also set dates for the issues in Jira itself, if the date fields have already been added in Jira. Any dates that are set in Jira will also reflect in the corresponding issues and plans in Portfolio for Jira. See Showing Portfolio custom fields in JIRA Software to know how to add target dates and custom dates to the issue screens in Jira.
You can drag either end of a schedule bar, so work for the issue is scheduled for a shorter or longer period of time.
When scheduling child issues, the start dates and end dates of these issues roll up to the dates of their parent issues. Effectively, this means:
If you need some ideas on how best to schedule work for your teams, Portfolio for Jira can help you out by auto-scheduling your plan for you. When auto-scheduling your plan, Portfolio for Jira will:
When you rank an epic with child issues higher, the ranking of its child issues will also be higher. When these changes are saved to Jira, the child issues will also be ranked higher in Jira.
This can be confusing, especially if your teams have already ranked issues in their backlogs or active sprints in Jira, and the child issues are suddenly ranked higher.
In the improved interface, the ranking of child issues is now independent of the ranking of their parent issues. If you rank a parent epic higher, the ranking of its child issues in Jira will stay as is.
Progress is calculated by the percentage of estimates completed against the total estimates.
In the improved interface, we now display progress more visually — you'll see a status breakdown bar, which displays issues grouped by status category:
Completed issues that are no longer displaying in the plan are also taken into account when progress is calculated. This progress calculation will be reflected in the status breakdown bar accordingly.
Saving changes in Jira
In the teams view, you can:
See Managing teams to know more about the functionality of teams.
In the releases view, you can:
See Managing releases to know more about the functionality of releases.
|Disabling the planning interface|
While we've released features and improvements, we understand that you may need some features that are not available yet. If this is the case, you may need to disable the planning interface, and continue using Portfolio live plans (from versions 2.0 to 2.27) while we build more functionality. See Future releases and limitations for the current limitations.
We'll announce new features and improvements as we roll them out in future releases. Check out our release notes for updates.
We hope you do use the improved planning interface again, as we iterate on and release more features over time. See Setting up the planning environment for more details.