Portfolio for Jira 3.6 release notes

Portfolio for Jira release notes

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

16 July 2019


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

Highlights

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


New issue type filter

You can now filter the issues in your plan using the issue type filter. Check out Filtering issues to know more.


Sample plan with issues filtered by issue types initiative and epic

Enhanced plan permissions

Building upon the user permission updates released in Portfolio for Jira 3.4, we're now further enhancing restricted user permissions in Portfolio.

Even if restricted users are able to edit issue details in the plans that they have access to, they cannot save any of these changes from Portfolio to Jira. See Permissions in Portfolio for Jira for more details.

Terminology improvements

For Scrum teams using story point estimates

We made the following terminology changes:

  1. Velocity is now sprint velocity.
  2. Iteration length is now sprint length.

We hope these changes make it easier to fully grasp the concept of team capacity for Scrum teams.


Previously: Team details with velocity and iteration length


Currently: Team details with sprint velocity and sprint length

See Managing teams for more details.

Clearer distinction between future sprints and projected sprints

Previously, projected sprints are named future sprints and are labeled with the PROJECTED SPRINT lozenge.


Previously: Sample projected sprint that's named as "Future sprint"

This can easily be confused with the future sprints that already exist in Jira.

To avoid further confusion, we've changed this up, and we are now aptly naming projected sprints as projected sprints. To make the distinction even clearer, we're still labeling projected sprints with the PROJECTED SPRINT lozenge.


Currently: Sample projected sprint that's named as "Projected sprint"

Check out Understanding sprints for more details.

Last modified on Aug 22, 2019

Was this helpful?

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