Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-88465

Logging time on an issue results in incorrect allocated hours on sprint flyout

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Timed out
    • Icon: Low Low
    • Plans - Timeline
    • None

      Issue Summary

      Using time based estimation means that sprint progress is lost when logging time on issues

      Steps to Reproduce

      1. Create a plan that uses day based estimates
      2. Use a scrum board as the issue source
      3. Create sprints on that board
      4. Create some issues on the backlog
      5. Set a weekly hours to 200 and iteration length to 3
      6. Add an issue to a sprint and give it a 10 days estimate
      7. The sprint progress will show 10/75 allocated hours
      8. Go to the issue and log 5 hours of work

      Expected Results

      The sprint fly-out should still show 10/75 allocated hours.

      Actual Results

      The sprint fly-out now shows 5/75 allocated hours. If you then log the remaining 5 hours and complete the issue it now shows 0/75 hours. This gives the false impression that there is available capacity in the sprint. 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              ddraper@atlassian.com Dave
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: