Content
View differences
Updated by Jens Ulferts 1 day ago
Follows ###AGILE-296
**As** an agile user a \[enter role of user\]
**I want to** have an overview over the work packages that are part of the sprint \[enter objective\]
**so that** I can quickly take in the key figures \[enter desired result\]
**Acceptance criteria**
* The sprint report page has a widget showing figures about the work packages of the sprint
* The widget is titled "Work packages"
* If possible, the number of work packages currently associated to the sprint are displayed as a pill after the title
* The widget has a progress bar depicting the number of total work packages, the number of finished work packages and the percentage that results in.
* The widget deliberately does not span the whole width on wide screens. The exact width will need to be identified during implementation.
* The widgets shows an additional row of information blocks below the progress bar:
* Each block has a heading, a number representing the total number of work packages and a number representing the sum of story points for those work packages.
* The heading might point to a baseline table view or a non baseline table view
* Baseline table view: the reference date (see the blocks) is the sprint start or finish date.
* \[open\] baseline view is an EE feature. What do we display if the instance does not have that feature?
* Non baseline table view: the reference date (see the blocks) is the current date.
* The information blocks for work packages are:
* "Initially planned" - those are the work packages assigned to the sprint on sprint start. The sprint start is the sprint start date.
* Reference date: sprint start or current date (the earlier of the two)
* "Changed after start"
* \[open\] which work packages are displayed here. Only those added after sprint start or also those removed from the sprint or the total of those
* "Completed" - those are work packages considered finished
* Reference date: sprint finish or current date (the earlier of the two)
* The number representing the total number of work packages is green.
* "Unfinished"- those are work packages not considered finished.
* Reference date: sprint finish or current date (the earlier of the two)
* The number representing the total number of work packages is red.
* The information blocks are displayed in a single line (4x1) if space permits. If there is less width, that changes to a 2x2 layout and eventually to a 1x4 layout.
* The exact breakpoints will need to be identified during implementation
Notes:
* "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)
* Some layout decisions will need to be taken during implementation. Contact <mention class="mention" data-id="100056" data-type="user" data-text="@Julia Racsko">@Julia Racsko</mention> for confirmation. <br>
**Technical notes**
* It might not be possible to have links in the <br>
**Permissions and visibility considerations**
* Users having the "view sprints" permission can see the sprint goal widget _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* <br> _Key terms and phrases in the key languages_
**Out of scope**
* Configuring <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the widget
* Displaying a different unit than story points (this will change with <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">###AGILE-198</mention>
* The sprint start and end dates and the current date are the only relevant dates. The point in time when a sprint was switched to "Started" or "Completed" is not relevant. changes._
**As** an agile user
**I want to** have an overview over the work packages that are part of the sprint
**so that** I can quickly take in the key figures
**Acceptance criteria**
* The sprint report page has a widget showing figures about the work packages of the sprint
* The widget is titled "Work packages"
* If possible, the number of work packages currently associated to the sprint are displayed as a pill after the title
* The widget has a progress bar depicting the number of total work packages, the number of finished work packages and the percentage that results in.
* The widget deliberately does not span the whole width on wide screens. The exact width will need to be identified during implementation.
* The widgets shows an additional row of information blocks below the progress bar:
* Each block has a heading, a number representing the total number of work packages and a number representing the sum of story points for those work packages.
* The heading might point to a baseline table view or a non baseline table view
* Baseline table view: the reference date (see the blocks) is the sprint start or finish date.
* \[open\] baseline view is an EE feature. What do we display if the instance does not have that feature?
* Non baseline table view: the reference date (see the blocks) is the current date.
* The information blocks for work packages are:
* "Initially planned" - those are the work packages assigned to the sprint on sprint start. The sprint start is the sprint start date.
* Reference date: sprint start or current date (the earlier of the two)
* "Changed after start"
* \[open\] which work packages are displayed here. Only those added after sprint start or also those removed from the sprint or the total of those
* "Completed" - those are work packages considered finished
* Reference date: sprint finish or current date (the earlier of the two)
* The number representing the total number of work packages is green.
* "Unfinished"- those are work packages not considered finished.
* Reference date: sprint finish or current date (the earlier of the two)
* The number representing the total number of work packages is red.
* The information blocks are displayed in a single line (4x1) if space permits. If there is less width, that changes to a 2x2 layout and eventually to a 1x4 layout.
* The exact breakpoints will need to be identified during implementation
Notes:
* "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)
* Some layout decisions will need to be taken during implementation. Contact <mention class="mention" data-id="100056" data-type="user" data-text="@Julia Racsko">@Julia Racsko</mention> for confirmation.
**Technical notes**
* It might not be possible to have links in the
**Permissions and visibility considerations**
* Users having the "view sprints" permission can see the sprint goal widget
* _When is it not visible?_
**Translation considerations**
* <br>
**Out of scope**
* Configuring
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of
* Displaying a different unit than story points (this will change with <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">###AGILE-198</mention>
* The sprint start and end dates and the current date are the only relevant dates. The point in time when a sprint was switched to "Started" or "Completed" is not relevant.