Sprint Status report comes in handy when you want to analyze status share from sprint to sprint.
| Table of Contents | ||||
|---|---|---|---|---|
|
Configuration
Once you added Issue History Collector Gadget as described here, the Configuration page appears.
Let's go and set up parameters for your report. Note that all fields are required.
| Metrics | Description | Configuration page |
|---|---|---|
Report type | Here you see the list of currently available reports. Select Sprint Status report. |
| |
Filter by | The report will be created based on Sprints. |
Item | Here you will see a list of all |
Sprints within your Jira Cloud instance. |
Make sure your Boards are not private to view the information by Sprints. | |
Status | Statuses that exist in the selected sprints are displaying. You can select as many statuses as you need. |
Assignee | Specify the users for whom you want to display data. |
Start and End date | Start and end date for the report. If you have chosen a longer time period than the Sprint dates, the information on the chart will be displayed within the Start and End dates of the Sprint |
. You can specify a shorter time interval than the Sprint date range if you only want to see data for a specific part of the Sprint. To display data for the current day, select the date of the next day as the end date. | |
Measure | A calculation can be shown in Days, Hours, or Minutes |
Update every 15 minutes
| . |
| Info |
|---|
Due to Jira Cloud architecture and depending Depending on the size of your projects and configuration options, it may take some time to display data for your gadget. Please wait and do not modify or and do not update the page. |
Usage
Sprint Status report allows you to explore Sprint performance by status. It It works perfectly for Agile teams.
Sprint Status report helps you:
- Easily compare how multiple scrum teams work including their Sprints on the chart together
- Track how how your team's behavior and workload change from Sprint to Sprint
- Analyze in which Sprint you had more tricky and time-consuming tasks
- Figure out when you spent more time on development and when on testing for example
- Identify in which Sprint your teammate was more efficient and hardworking and so on
...
- .
Enjoy and let us know what you think about it. We really appreciate your feedback and open to your suggestions.
What's next?
Take a look at other report types available in Issue History Collector Gadget: