Portfolio for Jira 3.7 release notes
30 July 2019
We're pleased to announce the release of Portfolio for Jira 3.7.
Renew your active software maintenance now.
Upgrade now to plan work for your teams more efficiently in Portfolio for Jira.
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
We've been doing a bit of gardening and made the following enhancements:
- When you group issues by teams or components, the groupings will now be sorted in alphabetical order.
- Only the releases of these filtered projects will be displayed in the timeline when you filter your roadmap by projects.
- We've improved how progress is calculated and displayed in the roadmap.
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.