Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Fixed
Fix Version/s: 4.2
Component/s: Issue - Time Tracking & Worklog
Labels:
- dreamteam

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?

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

(5 is related to, 2 relates to)

Assignee:: Unassigned
Reporter:: fbeauregard2
Votes:: 69 Vote for this issue
Watchers:: 38 Start watching this issue

Created:: 10/Jul/2003 7:39 PM
Updated:: 19/Sep/2019 6:06 AM
Resolved:: 22/Oct/2010 6:09 AM

Estimated:

120h

Remaining:

120h

Logged:

Not Specified

Details

Description

Attachments

Issue Links

Activity

People

Dates

Time Tracking