Scope report
Reports
On this page
Related content
- Find the smart value for a field
- Key concepts
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- Jira automation triggers
- Get started with Jira automation
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- Jira automation conditions
- Automation should be triggered only when specific field is changed, but it's considering all issues' updates
- Automation Rules for Issue Created trigger are not working when using Proforma fields
The scope report shows the global to-do list for the upcoming releases. It is usually composed of three key hierarchical levels by default:
- Epics - Once the higher level priorities are settled it's necessary to break them down into large pieces of work, which consist of multiple stories.
- Stories - User stories capture functionality requirements.
- Sub-task - Work components that make up stories.
The new hierarchy model allows you to create and customize unlimited hierarchical levels.
You can configure your scope view following these simple steps:
- Go to your plan > Reports > Switch report > Scope.
- Select the elements that you want to see in the scope columns.
Now you can see the selected elements in the main scope view. Select the drop-down menu located on the right-hand side of the scope view to change which hierarchy level is being displayed.
Filter Description Title Issue title Releases Releases the issue is assigned to. Estimates (h) Time estimate of the issue. Team Team name Members Team members Sprints Team members assigned to the issue. Epic Epic title Themes Show the themes assigned to each issue. Issue status Issue status Progress Issue progress bar Source Source where the issues are being pulled in from.
Related topics
Last modified on Jan 15, 2018
Related content
- Find the smart value for a field
- Key concepts
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- Jira automation triggers
- Get started with Jira automation
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- Jira automation conditions
- Automation should be triggered only when specific field is changed, but it's considering all issues' updates
- Automation Rules for Issue Created trigger are not working when using Proforma fields
Powered by Confluence and Scroll Viewport.