Portfolio for Jira 3.7 release notes

Portfolio for Jira release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Get the latest version

Want to try a shiny new version?
Renew your active software maintenance now.


Upgrade now to plan work for your teams more efficiently in Portfolio for Jira.

Learn more about our latest platform release, and check out this article if you have any pressing questions about the new plans!


Cheers,
Portfolio for Jira Server team


Reordering columns in your plan

Quickly drag and drop the columns of your plan, to organize your plan data in a way that makes sense for you and your stakeholders. See Displaying issue details to know how.

Sample plan with columns being reordered

Grouping by sprints

Quickly group the issues in your plans by sprints, and get a visual on how work is distributed across sprints and teams in your plan. Check out Grouping by sprints to learn more.

Sample plan with issues grouped by sprints

Rolled-up sprint values

The sprint values of child issues now roll up to the highest level in the plan hierarchy, as long as you configure your plan to show rolled-up values.

Sample plan displaying rolled-up sprints

Bulk action for issue rank

You can now update the rank of multiple issues in a plan. See Editing multiple issues in bulk to know more.

Available bulk actions in a plan

Support for URL custom fields

URL custom fields (read-only) are now supported in the improved interface. This is useful when surfacing links that are relevant to the issues in the plan, like feature specification pages.

Check out Custom fields to learn how to start using these.

Sample URL custom fields in a plan

Feature enhancements

We've been doing a bit of gardening and made the following enhancements:

Plan permission enhancements

We're streamlining auto-scheduling with the permission enhancements rolled out in Portfolio for Jira 3.4 and Portfolio for Jira 3.6. Starting with Portfolio for Jira 3.7, when auto-scheduling a plan, the issues are being auto-scheduled based on the plan permissions that you have. See Permissions in Portfolio for Jira for more details.

Last modified on Jul 30, 2019

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.