You can now plan work for your teams using the new experience in Portfolio for Jira. Check out our documentation to get started.
While using the new functionality, note that some features are not complete yet, as we continuously iterate on the functionality. Send us any feedback you may have via the give feedback icon in your plan. This will help us validate the work we've done so far, towards building the best planning experience for you.
When planning work, you're likely to be managing multiple issues that span multiple projects. It's easy to lose track of your work at one point or another, when you're across multiple work streams.
The roadmap view of your plan lets you see all the work that's relevant to you. With the new experience, you can use the different elements in this view, so you can focus on only the relevant details. For example, you can deep-dive into the details by narrowing down the available filters, or go wider by expanding the timeframe or hierarchy levels.
|1||Select the hierarchy levels from which and to which you want to view issues.|
Use filters to display the relevant issues in your plan, like projects, releases, teams, issue details, and more.
Choose the issue details that you want to display in your plan, which include:
To display these issue details, you'll need to add fields to your plan. These fields will be displayed as columns, and each field contains the corresponding issue detail. You can also remove fields from a plan, and reorder the fields in your plan.
Note that the order of the columns in the fields section depends on the order that you add the fields to your plan. We're currently iterating on the best way to reorder fields.
Above the timeline section, configure the timeframe settings as needed:
Notes when configuring timeframe settings
You may have issues with target start dates or target end dates that go beyond the selected timeframe. For such issues, you'll see an arrow at the end of the schedule block — this arrow indicates that the target date goes beyond the timeline.
In the example below, the selected timeframe is 1 year (1Y), and the highlighted issue has a start date of 5 Mar 18, which goes beyond the timeline.
By clicking the arrow of the schedule block, the timeframe updates into a custom date range, as shown below.
View the details of a release in your plan. This is helpful in monitoring if any releases are off track.
|6||Expand an issue to view its child issues.|
The schedule block, which represents the schedule duration of an issue in a plan, based on the target dates that have been set for the issue.
Ideally, an issue would have both target start and target end dates, but it's quite possible for an issue to have just one of the dates. In this case, the schedule block displays in a solid color on the end of the target date that's been set. The solid color gradually fades towards the other end of the schedule block, where the target date hasn't been set.
At the bottom of the scope section, you'll find the issues without parent section, which displays the issues that do not belong to any parent issue.
This section also displays the issues according to their hierarchy levels. Expand a hierarchy level to view the issues of that hierarchy level.
It can be easy to lose focus when you're planning work across multiple projects, releases, teams, and other factors. By filtering the work that's displaying in your plan, you can focus your attention on a specific scope of your plan, as needed.
In the new experience, you can use any of the following filters.
|プロジェクト||Choose the relevant projects, from the projects that are being used as issue sources in the plan.|
|リリース||Choose the relevant releases, from the releases that are included in the plan.|
|課題の詳細||Filter issues by entering either the issue key or issue summary.|
|チーム||Choose the relevant teams, from the teams that exist in the plan.|
Choose to show any of the following:
You can also use multiple filters, to further narrow down on the work you're trying to focus on. For example, you can filter only the issues that have dependencies, and that are assigned to v3.0 release.
Note that there may be times when some issues won't be returned, because of the multiple filters that have been applied. In the example above, even if the issue TIS-67 has dependencies, the issue might not be returned because it is not assigned to v3.0.