Rolling values up to parent issues
このページの内容
関連コンテンツ
- Filtering issues
- The Roll-Up is not happening on date in Advanced Roadmap Plans
- Configuring the scope view
- Not possible to link 2 Jira issues together via the The Parent Link field from Advanced Roadmap
- Showing Portfolio custom fields in Jira
- Advanced Roadmaps sub story estimate reverts back after refresh
- Customizing view settings
- Tracking progress and status
- How to properly configure the Parent Link field on screens in Jira Data Center
- Advanced Roadmaps Progress (issue count) bar does not take into account nested issues
For parent issues, you can choose to display a preview of the rolled-up values (estimates, teams, and releases) of the child issues in the corresponding fields.
In the example below, the values of teams are being rolled up, from the child issues to the parent issues.
In this example, you have the parent initiative TIS-118, with the following child epics: PERF-2 and PERF-6. Drilling down further, PERF-2 is also the parent epic of the child stories PERF-3, TIS-128, and TIS-148. The teams for the child stories have already been selected.
With rolled-up values enabled, PERF-2 is displaying the rolled-up value of Performance Engineering for its team. The same team value then rolls up to the parent initiative, TIS-118.
This doesn't mean that these teams are set in stone — this is just a preview, and you can still choose the teams for the epic and initiative here. You can still even change up the teams of the child stories, if needed.
関連コンテンツ
- Filtering issues
- The Roll-Up is not happening on date in Advanced Roadmap Plans
- Configuring the scope view
- Not possible to link 2 Jira issues together via the The Parent Link field from Advanced Roadmap
- Showing Portfolio custom fields in Jira
- Advanced Roadmaps sub story estimate reverts back after refresh
- Customizing view settings
- Tracking progress and status
- How to properly configure the Parent Link field on screens in Jira Data Center
- Advanced Roadmaps Progress (issue count) bar does not take into account nested issues