Portfolio for Jira 2.20 release notes
2018 年 12 月 4 日
We're pleased to announce the release of Portfolio for Jira 2.20.
Since we released Portfolio for Jira 2.18, we're iteratively releasing new features and improvements, as we continue to build the new planning experience. This new experience is an early access feature that all Portfolio for Jira users can already start using.
Renew your active software maintenance now.
We're keen to know how you find working in the new experience. Send us your thoughts via the give feedback button in your plan, and help shape the future of Portfolio for Jira.
In Portfolio for Jira 2.0, we're releasing the following features and improvements in the new planning experience:
Upgrade now to plan work for your teams more efficiently in Portfolio for Jira.
Check out Introducing a new planning experience in Portfolio for Jira in Atlassian Community!
Portfolio for Jira Server team
New experience enabled by default (early access feature)
We're enabling the new planning experience as an early access feature in your Jira instance by default. This essentially means you'll only need to switch on the new experience directly in your plan.
Enabling the new experience in a plan
Don't worry — if you prefer to keep using the previous layout in your plan, you can do that by:
- simply not enabling the new experience in your plans, or
- completely disabling the new experience in your Jira instance.
And if you're already trying the new experience, but finding the previous layout works better for you, you can choose to disable the new experience in your plans, or completely disable the new experience in your Jira instance.
If you do decide not to use the new experience, do let us know your reasons via the give feedback button in your plan. We're keen to know your thoughts on how we can improve the planning experience as a whole.
Filtering for dependency chains
When filtering for the dependencies of an issue, you can now choose to include not just its direct dependencies, but also any indirect dependencies.
For example, you have TIS-1 in your plan, and it's blocking TIS-2. TIS-2 is also blocking TIS-6 and PERF-1. By including the dependency chain of TIS-1:
- the direct dependency TIS-2 will display, and
- the indirect dependencies TIS-6 and PERF-1 will also display in the plan.
Filtering a specific issue and its dependency chain
Check out Managing dependencies to learn more.
New filter for labels
Following the new fields for labels and components released in Portfolio for Jira 2.19, you can now use labels to filter work in your plan.
Labels filter in the new experience
Note that you can only use the labels that are being used by the issues in the plan. See Filtering work for more details.
Support for single-line text custom fields
We're in the early stages of supporting custom fields in the new experience — and now, you can add single-line text custom fields to your plan in the new experience via a quick workaround. See Viewing work to learn more.
Sample plan with the custom field 'External issue ID'
Enhancement to release filters and icons
When filtering the work in your plan using releases, the release icons that display in the timeline will also be filtered accordingly. Check out Filtering work for more details.
Filtering releases and release icons
Inherited settings when sharing roadmaps
The shared roadmap now inherits the filters and settings that have been configured for the roadmap view. This includes the values applied for the hierarchy filters, filter settings, timeframe settings, view settings, and more.
With the relevant settings applied, it's easier for your audience to stay within context. See Sharing and exporting plan data for more information.
Coming soon — changes to system requirements
Currently, Portfolio for Jira Server supports the use of Jira Core Server 6.3, Jira Software Server 6.3, and later versions, to allow the easy integration and data flow between these products. However, in an effort to align with the Atlassian Support End of Life Policy, Portfolio for Jira will soon be adjusting the minimum supported versions of both Jira products.
With the future release of Jira Core Server 8.0 and Jira Software Server 8.0, Portfolio for Jira will no longer support Jira product versions 7.2 and earlier. Moving forward, Portfolio for Jira Server will align its support with the versions listed in the Atlassian Support End of Life Policy.
For updates on the status of this change, keep an eye on Installing the Advanced Roadmaps app within our Server product documentation.
For version upgrade assistance, check out Upgrading Jira applications and the Best practices guide for upgrading Jira Software Server.