Portfolio for Jira 2.23 release notes

29 January 2019

We're pleased to announce the release of Portfolio for Jira 2.23.

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.

Get the latest version

Want to try a shiny new version?
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.23, we're releasing the following features and improvements in the new planning experience:

New features

• Single- and multiple-choice select custom fields
• Removing issues from plans
• New filter option for teams and releases
• Configuration for completed issues

Improvements

• Improved configuration for scenarios
• Easier ways to find and add custom fields
• Enhanced column resizing
• Improved accuracy of status breakdown

Announcements

• Changes to system requirements
• End of life for classic plans

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!

Cheers,
Portfolio for Jira Server team

New features

Single- and multiple-choice select custom fields

We're adding support for single- and multiple-choice select custom fields in this latest version. Check out Configuring plans to learn more.

Sample custom field configuration, with the new custom fields

Removing issues from plans

You can now remove issues from a plan in the new experience — it doesn't matter if the issue is already saved or yet to be saved in Jira. Bonus points: you can even remove multiple issues from a plan all at once.

Removing multiple issues from a plan

New filter option for teams and releases

You can now filter for issues that are not assigned to any team or any release.

No release and No team options when filtering issues

Configuration for completed issues

We know how important it is for you, to keep completed issues displaying in a plan. In Portfolio for Jira 2.23, you can do just that.

Setting the days to include completed issues in a plan

Improvements

Improved configuration for scenarios

We're ramping up scenario configuration in this release, starting with the ability to:

• set colors for scenarios
  
• create and manage scenarios from the roadmap view
  

See Configuring plans and Using scenarios for more details.

Easier ways to find and add custom fields

You can now quickly find the custom fields you need to add to a plan. You can even hide custom fields that aren't supported in Portfolio for Jira, to further narrow down your search. Check out Configuring plans to learn more

'Add custom fields' page

Enhanced column resizing

Remember how you'd resize a column (by dragging and dropping one side of it) and the other columns in the fields section would be inadvertently resized as well? That's all fixed now.

Also, when you're resizing the width of columns to their minimum, the columns automatically collapse. To expand a column, simply click on it.

See it in action below.

Sample plan, with enhanced column resizing

Improved accuracy of status breakdown

Since you can now choose how long any completed issues in Jira will remain in your plan, note that this is also taken into account when calculating progress in your plan. With the number of days set to 30 as default, this calculation is reflected more accurately in the status breakdown bar.

Sample plan, with status breakdown reflecting the progress of work

Portfolio is getting the status of all the child issues of the corresponding issue sources of a plan. This is regardless of any filters configured in the plan.

See Configuring plans for more details.

Announcements

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.

Coming soon — end of life for classic plans

With the future release of Portfolio for Jira 3.0 (Server/Data Center), Portfolio for Jira will no longer support the use of classic plans. When we release this version, you will no longer be able to access or update any of your classic plans.

Note that this only pertains to classic plans. Portfolio for Jira 2.0 live plans will still be supported, even when we release Portfolio for Jira 3.0.

We recommend that you start planning your migration to the new planning experience. Check out our migration guide for more details.