Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-1993

Resolving an issue should automatically put the estimated time remaining to 0

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    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

          Suggestion - JRASERVER-29812 When "closing"/"integrating" an issue - set remaining effort to zero

          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-14673 Issue "Remaining Estimate" does not deduct "Sub-Task" original estimate for Sub-Tasks which are resolved.

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-2514 Closed issues still show up as incomplete in time tracking

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-3662 prompt for time entry on 'resolve issue'

          • Closed

          Suggestion - JRASERVER-3971 Estimated Time Remaining set to Zero

          • Closed
          is related to

          Suggestion - JRASERVER-961 Make more use of time tracking features

          • Closed

          Suggestion - JRASERVER-2860 Allow filtering on work log information

          • Closed

          Suggestion - JRASERVER-3011 More strict rules for time tracking

          • Closed

          Suggestion - 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

          Suggestion - JRASERVER-26067 Atlassian-supported workflow should include setting Estimated Time Remaining to zero

          • Closed
          relates to

          Suggestion - JRASERVER-868 Resolve & Time spent

          • Closed

          Suggestion - JRASERVER-2580 Ability to configure the workflow by project or issue type

          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 120h
                  120h
                  Remaining:
                  Remaining Estimate - 120h
                  120h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified