Details
-
Suggestion
-
Resolution: Fixed
Description
Resolving an issue should put the estimated time remaining to 0.
To be consistent, on the user interface that allows reopening an issue you should be able to enter a value for Estimated time remaining.
This is very annoying. Is there something I missed or do not understand?
Attachments
Issue Links
- duplicates
-
JRASERVER-29812 When "closing"/"integrating" an issue - set remaining effort to zero
- Closed
- is duplicated by
-
JRASERVER-14673 Issue "Remaining Estimate" does not deduct "Sub-Task" original estimate for Sub-Tasks which are resolved.
- Closed
-
JRASERVER-2514 Closed issues still show up as incomplete in time tracking
- Closed
-
JRASERVER-3662 prompt for time entry on 'resolve issue'
- Closed
-
JRASERVER-3971 Estimated Time Remaining set to Zero
- Closed
- is related to
-
JRASERVER-961 Make more use of time tracking features
- Closed
-
JRASERVER-2860 Allow filtering on work log information
- Closed
-
JRASERVER-3011 More strict rules for time tracking
- Closed
-
JRASERVER-13512 Setting remaining time to 0 in a post function of the workflow causes the original estimate to be set to 0 as well (only when no time was logged by the assignee)
- Closed
-
JRASERVER-26067 Atlassian-supported workflow should include setting Estimated Time Remaining to zero
- Closed
- relates to
-
JRASERVER-868 Resolve & Time spent
- Closed
-
JRASERVER-2580 Ability to configure the workflow by project or issue type
- Closed