Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16204

Remaining Estimate not updated with Split issue feature

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 7.5.1, 7.5.2
    • AgileBoard
    • None

      Summary

      When an issue is split, the remaining estimate of the issue is not adjusted to reflect the changes in the Original Estimate.

      Steps to reproduce:

      1. Set a Scrum board to use Original Estimate with Remaining Estimate as Estimate option.
      2. Access the backlog and set an estimate of an issue to 2weeks (example). Both Original & Remaining Estimates will be 2w.
      3. Right-click on the issue and click Split.
      4. Set the name of the split issue and adjust the estimate of the issue (1w + 1w as an example).
      5. Click save and check issue detail view of both issues. The remaining estimate of the original issue will remain at 2w. 

       

      Environment

      JIRA 7.5 and above. 

      Expected Results

      The Remaining Estimate is updated to reflect the changes with the Original Estimate

      Possible solutions:

      • Automatically adjust the remaining estimate
      • Let the user input the remaining estimate during the split action

       

      Actual Results

      The Remaining Estimate is not updated to reflect the changes with the Original Estimate
       

      Workaround

      Manually edit the Remaining Estimate

            [JSWSERVER-16204] Remaining Estimate not updated with Split issue feature

            JOCUO added a comment -

            Split issue is very helpful for future workflow and break down of early estimates in the backlog.

            Without the update to remaining estimate when splitting a task this feature has low value.

            JOCUO added a comment - Split issue is very helpful for future workflow and break down of early estimates in the backlog. Without the update to remaining estimate when splitting a task this feature has low value.

            Tanya Gordon added a comment -

            Hello All!

            Although this bug seems minor and not really important I would like to emphasize how much it affects our users. We're using Jira as our main ALM tool. About 400 users are planning their work quarterly. Each issue is estimated original to some amount of time. Then assigned to a sprint. If estimation is higher then sprint capacity it's splitted into smaller chunks and estimations are updated accordingly. Users find themselves browsing  and searching for the original issues and correcting the original estimation manually. This makes them feel annoyed and confused. Also, a lot of times, they just forget to update the estimation and this, of course, is shown later in the sprint report. 

            Please find a way to fix this bug, or find a better workaround for it (maybe using a script via script runner add on?..)

            Thanks,
            Tanya.

            Tanya Gordon added a comment - Hello All! Although this bug seems minor and not really important I would like to emphasize how much it affects our users. We're using Jira as our main ALM tool. About 400 users are planning their work quarterly. Each issue is estimated original to some amount of time. Then assigned to a sprint. If estimation is higher then sprint capacity it's splitted into smaller chunks and estimations are updated accordingly. Users find themselves browsing  and searching for the original issues and correcting the original estimation manually. This makes them feel annoyed and confused. Also, a lot of times, they just forget to update the estimation and this, of course, is shown later in the sprint report.  Please find a way to fix this bug, or find a better workaround for it (maybe using a script via script runner add on?..) Thanks, Tanya.

              Unassigned Unassigned
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              10 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated: