Portfolio for Jira 3.4 release notes
19 June 2019
We're pleased to announce the release of Portfolio for Jira 3.4.
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!
Portfolio for Jira Server team
Improvements on dependency scheduling
You can now configure how dependent issues are scheduled in your plan — whether the dependent issues can or cannot be worked on at the same time. Check out Scheduling to know more.
Sample settings for scheduling dependencies
Also, when you're auto-scheduling your plan, the lead time that appears in the dependency details is now an auto-scheduled value. The lead time value displaying is the new value that will be updated once the suggested changes are accepted.
Sample lead time of a dependency when a plan is auto-scheduled
Quick filtering for dependent issues
Click the filter link so you can quickly filter for the dependent issues that you need to focus on. See Managing dependencies to know more.
Quick filtering for issues by sprints
You can now quickly filter for issues by sprints by using the sprint filter in the roadmap, or by using the sprint filter link when you're viewing sprint details.
Sprint filter in the roadmap view
Sprint filter when viewing sprint details
Plan access changes
The following are now able to access any private plans in Portfolio for Jira:
- Users with the Portfolio for Jira administrator permission
- Users with the Jira administrators global permission, since these users are automatically made Portfolio for Jira administrators
- Jira administrators
- System administrators
See Permissions in Portfolio for Jira and Managing global permissions for more details.
Issues resolved in 3.4.1
Released on 9 July 2019
Was this helpful?Yes Provide feedback about this article