Future releases and limitations



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


This is the alpha version of Portfolio for Jira 3.0 — your sneak peek at the improved functionality that's just around the corner. As such, do note the following:

  • Some features may not be complete just yet, as we're continuously iterating on these.
  • Because it's an alpha version, the documentation will only be visible to you, our alpha users. You will not find any alpha pages in the usual page sidebar.

We've linked the table of contents below, so you can easily navigate to the alpha pages at any time.

We're working on more exciting features for 3.0 plans, and we'll incrementally release these features. However, as this is still the alpha version, there are limitations to take note of. We're working on implementing the ideal fixes and design flows for these limitations, and we'll incrementally roll these out in future releases as well.

We're also removing some functionality from alpha plans, as we believe some features weren't providing the full value that we had envisioned. If required in your plans, you can still use the removed functionality by opting out of alpha.

Future releases

Here are some of the items we're working on.

New features in 3.0 plans
Optimization for Kanban teams
  • At the moment, plans that use the Kanban methodology cannot be optimized directly. These are the plans that use Kanban boards for issue sources, or have teams using the Kanban scheduling methodology.
  • As a workaround, set the scheduling methodology to Scrum for the Kanban team in the team capacity view.
  • At the moment, clicking an issue in your plan will open the issue in Jira.
  • We're working on an issue detail view that opens up when you click the issue. This lets you surface additional issue details without having to leave the context of your plan.
Visual customization
  • We believe in the value of making your plan more consumable for you and anyone you want to share it with.
  • We're adding more ways for you to visually customize your plan, to make it just right for you and your audience.
  • To start, we're currently looking at team groupings, project groupings, and issue source colors.
Roadmap sharing
  • We're working on a quick and easy way for you to share your plans with relevant stakeholders.
  • This way, everyone stays on the same page across all work streams in your organization.
Features we're considering in 3.0 plans
  • We know how important dependencies are when planning work for your teams, to determine potential blockers at a glance.
  • In future releases, you'll be able to view, create, update, and delete dependencies in your plan as needed.
  • We're also working on visual indicators that make it easier to spot issues that have dependencies.
  • Themes are not supported in 3.0 plans at the moment, but we're looking to understand your needs for themes.
  • Let us know if you require themes, and how you use themes in your work, by clicking the Give feedback icon in your plan.
Multiple scenarios
  • We understand the value in using multiple scenarios when planning work.
  • We're currently looking at the ideal design for this in 3.0 plans.


These are the limitations to take note of, while using the alpha.

Optimization for Kanban teams
  • At the moment, plans that use the Kanban methodology cannot be optimized directly. These are the plans that use Kanban boards for issue sources , or have teams using the Kanban scheduling methodology .
  • As a workaround, set the scheduling methodology to Scrum for the Kanban team in the team capacity view.
Parent issues don't inherit child issue details
  • Parent issues don't get the aggregated value of the estimates that have been set for their respective child issues.
  • Parent issues also don't inherit the following values of their respective child issues: releases, teams, and assignees
  • Unfortunately, there's no workaround to get the aggregated or inherited values. At present, you can expand the parent issue, to view the details of the child issues.
Team members are now assignees when planning work
  • Though there are team members in the team capacity view, you now assign issues to assignees, and not team members anymore.
  • You can assign an issue to only one assignee.
Individual capacity planning is replaced by team capacity planning
  • In alpha, we don't have the functionality of individual capacity planning. We're still considering how this will be implemented in 3.0 plans.
  • At the moment, when optimizing a plan, Portfolio for Jira will consider the total capacity of a team to complete the work being scheduled.
  • For Portfolio to do this, you must directly set team capacity in your plan.

Teams and sprints that have been set in Jira may not display in the plan

  • If a team or sprint is assigned in Jira, but these do not exist in Portfolio, then you cannot select this team or sprint in the fields section of your plan.
  • There is no workaround for this. The only way to have such teams and sprints display as options is to add these in your plan itself.
3.0 plans remain visible after disabling alpha

If you've opted out and have already disabled alpha in your instance, the existing 3.0 plans will still be displayed in your instance. We're not deleting any existing 3.0 plans, to make it still possible for you to reenable alpha, in case you want to opt in again. However, accessing any 3.0 plan will result into an error.

If you want to opt in and reenable an alpha plan:

  1. Enable the alpha feature flag in your Jira instance.
  2. Enable alpha for each plan as needed.

If you want to delete a 3.0 plan that you no longer need:

  1. Go to Portfolio (in header) > View Portfolio. This will display the Manage portfolio page.
  2. Click more () for the plan you want to delete > Delete.
  3. In the confirmation message, click Delete.
Cannot use filters when optimizing plans
  • When optimizing your plan, you can't use any of the plan filters, to surface any of the plan data that's been optimized.
  • We understand the value in filtering out the issues that will have the newly optimized changes, and this is one of our top focus items.
Cannot save changes for teams and releases in the new 'Review changes' dialog

At the moment, you cannot save any changes involving teams and releases in the new 'Review changes' dialog in 3.0 plans.

You'll need to save these changes via the 'Review and commit changes' dialog from 2.0 plans. See Saving changes in Jira to know more.

Cannot remove issues from plans
  • We're still building what we believe is the best experience for removing issues from 3.0 plans.
  • See Planning work for the current workarounds.
Cannot sort columns in plans
  • It's a familiar operation to sort columns, especially since you can do this in 2.0 plans.
  • At the moment, it's not possible to sort columns in 3.0 plans. Though we unfortunately don't have a workaround for this, we are looking into building this in a future release.
Cannot reorder columns in plans
  • When working with columns, it's common practice to reorder columns by drag and drop.
  • At the moment, it's not possible to drag and drop columns in 3.0 plans. See Reordering columns for the current workaround.
Cannot view optimized, dynamic release dates
  • At the moment, the optimized, dynamic release dates will not display in the releases view of your plan.
  • This also means that in the releases view, there's no visual indication of any releases that are off track. You can only see this information in the roadmap view.
Minor change when entering estimates for issues

In 2.0 plans, you can enter an estimate for an issue, then click the Enter key to move to the issue in the next row.

In 3.0 plans, you need to:

  1. Enter an estimate for an issue.
  2. Click the tab key on your keyboard. This will move your cursor to the estimate field of the issue in the next row.
  3. Repeat the above steps as needed.
Limited browser compatibilityWe highly recommend you use Chrome or Firefox as your browser. You can also use Internet Explorer 11 and Safari — we've fixed some issues specific to these browsers in the latest version.

Functionality removed from 3.0 plans

We've removed the following functionality:


We've removed stages and skills from 3.0 plans, for the following reasons:

  1. There's low usage of stages and skills across Portfolio for Jira users.
  2. Stages require regular, manual maintenance, while skills require significant work to break down the skill estimates for each issue in a plan.
  3. Usage of stages and skills contradict with the workflows in Jira.
  4. Any data involving stages and skills only exist in a plan. Without a way to integrate the data with Jira, this can lead to lack of transparency. This doesn't work with the direction we're taking in the new planning experience.
Scheduling factors

In 2.0 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 3.0 plans, this section isn't available anymore. If an issue is not scheduled as expected, you can manually reschedule the issue straight away.

This doesn't necessarily mean that the removal is final, nor does it mean that the functionality will be back in future releases. If you need the removed functionality in your 3.0 plans, let us know via the Give feedback icon.

最終更新日: 2019 年 2 月 14 日


Powered by Confluence and Scroll Viewport.