Content
View differences
Updated by Jens Ulferts about 5 hours ago
**As** a an agile user \[enter role of user\]
**I want to** have an easy to understand burndown graph \[enter objective\]
**so that** I can quickly understand the sprint progress \[enter desired result\]
<img class="image_resized op-uc-image op-uc-image_inline" style="width:749px;" src="/api/v3/attachments/922292/content">
**Acceptance criteria**
* The existing burndown graph is reworked.
* The y-axis is the sum of story points (this unit needs to be flexible later - <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">###AGILE-198</mention>)
* The x-axis is the days between the sprint start and finish date
* \[open\] format of the dates
* Two data series exist
* Remaining work packages represents the actual reduction of work
* \[open\] is this name correct?
* The series represents the sum of story points per day of the work packages associated to the sprint in the project that are not closed (according to the backlogs settings for the project).
* The story point value factored in for a work package is the value at the end of each day (local time for the user), or the current date depending on which is earlier.
* The series stops at the current date if that is earlier than the sprint's finish date
* \[open\] should the current date be represented somehow in the graph
* Guideline represents the ideal reduction of work
* The series starts from the sum of story points at the sprint's start date and finishes at 0 at the sprint's finish date. Between those two, the series declines with a constant reduction. On non working days, there is no reduction as no work is expected to take place.
* \[open\] What to do if the story points were empty at the beginning and only assigned later on in the sprint?
* The non working days are displayed as a gray bar.
* A blankslate is displayed instead of a graph
* If the sprint doesn't have a start and an end date
* If the user has the "create sprint" permission, the blankslate includes the ability to set the date
* If the current date is before the sprint's start date
* If no work package has had any story point set throughout the sprint's interval
<br>
**Technical notes**
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_ languages_
**Out of scope**
* A change in the backlogs setting for the statuses considered closed affect the whole graph. <br>
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._
**I want to** have an easy to understand burndown graph
**so that** I can quickly understand the sprint progress
<img class="image_resized op-uc-image op-uc-image_inline" style="width:749px;" src="/api/v3/attachments/922292/content">
**Acceptance criteria**
* The existing burndown graph is reworked.
* The y-axis is the sum of story points (this unit needs to be flexible later - <mention class="mention" data-id="74098" data-type="work_package" data-text="###AGILE-198" data-display-id="AGILE-198">###AGILE-198</mention>)
* The x-axis is the days between the sprint start and finish date
* \[open\] format of the dates
* Two data series exist
* Remaining work packages represents the actual reduction of work
* \[open\] is this name correct?
* The series represents the sum of story points per day of the work packages associated to the sprint in the project that are not closed (according to the backlogs settings for the project).
* The story point value factored in for a work package is the value at the end of each day (local time for the user), or the current date depending on which is earlier.
* The series stops at the current date if that is earlier than the sprint's finish date
* \[open\] should the current date be represented somehow in the graph
* Guideline represents the ideal reduction of work
* The series starts from the sum of story points at the sprint's start date and finishes at 0 at the sprint's finish date. Between those two, the series declines with a constant reduction. On non working days, there is no reduction as no work is expected to take place.
* \[open\] What to do if the story points were empty at the beginning and only assigned later on in the sprint?
* The non working days are displayed as a gray bar.
* A blankslate is displayed instead of a graph
* If the sprint doesn't have a start and an end date
* If the user has the "create sprint" permission, the blankslate includes the ability to set the date
* If the current date is before the sprint's start date
* If no work package has had any story point set throughout the sprint's interval
* <br>
**Permissions and visibility considerations**
* _To whom is this feature visible?_
* _When is it not visible?_
**Translation considerations**
* _Key terms and phrases in the key languages_
**Out of scope**
* A change in the backlogs setting for the statuses considered closed affect the whole graph.
_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._