Still need help?

The Atlassian Community is here for you.

Ask the community

In the new planning experience, 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 block, which displays when an issue starts and ends in your roadmap. To schedule work, you can manually set target dates, or manually drag and drop the issue blocks in your timeline accordingly.
  • Optimizing your plan: Aside from setting target dates and manually scheduling issues, you can also choose to optimize the work in your plan. By optimizing, Portfolio will use all existing scheduling factors to prepare an optimized schedule for you. You can then choose to accept or discard the proposed changes as needed.

Here is a sample plan in the new experience:

Take note of the following details when using the new experience.

Configuring plans

In the new experience, you can currently configure the estimation, issue sources, and permissions being used by a plan. See Configuring plans for more details.

The following settings from the current planning experience are also used as default:

  • Working hours and days
    • Region: System default
    • Work day: 8 hours
    • Work week: Monday through Friday
  • Scenarios
    • We're still working on supporting multiple scenarios. See Future releases and limitations to know more.
    • As a default, in the case where an existing plan has been converted to the new plan, the current scenario will be used in the new plan. You can also switch to any of the scenarios that may have been set up before the conversion.
  • Commit issue assignee: In the new experience, you now assign issues to assignees, and not team members anymore. With this behavior by default, this option is no longer needed in the new experience.
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 new experience, plans have three (3) views, which let you focus on specific aspects of your plan.

  • Roadmap, where you can plan and schedule issues across the projects you're managing.
  • Teams, where you can view, create, edit, and delete the teams in your plan.
  • Releases, where you can view, create, edit, and delete the releases in your plan.

See What is a Portfolio plan to know more.

Planning your work

The new planning experience provides an interactive and more intuitive interface for you to view and manage the issues in your plans.

In the roadmap view of your plan, you have the following sections:

  • Scope section, which functions as the backlog of your plan.
  • Fields section, which contains pertinent details about the issues in your plan, like status, status breakdown, and estimates.
  • Timeline section, which displays the schedule blocks for each issue in your plan, according to how the issues are scheduled. You can use move blocks to schedule your issues accordingly.

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 new experience provides more obvious and intuitive ways to create issues.

When assigning issues, note that in the new experience, you now assign issues to assignees, and not team members anymore. You can also assign an issue to only one assignee.

See Planning work for more details.

Scheduling issues

We're simplifying the experience of scheduling issues by using only one type of date — target dates.

You can now interact with the timeline itself to schedule issues:

  • by dragging and dropping the corresponding schedule blocks in the timeline,
  • or by entering target start dates and target end dates for the issues.

You can also set target dates for the issues in Jira itself, if target date fields have already been added in Jira. Any target 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 to know how to add target dates to the issue screens in Jira.

You can drag either end of a schedule block, 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:

  • the start date of a parent issue would be the earliest start date of all its child issues,
  • and the end date would be the latest end date of all its child issues.

If you need some ideas on how best to schedule work for your teams, Portfolio for Jira can help you out by optimizing your plan for you. When optimizing your plan, Portfolio for Jira will:

  1. Consider various issue details, including assigned sprints, assigned releases, dependencies, estimates, and target dates.
  2. Give you a preview of how the issues in your plan would be scheduled.
  • The optimized changes will not be automatically saved when these changes display in your plan. You can choose to accept the optimized changes, or return to your plan to make other changes accordingly.
  • For Portfolio to optimize your plan and produce a realistic schedule, you need to estimate the issues in your plan and set up the capacity for your teams.

See Scheduling work and Saving changes in Jira for more details.

Ranking issues

When you rank an epic with child issues higher, the ranking of its child issues will also be higher. When these changes are committed 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, and the child issues are suddenly ranked higher.

In the new experience, 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.

Calculating progress

Progress is calculated by the percentage of estimates completed against the total estimates.

In the new experience, we now display progress more visually — you'll see a status breakdown bar, which displays issues grouped by status category:

  • blue, for issues that are still in the To do status category
  • yellow, for issues in the In progress status category
  • green, for issues in the Done status category

Saving changes in Jira

  • Any changes you make in your plans will not be saved in Jira, until you're comfortable with the changes made. These include the manual changes you make in your plan, and the optimized changes that you may have accepted.
  • You can review and select which changes to save in Jira. See Saving changes in Jira for more details.
Managing teams

In the teams view, you can:

  • Create teams and add members to teams
  • Set the working hours for team members
  • Choose the scheduling method for your teams
  • Assign tasks to teams accordingly

We're still considering how best to manage capacity in the new experience. We're starting with the following details:

  • Currently, only team capacity can be defined. More focus on individual capacity is planned for the future.
  • When optimizing a plan, Portfolio for Jira will consider the total capacity of a team, to complete the work being scheduled.
  • For Portfolio for Jira to do this, you must directly set up the capacity for your teams.

See Managing teams to know more.

Managing releases

In the releases view, you can:

  • Create and manage project-specific releases and cross-project releases
  • Keep track of the progress of these releases
  • Determine if these releases will be completed on time, as planned

We're still considering how best to manage releases in the new experience. At the moment, the dynamic, optimized dates of releases will not be visible.

See Managing releases to know more.

Opting in and out of the new experience

While we've released heaps of 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 opt out of the new experience while we're building 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 opt in again, as we iterate on and release more features over time. See 
Setting up the new experience for more details.

Last modified on Jan 21, 2019

Was this helpful?

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