Working with Portfolio plans
Starting with Portfolio for Jira 2.17.1, the new planning experience can now be used in your production instances.
Note the following when using the new experience:
- Some features may not be complete just yet, as we're continuously iterating on these.
- Any pages discussing the new experience will not be available in the usual page sidebar.
We've linked the table of contents below, so you can easily navigate the documentation at any time.
- Portfolio for Jira 3.0 alpha documentation
- Setting up your alpha experience
- Comparing alpha and current versions
- What is a Portfolio plan
- Working with Portfolio plans
Your Portfolio plan has three (3) views, which let you focus on specific aspects of your plan. These views make it easier for you to monitor the current progress of multiple projects, and ultimately stop potential bottlenecks from happening, by spotting these bottlenecks before they even happen.
The roadmap view of your plan is where you plan and schedule issues across the projects you're managing, so your teams can know when to work on them accordingly.
The roadmap view has three (3) sections:
|Team capacity view||
The team capacity view helps you make sure that your teams do have the capacity to handle the issues that you're scheduling for them to work on.
In the team capacity view, you can do the following:
You can choose to create a team for a specific plan, or to share that team across multiple plans.
See Managing team capacity to know more about teams.
Portfolio for Jira dynamically loads issues from Jira into your plan, and then suggests the releases you can work with for the issues in your plan.
We're still iterating on how releases are managed in the new planning experience. This is why the dynamic release dates that have been optimized are not visible in the releases view just yet.
In the releases view, you can do the following:
You can choose to create project-specific releases, which are associated to one particular project, or cross-project releases, which give you a higher level view of your work since you can associate multiple projects with a cross-project release.
See Managing releases to know more about releases.