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 tables listing work packages of different criteria \[enter objective\]
**so that** I can understand the sprint's work package state in more depth \[enter desired result\]
**Acceptance criteria**
* The sprint report page has three work package tables as widgets
* "Completed work packages"
* Work packages associated to the sprint that are finished
* Reference date: sprint finish date or current date (earlier one)
* "Unfinished work packages"
* Work packages associated to the sprint that are not finished
* Reference date: sprint finish date or current date (earlier one)
* "Scope change after sprint start"
* Work packages added or removed from the sprint after the sprint start date
* \[open\] what to display if the sprint hasn't started yet
* Each of those work package tables are
* baseline table if the reference date is a sprint start or finish date
* \[open\] Baseline is an EE feature. What is displayed if that feature is not available.
* non baseline table if the reference date is the current date
Notes:
* "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)
* The widgets should always cover the full width
* While the sprint start and finish dates are dates (whithout time zones) the current user's local time for start or end of the day of that date is used. <br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br> _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 widgets changes._
**As** an agile user
**I want to** have tables listing work packages of different criteria
**so that** I can understand the sprint's work package state in more depth
**Acceptance criteria**
* The sprint report page has three work package tables as widgets
* "Completed work packages"
* Work packages associated to the sprint that are finished
* Reference date: sprint finish date or current date (earlier one)
* "Unfinished work packages"
* Work packages associated to the sprint that are not finished
* Reference date: sprint finish date or current date (earlier one)
* "Scope change after sprint start"
* Work packages added or removed from the sprint after the sprint start date
* \[open\] what to display if the sprint hasn't started yet
* Each of those work package tables are
* baseline table if the reference date is a sprint start or finish date
* \[open\] Baseline is an EE feature. What is displayed if that feature is not available.
* non baseline table if the reference date is the current date
Notes:
* "Finished" always refers to the work packages that have a status considered closed in the project (backlogs settings)
* The widgets should always cover the full width
* While the sprint start and finish dates are dates (whithout time zones) the current user's local time for start or end of the day of that date is used.
**Technical notes**
* <br>
**Permissions and visibility considerations**
* <br>
* _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