nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Remaining time is not updated when estimating a new issue

Maximiliano Cruz

I notice that I cannot report an issue in slack, so I ask it here to see if anyone can solve it:

Error: When estimating a new task, remining time is not updated (it remains undefined)

Expected behavior: Remaining time should be updated to match the estimated time.

Thanks!

Accepted answers

All comments

Petter Gonçalves

Hello Maximiliano,

Welcome to Atlassian Community!

Can you please provide us a screenshot displaying how you are configuring your time estimation? If possible, could you please provide us with a fast video reproducing the problem?

By default, the Remaining Estimate field should be automatically calculated with the same value as the Original estimate field, getting lower when the time is logged (Remaining Estimate = Original Estimate - Logged work).

If this is not happening, I believe you have manually configured a default value for the remaining estimate field or a post function is configured to clear the value when transitioning the issue.

We will be waiting for the information required to better troubleshoot the issue.

Leo Jankowski

This is happening to me as well. I go to add an estimate on the right panel of the backlog view, but when I put the ticket in the sprint there is discrepancy between original and remaining. I can only update remaining by going into the ticket, then old view, then clicking edit to update.

This is extremely frustrating and a relatively new issue.

Anne Gallant

This is occurring for me as well. I have attached a screenshot.

The original estimate was 1 day and then it was changed to 3 days, but the remaining time shows the originally estimated time.

updated estimate.JPG

iCentris Admin

Also happening for me.

Anne Gallant

It seems that the Estimated and Remaining fields are not linked, thus if 2 hours are added to the estimated time manually then 2 hours must be also added to the remaining time. I do not work for Atlassian so I cannot say if this is how they intended for these fields to work but my validation has determined that this is how it is working.

Petter Gonçalves

Hello Anne,

It is correct to say that if you manually set both the remaining and original estimate, they will be not linked.

However, if you fill the original estimate and leave the remaining estimate field empty, both fields will be properly receiving the same value and both fields would be linked.

Kevin Palm

I am experiencing the same problem:

When I enter a value for the estimate, it's value is taken over to the remaining-field (because it was empty before).

But when I now adapt the estimate, then the remaining is not updated, and it still contains the old (wrong) estimation value :-(

Changing both fields by hand is very time annoying and time-consuming (with the old ticket view this was faster since both fields were directly editable in the edit-view)

Manali Butey_74pgd2

@Petter Gonçalves - what about when the 'original estimate' field is update while some time had already been logged ? would remaining estimate field still be automatically updated ?

Andrea Santi

@Petter Gonçalves Hi. I know this is super-old but can you provide a feedback on this? We are getting the same problema:

The first time we set the "original estimate" a value is copied in "remaining estimate"
Next updates to "original estimate" leave the "remaining estimate" field untouched.

Is this the expected behaviour?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud