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

Estimates in Advanced Roamaps doesn't update ticket estimate

Channing Childs

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?

Comments

Pete Morris

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_21xzqa

@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

Channing Childs

@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!

https://community.atlassian.com/t5/Advanced-Roadmaps-questions/Target-Dates-vs-Start-Dates-in-Advanced-Roadmaps/qaq-p/1415149

Andrea Santi

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

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-cloud

advanced-roadmaps

jira-core-cloud

estimate

field

sync