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.
Here are some of the items we're working on.
|New features in 3.0 plans|
|Optimization for Kanban teams|
|Features we're considering in 3.0 plans|
These are the limitations to take note of, while using the alpha.
| Optimization for Kanban teams |
|Parent issues don't inherit child issue details|
|Team members are now assignees when planning work|
|Individual capacity planning is replaced by team capacity planning|
Teams and sprints that have been set in Jira may not display in the plan
|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:
If you want to delete a 3.0 plan that you no longer need:
|Cannot use filters when optimizing plans|
|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|
|Cannot sort columns in plans|
|Cannot reorder columns in plans|
|Cannot view optimized, dynamic release dates|
|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:
|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.|
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:
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.