Cloud
Data Center 2.25
Versions

Future releases and limitations

Overview

On this page

Related content

  • No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

We're working on more features for the new planning experience, and we'll incrementally release these features. As such, there are limitations to take note of.

We're also removing some functionality from the new experience, 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 the new experience.

Future releases

Here are some of the features we're working on:

New features in the new experience

1Issue detail 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.
2Visual 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.
  • Starting with Portfolio for Jira 2.19, you can now group issues by and color issues by, using several visualization options. See Customizing view settings for more details.
3Release management

We're still working on how best to support release management in the new planning experience.

At the moment, you can perform the basic release management tasks, like viewing, creating, updating, and deleting releases.

Features we're considering in the new experience

1Flexible coloring options
  • We're currently looking into flexible coloring options to replace the main value of themes in previous plans, which is providing your audience a visual way to distinguish different themes in a plan at a glance.
  • If you have any ideas and suggestions on coloring options in the new experience, let us know by clicking the give feedback icon in your plan.
2Reporting functionality

Reporting functionality is currently limited in the new experience. However, we're currently building more working views that can be shared as reports to relevant audiences.

Limitations

Take note of the following limitations:

Optimize limitations

1Optimize functionality is incomplete at the moment

In the new experience, optimize is the new form of automatic scheduling that's replaced the previous calculate functionality. Right now, the optimize functionality is incomplete – we're still working on intuitive controls to easily use the functionality, and there's little guidance for how to use it as well. These are all areas that we'll be improving before the official release of the new experience in the future.

If you require the scheduling algorithm in your plan, and the optimize functionality produces poor results, let us know about your experience via the give feedback button in your plan.

While we build the new experience to completion, you may want to consider opting out, so you can keep using the previous calculate functionality for now.

2 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 teams view.
3Filters are not available 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.
4

Optimized, dynamic release dates do not display


  • 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.
5

Lead time in dependency details is not an optimized value

(info) When you're optimizing your plan, note that the lead time that appears in the dependency details is not an optimized value.

Sample lead time of a dependency when a plan is optimized

Compatibility limitations

1Plans with the new experience are not compatible with programs
  • At the moment, the scope view in programs will not work if the program has a plan with the new experience enabled in it.
  • Unfortunately, there's not workaround for this. To make the scope view in a program work, you'll need to remove any plans with the new experience from the program.
  • We're working towards making programs and plans with the new experience compatible in a future release.
2Limited 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.

Layout limitations

1Cannot sort columns in plans
  • It's a familiar operation to sort columns, especially since you can do this in the current 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.
2Cannot 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 the new experience. See Displaying issue details for the current workaround.

Limitations with technical changes in the new experience

1Multiple scenarios

We're still working on fully supporting multiple scenarios. At this time, you cannot edit the name of existing scenarios.

2Support for custom fields

Though you can now add custom fields to your plan, this is currently limited to the following custom field types:

  • single-line text fields
  • single-choice select fields
  • multiple-choice select fields (read-only)
  • date picker fields
  • number fields

Specifically for multiple-choice select fields, being read-only, you cannot edit the values of these fields directly in your plan. Any values set in Jira will reflect in your Portfolio plan, but you can only edit these values in Jira.

We're still working on supporting more custom field types in future versions.

3

Plans with the new experience remain visible after opting out

If you've opted out and have already disabled the new experience in your instance, the existing plans with the new experience will still be displayed in your instance.

We're not deleting any of these plans, to make it possible for you to reenable the new experience, in case you want to opt in again. However, accessing any of these plans will result into an error.

If you want to opt in again and use the new experience with your plan:

  1. Enable the new experience as an early access feature in your Jira instance.
  2. Enable the new experience for each plan in Portfolio for Jira as needed.

If you want to delete a plan with the new experience 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.
4Parent 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 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.
5Team members are now assignees when planning work
  • Though there are team members in the teams view, you now assign issues to assignees, and not team members anymore.
  • You can assign an issue to only one assignee.
6Individual capacity planning is replaced by team capacity planning
  • We currently don't have the functionality of individual capacity planning. We're still considering how this will be implemented in the new experience.
  • 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.
7

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.
8Parallel sprints not displaying in a plan

We're still working on displaying parallel sprints in the timeline of a plan. If your teams work in parallel sprints in Jira, we recommend not to use this feature just yet.

See Grouping issues by teams to know more about displaying sprints in the timeline.

9Minor change when entering estimates for issues

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

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

Functionality removed

In the new experience, we've removed the following functionality:

1Stages and skills

We've removed stages and skills 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. With no 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.
2Scheduling factors

In current 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.

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 plans, let us know via the give feedback button in your plan.

Last modified on Mar 8, 2019

Was this helpful?

Yes
No
Provide feedback about this article

Related content

  • No related content found
Powered by Confluence and Scroll Viewport.