Configuring the scope view
The scope in Portfolio for Jira is the global to-do list for upcoming releases for your work.
The scope is comprised of three (3) hierarchy levels by default:
- Epics - Once higher-level priorities are settled, it's necessary to break them down into large pieces of work, which consist of multiple stories.
- Stories - These are the user stories capture functionality requirements.
- Sub-task - These are the work components that make up stories.
Though these are the default hierarchy levels, you can still create and customize unlimited hierarchical levels in Portfolio for Jira.
Viewing issues in the scope table
- Go to your plan via Portfolio (in header) > View Portfolio > click your plan.
- Click the Scope tab to display the scope table.
- From the hierarchy menu, click the hierarchy level for the issues that you want to display in the scope table.
- In the scope table, click an issue to view more details about the issue on the right panel that appears.
Note that when you click an issue, that issue will also be highlighted in the timeline.
The scope table displays the following issue details:
|1||#||Position or ranking of the issue in the scope table|
|2||タイトル||Title of the issue|
|3||リリース||Release to which the issue is currently assigned|
|4||見積もり||Time estimate of the issue|
|5||初期見積||Original time estimate of the issue, if any|
|6||Progress||Current progress of the issue|
|7||チーム||Team that the issue is currently assigned to|
|8||Members||Members of the team to which the issue is currently assigned|
|9||Sprint||Sprint to which the issue is currently assigned|
|10||Earliest start date|
The earliest date when work for the issue will start.
Read more about how the earliest start date works
The earliest start date is a constraint that guarantees that an issue is not scheduled before the date that you define. This applies even if the issue has a higher priority relative to other issues in the backlog, and even if there are free resources to work on that issue.
|11||Target start date|
The date when work for the issue is targeted to start – this has no impact on schedule calculation
|12||Scheduled start date|
The date when work for the issue is scheduled to start, based on the data provided in the plan
|13||Target end date|
The date when work for the issue is targeted to be concluded – this has no impact on schedule calculation
|14||Scheduled end date|
The date when work for the issue is scheduled to be completed, based on the data provided in the plan
Initiative to which the issue belongs to, if any.
If you're using the default hierarchy configuration in Portfolio for Jira, initiatives would only display if you're viewing issues at the epic level.
Epic to which the issue belongs to, if any.
If you're using the default hierarchy configuration in Portfolio for Jira, epics would only display if you're viewing issues at the story level.
Label assigned to the issue, if any.
Labels are usually keywords or tags that you can add to your issues, as a means to categorize work.
Component assigned to the issue, if any.
Components are usually sub-sections of a project. These are used to group issues within a project into smaller parts.
|19||テーマ||Theme assigned to the issue, if any|
Current status of the issue in the workflow.
By default, Portfolio for Jira considers an issue to be "completed" when it is assigned to any status of the "done" category.
|21||Progress||Current progress of the issue|
|22||ソース||The board, project, or filter from which the issue is pulled from|
Configuring the details in the scope table
You can choose which issue details to display in the scope table. This is handy when you just want to quickly view specific details about the issues in your plan.
- In the scope table, click .
- Click the issue details that you want to display in the scope table.
Try one of the following steps to make your issues appear in your plan:
- Make sure the fixVersion field is not hidden for that issue type.
- Check if there are any view filters configured for your plan that exclude the issues not appearing.
- The issues not appearing may not have been given a resolution value, such as unresolved.
- The issues may have already been completed.
- The issues may be within a release that's excluded from your plan.
- The issues were manually excluded when creating your plan. For instance, when you exclude an epic during plan creation, the child stories of that plan are also excluded.
This is currently a problem with issues that are created and committed for particular issue sources. If the issue source is a filter or board, and the queries used for that source require a specific field value, then that field value won't be applied when creating issues.
We're working on a solution for this, but for now, we recomend you use an agile board for your filter, and then initially create your issues on that board. In most cases, the required filter values will be automatically added to the issue.
This can happen if there is no active sprint. To fix this, change the "Completion date" filter to something other than "Current sprint."
For example, in your plan, go to More > Completion date.