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

Time remaining should change based on changes made to Original estimate

XMLWordPrintable

    • 37
    • 45
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      The Time remaining of an issue should change accordingly if you adjust the Original estimate of an issue before any time is logged in the issue.

      Currently issues might not have their time remaining adjusted upon an Original estimate change even if no time was logged.

      Steps to Reproduce

      • Add a value to the Original estimate and see the Time remaining being adjusted
      • Now change the Original estimate again

      Expected Results

      If not time has been logged in the issue the time remaining will be updated accordingly.

      See the recording: Time remaining adjust.mp4

      Actual Results

      The time remaining might not change according to the Original estimate even if no time has been logged in the issue.

      Workaround

      Using Automation for Jira, you can update the "Remaining estimate" field by comparing the Original Estimate field value and the total Time spent Worklog entry.

      Please find the rule details below:

      Rule Trigger:
      Field value changed (Time tracking)

      If: Condition
      => If: Advanced compare

      {{triggerissue.worklog.timeSpentSeconds.sum}}
      
      Equals
      
      0
      

       => ActionEdit Issue
      Set the Remaining estimate field value as the below smart value:

      {{#=}}{{timeoriginalestimate}}/60{{/}}m

              Unassigned Unassigned
              lalmeida@atlassian.com Leonardo De Almeida
              Votes:
              89 Vote for this issue
              Watchers:
              44 Start watching this issue

                Created:
                Updated: