Portfolio for Jira and it's third iteration that was released in April 2019 has some great features. In no less than 18 releases since the main release Portfolio for Jira has grown into a powerful tool to manage projects and programs in Jira. This is a summary of the biggest features released for Portfolio for Jira 3.0.
Set a plan that reflects your reality
One of the most difficult aspect of managing teams in Jira is to get a holistic overview. Using Portfolio for Jira this becomes much easier and in 3.0 it becomes even easier as you can adjust your plan by dragging and dropping issues to designate or reassign their parents, reorder them based on priority, and set timelines for their execution to generate a roadmap your teams can really get behind. All data is in real time so you can always get that holistic overview you need.
Constantly evolve and respond to change
With Portfolio for Jira 3.0 you can can visualize cross-project and cross-team dependencies to proactively navigate pitfalls and continually adapt plans, forging a clear path forward to help your team deliver on time. Get the data you need to adjust plans and drill down into the latest changes when ever you need to.
For more advanced users, Portfolio can do the heavy lifting when it comes to constructing a roadmap. When its sophisticated scheduling algorithm is activated using the Auto-schedule button, Portfolio will take into account multiple variables, including the priority of your backlog, estimates, dependencies, and more, to generate a plan in a matter of seconds.
Consistently communicate and share the best of your plan
A variety of display options allow you to share updates with the right level of detail tailored to your audience and keep everyone on the same page, even as plans evolve. And because plans are open to everyone in the organization using Portfolio, individual team members can see how their work connects to bigger-picture initiatives, while management can see when work is forecasted to ship.
Following the launch of 3.0, highly requested fields such as Priority and Parent are added to give you even better detail of the work. In addition to this you also will find a new field called progress that track the completed work based on estimates (days, hours, or story points) for all the descendants of a given issue. This is displayed based on both completed and partially completed issues for which time has been logged against the estimated workload.
Five additional fields are available with Portfolio for Jira 3.0. These are Checkbox, Radio button, User picker (single user), URL (read-only), and Label. You can use these to further add data to your overview.
Five bulk actions have been added to Portfolio for Jira 3.0. Fields that can now be manipulated in bulk include Target start, Target end, Assignee, Sprint, and Issue rank. Clean up your plan by removing or reranking issues, or set dates all in one go.
With Portfolio for Jira 3.0 there are now filtering support for Jira standard fields Assignees, Sprints, Issue sources, and Issue types. There are also filtering for custom fields such as Single-select, Label, and Radio button, but it still in progress so expect this to be expanded in future updates. These new filter options makes it even easier to get the view you need.
With support for coloring, grouping, and general display of information in your plan you add meaningful context and a greater dimension to your data. This will make thins more clear as you track progress or share your plans with others.
The new view settings now have the ability to roll up sprints on the timeline, new sorting capabilities (sort by Dates, Status, Sprint, Estimate, and Priority), and the new grouping options (group by Label, Release, Sprint).
Portfolio for Jira plan Confluence macro
In an effort to expand on the options for sharing Portfolio plans, in version 3.12 we announced the arrival of the “Portfolio for Jira plan” Confluence macro, which enables users to embed lightweight Portfolio for Jira plans directly within Confluence pages. It’s yet another way to keep everyone on the same page, even as plans evolve.
Other notable improvements
Let’s not forget the little things that make Portfolio plan owner’s lives easier:
- Sticky sprint header In the early days of the new planning experience, it was easy to lose context as you scrolled down a massive plan grouped by Sprint or Team. As a result, we made sprint headers persistent, so sprint details will always display as you maneuver through your plan.
- Column re-ordering Early on, we spotted a need to improve the functionality supporting the display of field columns in a plan. Now, you can drag and drop the columns of your plan to organize them in a way that makes sense for you and your stakeholders.
- Configurable dates When we first launched 3.0, Portfolio plans relied on Target start and Target end dates to display items on the roadmap. To better align with the way your teams might have historically tracked timelines in Jira, we’ve since expanded to allow for the use of custom dates to schedule work.
Impressions so far
Portfolio for Jira is by far the most useful overview for day to day operational management of Jira projects. Where Jira align is useful for Portfolio management on a strategic level and Roadmaps for Jira Cloud give a different visual overview on a team level, Portfolio for Jira give the operational overview.
The continued improvement of Portfolio for Jira 3.0 has continuously made this experience better and easier to work with. As we see more and more organizations start to implement SAFe into their way of working, Portfolio for Jira still is the best way to implement this on an operational level.
If you have not tried Portfolio for Jira I strongly recommend that you give it a test run. It is an amazing addition to your Jira instance if you are serious about portfolio management on an operational level.
More information on Portfolio for Jira can be found here: