Future releases and limitations
This page has been written with the assumption that you've already migrated from live plans (any version from 2.0 to 2.27) to plans with the improved interface (version 3.0 and later).
We've also removed some functionality from the improved interface, 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 disabling the improved interface.
Here are some of the features we're considering:
|1||Issue detail view|
|3||Dynamic release dates|
The concept of dynamic release dates does not apply in plans with the improved interface at the moment. Currently, if you're purely manually scheduling issues, you would not get a value for release dates. Instead, issues would be grouped into specific releases that don't really have an end date. We're still considering how best to support dynamic release dates in the improved interface.
At the moment, to generate a "dynamic" release end date, you'll need to auto-schedule the issues in your plan. Depending on how your auto-schedule settings are configured, Portfolio may generate a date for this.
Reporting functionality is currently limited in the improved interface. However, we're currently building more working views that can be shared as reports to relevant audiences.
With the introduction of priority data handling, your plan may not load properly if you're using Portfolio for Jira 3.4 and later with Jira 7.5.3 and earlier. This is caused by - JPOSERVER-2623Getting issue details... STATUS .
While we're fixing this issue, a quick workaround is to make sure you've set the default priority value for the priority scheme that your Jira projects are using. See Associating priorities with projects and Defining priority field values for more details. We recommend you watch JPOSERVER-2623 as well.
Take note of the following limitations:
Compatibility and layout limitations
|1||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.|
|2||Cannot sort columns in plans|
|3||Cannot reorder columns in plans|
Progress bar not displaying accurate information
In the new releases view, the progress bar of each release displays the number of issues in the release. You can hover on the progress bar, to see the issues grouped by status category.
At the moment, the progress bar only includes the details of the issues that are currently visible in the plan. This means that old releases may not have accurate information. See Managing releases for more details.
|2||Team members are now assignees when planning work|
|3||Individual capacity planning is replaced by team capacity planning|
|4||Sprint data may not display in the plan|
Teams and sprints that have been set in Jira may not display in the plan
|6||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 improved interface, you need to:
We've removed the following functionality from the improved interface:
|1||Stages and skills|
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 improved interface, this section isn't available anymore. If an issue is not scheduled as expected, you can manually reschedule the issue straight away.
|3||Shared people settings|
Since individual capacity planning is not supported, any configured settings for the following will not apply to plans with the improved interface:
If you need any of the removed functionality in your plans, we'd like to understand this better. Let us know via the give feedback button in your plan.