Portfolio for Jira 2.26 release notes
12 March 2019
We're pleased to announce the release of Portfolio for Jira 2.26.
Since the release of Portfolio for Jira 2.18, we're iteratively releasing new features and improvements, as we continue building the new planning experience in our eventual release of Portfolio for Jira 3.0.
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.
In Portfolio for Jira 2.26, we're releasing the following features and improvements in the new planning experience:
Upgrade now to plan work for your teams more efficiently in Portfolio for Jira.
Want to learn more about the new planning experience? Check out this article in Atlassian Community!
Portfolio for Jira Server team
Compatibility with programs
Though programs are not sporting the new UI, you can now leverage programs in the new planning experience. Programs provide an aggregate view of multiple plans, and help you monitor how different workstreams are tracking against high-level business priorities.
See Programs and Adding plans to programs for more details.
Sample program with plans in the new experience
New bulk action — move issues to new parent
Quickly move issues to a new parent using this new bulk move action. See Editing multiple issues in bulk to know more about the existing bulk actions in the new experience.
Moving issues to new parent in bulk
Based on the feedback we've received, we're making the following visual enhancements in the new experience:
- We're improving the badges for adding dependencies, making it simpler and more intuitive.
- We've heard that a lot of people use the issue details filter to quickly narrow down on their work. So we've bumped this filter up to the top of the list.
Scenario names now editable
Scenarios are now fully supported in the new experience, now that scenario names are editable. Check out Configuring plans for more details.
If you have any feedback on how your teams are using scenarios in Portfolio for Jira, let us know via the give feedback icon in your plan.
We're helping you plan work more efficiently by surfacing warnings when issues in your plan are subject to scheduling conflicts. Another warning we're releasing is for when the current date (at that exact day of viewing) is past the target end date of issues that are not yet completed.
Sample warning, when an issue's target end date is past the current day's date
See Scheduling work for more information.
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.
We recommend that you start planning your migration to the new planning experience. Check out our migration guide for more details.
Was this helpful?Yes Provide feedback about this article