-
Suggestion
-
Resolution: Answered
-
None
-
None
When a mistype in the Original Estimate field is made and it is corrected(say from 9weeks to 9hours) there is still a spike in the Burndown Chart.
This feature request is open to look into the possibility of having a way to remove the initial Original Estimate value so it does not affect the Burndown Chart.
- relates to
-
JSWSERVER-10753 Mistakes when setting remaining estimates cannot be corrected for the burn down chart, possibly rendering it unreadable and useless.
- Closed
- mentioned in
-
Page No Confluence page found with the given URL.
Form Name |
---|
[JSWSERVER-8477] As a user, I would the ability to correct mistypes in Estimations without a spike in the Burndown Chart
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 128710 ] |
Workflow | Original: JAC Suggestion Workflow [ 3069871 ] | New: JAC Suggestion Workflow 3 [ 3663144 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2626883 ] | New: JAC Suggestion Workflow [ 3069871 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2325763 ] | New: Confluence Workflow - Public Facing v4 [ 2626883 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2042803 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2325763 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030873 ] | New: JIRA PM Feature Request Workflow v2 [ 2042803 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 736614 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030873 ] |
Labels | Original: affects-server | New: affects-cloud affects-server |
Labels | New: affects-server |
Attachment | New: Burndown mess, WEL-Feature-sprint-2.PNG [ 207071 ] |