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; } } }

How to Edit Estimates field in Jira plan

unknown

Hi All,

Whenever I try to update the Estimates (h) field in Jira plans it ends up updating the time remaining field.
Is there another way where I can get this to updated under the "Original Estimate" field?

Screen Shot 2021-10-26 at 1.32.40 pm.png Screen Shot 2021-10-26 at 1.34.28 pm.png

I'm currently using Tempo planner and as default it requires me to update the Original Estimate section for resource planning. I find it easier for Jira users to update their Due date and Estimates in plans rather than updating them for each task individually.

Please let me know if there's a workaround for this

Accepted answers

Walter Buggenhout

Hi @[deleted],

Unfortunately, the original estimates field is not available in Advanced Roadmaps. There is a feature request for it in the backlog: JSWCLOUD-20483 that you may watch and vote for.

I do believe though that this is not really an oversight in Advanced Roadmaps, but rather a very conscious decision. AR is a management tool with a strong focus on when your teams will be able to deliver work. And for that matter, remaining estimates are the ones that matter, once work has started.

It is a best practice to not update your original estimates anymore once you start working on an issue. If you do, you no longer have the ability to see what your original estimate actually was. You have probably noticed that Jira automatically copies your original estimate over to the remaining estimate field as soon as you enter it for the first time. By only updating remaining estimates from that point onwards (by logging work or manually applying corrections) you can get a view of the quality of your estimates.

As a workaround, I have seen suggestions to create an additional custom field to duplicate the original estimate and import that in your plans. That implies some overhead, obviously, but is a potential option to tackle a classic challenge in agile environments to list original original estimates at e.g. Epic level while not all stories have been defined in Jira yet.

Hope this gives you some useful pointers!

All comments

Walter Buggenhout

Hi @[deleted],

Unfortunately, the original estimates field is not available in Advanced Roadmaps. There is a feature request for it in the backlog: JSWCLOUD-20483 that you may watch and vote for.

Hope this gives you some useful pointers!

unknown

Hi @Walter Buggenhout ,

Thanks for your answer, I did create a customer number field and added it to my plans. But the issue here is Tempo planner.

It only recognises "Original Estimate" from Jira field and nothing else.

Is there a way for me to copy over the value entered in my custom field to "Original estimate" ?

Walter Buggenhout

You might be able to pull that off with Automation, but it may require some advanced stuff to update the original estimate field correctly.

You could trigger your rule from Field Value Changed on your custom field and as action update the Original Estimate field. But if I am not mistaken, Jira stores this type of data in milliseconds in the database. So you may have some searching to do to find the proper format.

And once more, I can't stress enough to be careful what other processes you might be impacting when you start updating original estimates in the system!

unknown

Hi @Walter Buggenhout

In that case I will reach out to Tempo and get their estimates based on Time remaining and not from Original Estimates

Thanks for your answers

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

jira-software-cloud