Content
View differences
Updated by Jens Ulferts 4 days ago
**As** an agile user
**I want to** have a sprint overview page with an overview of the sprint
**so that** I can easily understand what happened in the sprint
**Acceptance criteria**
* There is a sprint report page
* The header shows:
* the breadcrumb: \[Project name\] / Backlogs / \[Sprint All sprints / Sprint "\[Sprint name\]" report
* \[open\] Why not use \[Project name\] / Report
Backlogs / Sprint "\[Sprint name\]" / Report?
* The title: \[Sprint name\] 'Sprint report "\[Sprint name\]"'
* The status of the sprint
* The dates of the sprint
* A single, static widget is displayed on the page (subject to change later)
* overview over wp # within the burndown chart is moved from its full page inside the widget. Its functionality is unchanged. sprint
* \[open\] if not dates are set on number of work packages initially planned for the sprint, sprint
* number of work packages completed
* number of work packages unfinished
* number of work packages added additionally to the burndown chart cannot be rendered. Do we hide sprint during the widget then completely or show a message informing the user about the need for the dates? sprint
* \[note\] The specification on this widget is still changing. It might well be that e.g. <mention e.g. <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">###AGILE-198</mention>will have to be taken into consideration, especially if "work" or " none" is selected as the unit.
* Probably, the burndown chart will need to be able to work with those different units.
* When on the report page, the "All sprints" menu item is selected
* The page can be accessed:
* via all sprints index page
* Every row gets a ... menu at the end. The menu contains the following items:
* Edit sprint - changing the name and dates \[open\] How will necessitate a reload of this be triggered? For completed sprints, it could replace the page
* Sprint report - takes the user main link currently pointing to the sprint report
* Sprint board - takes work package list. For the user to planned one, replacing the sprint board
main link is probably not desirable. Adding a menu per row is probably preferable.
* via ... menu on sprints within the "backlog and sprints" page
* The "Burndown chart" menu item will be replaced by the link to the report page (if the feature flag is active)
* ~~from from the sprint board~~ board
* We \[open\] we currently cannot control the headers. This will only be possible with the reworked boards view.
* The feature is hidden behind a feature flag. This is done so that additional widgets can be added one by one before it is released to the public.
**Technical notes**
* The page will be static. There is no possibility whatsoever for the user to configure it. But the page should look like a dashboard so that a configurable dashboard can later replace it.
**Permissions and visibility considerations**
* Users allowed to view the sprint are allowed to see the page and its contents.
**Out of scope**
* Manipulating the report page (subject to change)
* Show additional widgets (subject to change)
<br>
**I want to** have a sprint overview page with an overview of the sprint
**so that** I can easily understand what happened in the sprint
**Acceptance criteria**
* There is a sprint report page
* The header shows:
* the breadcrumb: \[Project name\] / Backlogs / \[Sprint
* \[open\] Why not use \[Project
* The status of the sprint
* The dates of the sprint
* A single, static widget is displayed on the page (subject to change later)
*
* \[open\] if not dates are set on
* number of work packages completed
* number of work packages unfinished
* number of work packages added additionally to
* \[note\] The specification on this widget is still changing. It might well be that e.g. <mention
* When on the report page, the "All sprints" menu item is selected
* The page can be accessed:
* via all sprints index page
* Every row gets a ... menu at the end. The menu contains the following items:
* Edit sprint - changing the name and dates
* Sprint report - takes the user
* Sprint board - takes
* The "Burndown chart" menu item will be replaced by the link to the report page (if the feature flag is active)
* ~~from
* We
* The feature is hidden behind a feature flag. This is done so that additional widgets can be added one by one before it is released to the public.
**Technical notes**
* The page will be static. There is no possibility whatsoever for the user to configure it. But the page should look like a dashboard so that a configurable dashboard can later replace it.
**Permissions and visibility considerations**
* Users allowed to view the sprint are allowed to see the page and its contents.
**Out of scope**
* Manipulating the report page (subject to change)
* Show additional widgets (subject to change)
<br>