Future releases and limitations
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.
Here are some of the features we're working on:
New features in the new experience
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
|1||Flexible coloring options||
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.
Take note of the following limitations:
- Optimize limitations
- Compatibility limitations
- Layout limitations
- Limitations with technical changes
|1||Optimize 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
|3||Filters are not available when optimizing plans||
Optimized, dynamic release dates do not display
Lead time in dependency details is not an optimized value
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
|1||Plans with the new experience are not compatible with programs||
|2||Limited browser compatibility||We 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.|
|1||Cannot sort columns in plans||
|2||Cannot reorder columns in plans||
Limitations with technical changes in the new experience
We're still working on fully supporting multiple scenarios. At this time, you cannot edit the name of existing scenarios.
|2||Support for custom fields||
Though you can now add custom fields to your plan, this is currently limited to the following custom field types:
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.
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:
If you want to delete a plan with the new experience that you no longer need:
|4||Parent issues don't inherit child issue details||
|5||Team members are now assignees when planning work||
|6||Individual capacity planning is replaced by team capacity planning||
Teams and sprints that have been set in Jira may not display in the plan
|8||Parallel 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.
|9||Minor 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:
In the new experience, we've removed the following functionality:
We've removed stages and skills for the following reasons:
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.