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

Where are estimates stored Advanced Roadmaps

Lars Morten Nygaard_6unsvl

We're using Advanced Roadmaps for our product planning using a top down estimation approach for the long term.

This means we start with adding rough estimates to the initiative, and break the estimation down into epics later in the process.

I'm trying to find these estimated, initiatives and epics, on the Jira issues, but there are no obvious place on the issue itself were these estimates are stored. Original Estimate would be the obvious one, but that seems to be the wrong idea.

Anyone that know where to on the Jira issue these estimates are stored?

/LarsM

Comments

Jenn Sherman

I created a custom field on the initiative to hold the estimate at that level. I can then display that field in the Advanced Roadmap. It seems a clunky way to handle it so I'm hoping someone else has a better idea.

Dave

@Lars Morten Nygaard The estimate field in Advanced Roadmaps is linked to the remaining estimate in a Jira issue rather than the Original Estimate field. You can find this under "Time tracking" on the issue details view.

We use Remaining Estimate so that when you plan future sprints and review progress on an issue you are looking at the work remaining / work completed. If we just used the Original Estimate field then you would constantly be planning for the original scope of work and not what is remaining.

Regards,

Dave

Anthony Dietrich

Dave, this is a flaw. though.

Roadmaps should first look at the original estimate to plan the work. The remaining estimate as the sole source of planning is like giving us a tool to use (Original Estimate in Jira issue), and then telling us not to use that tool (not even available as a selectable field in Roadmaps). This just makes no sense. At the bare minimum, make it a field we can add.

Anthony Dietrich

Looking into this further, the remaining estimate can serve as the datapoint we want. That said, it would be handy, when roadmapping pipeline projects, to be able to have original estimates be a point that can be compared to actuals.

Dave

Thanks for those updates @Anthony Dietrich ...

To provide a more concrete rationale... imagine that you start a piece of work in one sprint that is 40h long and you complete half of it by the end of the sprint. You need to finish it in the next sprint so when you're planning do you assume it's still going to take 40h or do you plan for the remaining 20h of work?

This is basis of why Advanced Roadmaps looks at the remaining estimate. However, it is possible to access the data from the "Progress (hours)" field, as shown in this example.

Screen Shot 2021-02-11 at 1.02.29 pm.png

Here you can see that the remaining estimate is shown (20h) but the progress field is showing the original estimate data.

Regards,

Dave

VINCENT DUPONT

Hello Jira

could you please allow us to display and use the following columns in Advanced Roadmap:

* original estimate

* remaining Work

* time tracking

this would be more explicit for everyone

thanks

Vincent

kris_xix7yo

I have waited for so long about this so I forget how much passed by since I migrated to clikup 😀 Good luck!

Rodolfo Romero - Adaptavist

We're still facing this issue in July 2025. We are not asking to change the behaviour of the calculation for Sprint planning. We are asking to provide the possibility of adding other system fields, like Original Estimate, to the Plan views so we can reference that information in one place.

No matter how Agile a team can be, referencing the original estimation is crucial in the ongoing process improvement. These tools are not just to be reactive, but proactive in the project planning process.

Anthony Dietrich_fh9dj1

I gave up on this and so should everyone watching this issue. Atlassian abandoned this and other "Advanced Roadmaps" functionality. Our company dropped Jira for this and many other reasons. There are far better options out there for the work planning use cases. Jira is basically only good as a kanban development board. And there's WAY cheaper options out there now. Atlassian has refused to innovate and has been left behind. Good luck to all of you still trying to use this tool for something it was clearly never intended to do (they say it is, but it's not).

Darrel Jackson

I disagree with you but respect your opinion and share your frustration.

There are absolutely use cases where Plans beats any other tool - especially when Jira is at the heart of your delivery tooling.

Not having the availability of Original Estimate is an annoyance, not a primary use case. There are many other options to get this data.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

advanced-roadmaps