Overview
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 provides you with a single source of truth into the current and future health of your initiatives. Using Portfolio for Jira, you can create reliable forecasts of the work of your teams in Jira, while keeping track of current work across realistic schedules in an ever-changing environment.
This is how a Portfolio for Jira plan looks like, with the new planning experience:
Before you begin
Take note of the following details when using the new experience:
| Managing plan permissions | As a Portfolio administrator, you can choose the users who can make changes in a plan, and the users who can only view a plan.
Sample plan permissions Note that plan permissions are plan-specific, so you'll need to make any necessary changes in each plan. See plan permissions for more details. |
| Viewing and managing your work | With the new experience, plans have three (3) views, which let you focus on specific aspects of your plan.
See What is a Portfolio plan to know more. |
| Planning your work | The new planning experience have a simpler, more intuitive interface for you to view and manage the issues in your plans. In the roadmap view of your plan, you have the following sections:
You can also filter the issues in your plan, so you can view only the work you need to focus on. You can filter your work by projects, releases, assigned teams, and even by the timeframe during which these issues are scheduled. See What is a Portfolio plan to know more. |
| Scheduling issues | You can schedule the issues in your plan by dragging and dropping the corresponding schedule blocks in the timeline, or by entering target start dates and target end dates for the issues. You can also drag either end of a schedule block, so work for the issue is scheduled for either a shorter or longer period of time. When scheduling child issues, the start dates and end dates of these issues roll up to the dates of their parent issues. Effectively, this means:
If you need some ideas on how best to schedule work for your teams, Portfolio for Jira can help you out by optimizing your plan for you. When optimizing your plan, Portfolio for Jira will:
See Scheduling work and Saving changes in Jira for more details. |
Saving changes in Jira |
|
| Managing team capacity | In the team capacity view, you can:
See Managing team capacity to know more about teams. |
| Managing releases | In the releases view, you can:
See Managing releases to know more about releases. |
| Opting in and out of the new experience | While we've released heaps of features and improvements, we understand that you may need some features that are not available yet. If this is the case, you may need to opt out of the new experience while we're building more functionality. We'll announce new features and improvements as we roll them out in future releases. Check out our release notes for updates. We hope you do opt in again, as we iterate on and release more features over time. See Setting up your alpha experience for more details. |
