Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Estimates in Advanced Roamaps doesn't update ticket estimate

I love how easy it is to create Epics and Stories in Advanced roadmaps but the Estimate field does not transfer to the ticket in either the Story Points or Original Estimate field. 

If I create a ticket via the Create button with a Story Point that does not translate to the estimate field.

If I add an original estimate time it does show on Advanced Roadmaps - yay! But if I change the Estimate on Advanced Roadmaps and save it. There is no update in the ticket. 

Is this a bug? Oversite? Or is there another way I should be managing estimates in ticket so what I change in one area is reflected in the other?

1 answer

1 accepted

1 vote
Answer accepted
Pete Morris
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 24, 2020

Hi @Channing Childs !

I'm super happy to hear you're enjoying Advanced Roadmaps!

Depending on your chosen estimation method (Cog next to the plan's name -> Scheduling -> Estimation), Advanced Roadmaps will show either a "Story points" field or an "Estimates (h/d)" field. "Story points" maps directly to the "Story points" field on the issue once changes are committed via the Review changes dialog. "Estimates (h/d)" actually maps to "Time remaining" which can be found in the "Time tracking" section on the Jira issue.

Screen Shot 2020-06-25 at 10.44.59 am.png

The confusion here arises from the fact that updating "Original Estimate" the first time will automatically transfer to the "Time remaining" field, but subsequent changes do not. Advanced Roadmaps does not reference the "Original Estimate" field at all.

I hope that helps. Please let me know if you have any other problems.

Peter Reiser
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jun 25, 2020

@Pete Morrish 

We are using Advanced roadmap to plan our estimation "budget (h)" of a ticket.

We need to set the original estimate as the "budget (h)" and then we book time spent (h) against  original estimate (h) to measure budget (h).

We cannot use "Time Remaining" as the budget (h).

So I think to correct behaviour would be to set "Original Estimate" if it's empty.

With the current implementation we have to manually set the "Original Estimate" per ticket which makes the use of advanced roadmap pretty useless :-(

I think this is a pretty standard use case and should be covered by Advanced Roadmap

Like # people like this

@Pete Morris thanks so much for clarifying. This should be updated in the documentation as I could not find this anywhere. 

I'd love help with my question here too!

Like Jo Beck likes this

We also need to have the estimate written into "original estimate". Can this be made configurable in any way??

Like Kelli Bryant likes this

Hi all, any update to this? Can this be done by some automation rule?

Fixing this would be awesome.

We have built an automation that copies the Time Remaining to the Original Estimate field if the Original Estimate is blank.

Hi @Garth Hume and all, can you share how did you manage to copy the RTE to OTE?

We have stuck between Advanced Roadmaps - which do not update the OTE and the Scrum boards which do accept only OTE as an estimate. So unless we find a way to copy the RTE to OTE - using Advanced Roadmaps will generate a huge manual overhead.

Hopefully, your approach will work in the cloud!

Thank you in advance,


Hi, we are facing the same issue. @Garth Hume any chance you could share your solution please?

same issue here

Vedant Kulkarni
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Sep 13, 2023

issue still persists in September 2023. Estimate hours are written in the Time Remaining field instead of the Original estimate

Like Benjamin Grab likes this

Hi, we used a Jira automation to do this.  We created a custom field called SWAG which will set the Original estimate and override the Time Remaining if Time Remaining is blank.  We do this using Jira automations.  the SWAG field can be used in Advanced Roadmaps.  It's slightly clunky, because you have to apply changes so the automation can fire.  It works OK as you are likely not estimating your size and planning your timeline at exactly the same time.  It's basically just a workaround for a poorly designed function in Jira.

Benjamin Grab
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Sep 14, 2023

Hi, is there any time estimate for this option? It was requested in 2020 and after 3 years it's still not possible to use this useful field.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events