-
Suggestion
-
Resolution: Won't Fix
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
This issues is related to JRA-1423 and JRA-1993 but is distinct.
As a user, I want an Atlassian-supported workflow to set the Estimated Time Remaining to be set to zero when resolving or closing an issue.
The aforementioned bugs indicate a clear need by many people to zero the Estimated Time Remaining on issues upon closing or resolving. The info note on the JIRA close issue form even states "Closing an issue indicates that there is no more work to be done on it, and that it has been verified as complete," which indicates to me that zeroing the remaining time is the expected behavior. This was partially mitigated when using GreenHopper as the close/resolve screens had the default option to zero the remaining time, but this useful feature has been removed from those GreenHopper screens.
Requiring every user to manually add post functions is error-prone and places an undue burden on the end-user. I would prefer this action to be part of the default system workflow; however, it would be acceptable to provide a second system workflow or the option to add the zeroing behavior to the default.
- is related to
-
JRASERVER-26067 Atlassian-supported workflow should include setting Estimated Time Remaining to zero
- Closed
-
JSWCLOUD-8340 Burndown report includes time remaining from Resolved and Closed issues.
- Closed