You can also see the Opsgenie alert chart for your Jira Software project. If your board is configured to track remaining estimates and time spent, a green line will display in the Sprint Report, indicating work logged on issues. It also reflects issues that are added or removed from the sprint. Note that the red line shows the current total estimate for unresolved issues at any point in the sprint. The red line represents actual work done during the sprint - it's drawn from the total estimate of the issues at the start of the sprint, and it goes higher or lower as your team works on the issues in the sprint. The grey line stays flat during non-working days. The grey line is a guideline that's drawn from the total estimate of the issues at the start of the sprint, to 0 at the end of the sprint. Similarly, an issue is considered to be 'Done' when it is in a status that has been mapped to the right-most column of your board. See Configuring columns for more information. Issues added after the sprint starts are indicated with an asterisk.Īn issue is considered to be 'To Do' when it is in a status that has been mapped to the left-most column of your board. The Sprint Report is board-specific – that is, it will only include issues that match your board's saved filter. The following information will help you understand the key functionalities of the Sprint Report: Select the relevant sprint from the sprint drop-down.īefore you start using the Sprint Report, you should get to know how it works. (Only estimates on parent issues are included.)Ĭlick Projects in the navigation bar and select the relevant project. Before you beginĮstimates on sub-tasks are not included in the Sprint Report. See Linking a Confluence page to a sprint for details. If you have Jira Software connected to Confluence, you can create a 'Retrospectives' page via the Linked pages link.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |