Content
View differences
Updated by Jens Ulferts 1 day ago
Follows ###AGILE-296
**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
* If the sprint start date is in the future future, an empty table is displayed.
* \[open\] Do we show a blank slate stating: "Work packages will appear here after the sprint starts."
blankslate?
* If dates are not set for the sprint, blankslates are shown.
* Each of those work package tables are
* baseline table if the reference date is a sprint start or finish date
* non baseline table if the reference date is the current date
* The widget is only displayed if the instance has an EE pro license
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.
* The widget will be EE (pro) only. Because of that, all users able to access the widget will have access to the baseline feature which is EE (basic).
**Technical notes**
* <br>
**Permissions and visibility considerations**
* View sprints (and by that view work packages) is required.
**Translation considerations**
* <br>
**Out of scope**
* Configuring the widgets
**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
* If the sprint start date is in the future
* \[open\] Do we
* Each of those work package tables are
* baseline table if the reference date is a sprint start or finish date
* non baseline table if the reference date is the current date
* The widget is only displayed if the instance has an EE pro license
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.
* The widget will be EE (pro) only. Because of that, all users able to access the widget will have access to the baseline feature which is EE (basic).
**Technical notes**
* <br>
**Permissions and visibility considerations**
* View sprints (and by that view work packages) is required.
**Translation considerations**
* <br>
**Out of scope**
* Configuring the widgets