Changes in the new experience



アトラシアン コミュニティをご利用ください。


The following table lists the important changes to note when planning in the new experience.


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

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

  • Working hours and days
    • Region: System default
    • Work day: 8 hours
    • Work week: Monday through Friday
  • シナリオ
    • We're still working on fully supporting multiple scenarios. See Future releases and limitations to know more.
    • At the moment, for scenarios to work in the new experience, the corresponding scenarios should already be configured in the plan before the new experience is enabled in that plan. See Using scenarios for more details.
  • 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.
Viewing issues in a plan

Previously, issues were displayed in a timeline at the top of the plan, with the work items of your teams displayed in a scope table at the bottom, as shown in the sample plan below.

In the new experience, you still have the scope table in fairly the same position in the plan, but we now call this the scope section.

However, the timeline has been moved to the right of the scope section, and each issue has its corresponding schedule block. The schedule blocks are displayed in the timeline, according to how these are scheduled, as displayed in the following sample plan.

Visualizing work using grouping and coloring settings

Previously, using the themes report, you could apply a monochromatic, single-level view of your plan, to distinguish different work streams (projects, teams, and more) into separate swimlanes.

In the new planning experience, you can now mix and match grouping and coloring options, which let you visually display more details to your audience. This also makes it easier for your audience to consume your plan in greater detail.

Sample plan, with issues grouped by project, and issues colored by status

See Customizing view settings for more details.

Viewing dependencies in the timeline

Previously, you would know if an issue has a dependency if the issue has a light blue bar in either end in the timeline. These visual indicators are not obvious, and are not intuitive to use.

Sample plan with issue that have dependencies

In the new experience, we're making it easier to for you to keep track of any dependencies in your plan. All you have to do is add the dependencies column to your plan, and you can view the existing dependencies straight away. Not only that — you can also create dependencies to and remove dependencies from any issue, directly in your plan.

Sample plan, with issues having dependencies

See Managing dependencies for more information.

Creating issues

Previously, there were several ways to create issues, and some of these ways were not directly obvious to users.

In the new experience, we're redesigning how you can create issues, making these more obvious and more intuitive:

  • You can create an issue from the top of the scope section. When you're doing this, you can specify the hierarchy level for the issue, as well as the project to associate it with.
  • You can also hover over an issue at any hierarchy level, and create a child issue for it. The new issue will inherit the same project by default.

See Planning work for more details.

Assigning issues

In Portfolio for Jira, plans use the concept of team members, which are independent from assignees in Jira. You'd first assign an issue to a team member in Portfolio for Jira, and when you commit this change to Jira, the issue is then assigned to the corresponding assignee in Jira.

In the new experience, we're simplifying this task by letting you set the assignee directly in your plan. This effectively removes that extra step of assigning the issue to a team member first, then saving the change in Jira as an assignee change. One thing to note, in the new experience, you can assign an issue to only one assignee.


Previously, you'd need to use the calculate functionality, to interact with the timeline itself. When you calculate your plan, Portfolio would calculate the realistic scheduled start and end dates of the issues, and then create a realistic schedule of the issues.

In the new experience, we're simplifying the experience by using only one type of date — target dates. You can also directly interact with the timeline itself to schedule issues. You can manually drag and drop issues in the timeline, according to how you want to schedule these issues.

You can also choose to make Portfolio optimize your plan for you and create a schedule of your work. But it's up to you to decide whether or not you'll accept the optimized changes made by Portfolio.

See Scheduling work for more details.

In today's Portfolio's plans, you can use the scheduling factors section, to understand how issues are scheduled off your backlog, as well as why some issues aren't scheduled as expected.

In the new experience, this section isn't available anymore. If an issue is not scheduled as expected, you can manually reschedule the issue straight away.


Previously, when you'd rank an epic with child issues higher, the ranking of its child issues would also be higher. When these changes were committed to Jira, the child issues would 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

Previously, progress would be calculated by the percentage of the estimates completed against the total estimates.

In the new experience, we now display progress more visually — in 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

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.
Zooming in and out of the work in your timeline

In the new experience, you can quickly see issues for a set timeframe, like 3 months, 1 year, or a custom date range. This lets you focus on only the issues scheduled within the selected timeframe.

You could also do this in today's plans; however, you'd need to use the scheduled range filter — and this method wasn't too obvious to use.


Previously, you'd manage your teams by clicking the Teams view, at the top-right area of your plan.

In the new experience, team management is accessed via the teams tab above the scope table.


Previously, you'd be able to plan the individual capacity of your team members.

In the new experience, we're still considering how capacity is best managed. We're starting with the following details:

  • Individual capacity planning is replaced by team capacity planning.
  • 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 team capacity in your plan.

Previously, you'd manage your releases by clicking the Releases view, at the top-right section of your plan.

In the new experience, release management is accessed via the releases tab above the scope table. We're still iterating on how releases are managed, and this is why the dynamic optimized dates of releases won't be visible as of yet.

Reporting work

Previously, you could share details about your plan using different report types, like the capacity report and dependencies report, via the Reports view.

In the new experience, we've removed the Reports view because we're currently building more working views that can be shared as reports to relevant audiences. Although the reporting functionality is currently limited, you can still share a read-only version of your roadmap.

最終更新日 2019 年 1 月 11 日


Powered by Confluence and Scroll Viewport.