Track changes of the roadmap

Noting this feature needs to enable users to easily track a change to any field based on a particular time interval (e.g. changes in release assignments in the past X months) and allow for an optional comment section as to why that can be reported on as others have noted. If it is limited to changes in only certain fields, then the value of it is greatly diminished.

It is fantastic to see that this feature is now in development. Would be great to have the ability to create multiple baselines to compare your current roadmap to.

This feature is in development now! We do not have specific timing for launch yet but we will share more after the new year.

Do you have any idea on timeline for implementation?

This also gets my vote.

The Retrospective screen is a partial solution to this. Being able to report against the Histroy of Features etc might be another way.

I cannot underestimate how much of a game changer this would be for me! I'd like this to include the ability to track who/when changes were made but also to include the ability to add a narrative element. Handling this using a custom field at the moment and it is messy

Being able to report on the fact that something changed is great, but the next question is why did it change. There needs to be some sort of way to add additional information about the change as well.

We have to download a snapshot of every product (we have 15) roadmap every quarter, save it, then report on what changed the following quarter (for our exec team). I can think of 786 things I'd rather be doing! I think this would, for me, be the one thing that would save me the most time as a Head of Product.

My stakeholders expect transparency on what we deliver vs what we said we'd deliver. My current roadmap updates in real-time so stakeholders don't know what the changes are only that the current deliverable date. This would help me track and communicate those chagnes.

This would be incredibly helpful when doing quarterly planning and progress reporting.

Tracking changes made to release phases is also missing.

This is perhaps the most important feature sought after by the top management, as there are lot of changes that happen in Agile projects. To be able to track them will put development teams in a comfortable position and gain management confidence on when and why the changes were done.

It would be great to have this feature developed in Aha! asap, please.

WHY is an important part of "..who made the change and when". Please consider that when analysing the the problems being solved by providing tracking of roadmap changes.

This would be very beneficial. Tracking version control is now table steaks in many cloud services including google suite. For senior leaders it is a benefit to quickly see what has changed recently from our teams... (ie. Meeting with SVP, did any key dates slip... or key initiatives get added or removed). Unless they are glaring obvious, I have to then ask all my employees which creates preventable context switching.

This would be great if we could highlight which features had a specific field change over a specific period of time (i.e. the release changed from Q3 to Q4 in the past quarter)

Any indication if this Idea will be progressed. It would really help portfolio reporting.

This is critical for our teams in tracking on-time-delivery. We currently have to do it manually with custom fields which is a clunky user experience. 

Very important! Version control should be implemented as it is a key for auditing and not only, we should be able to see on what requirements there was a sign-off from the business, what was approved in regards to budget etc.

This would be very valuable to track changes to release dates and stimulate internal process reviews. We've created a custom date field to capture a baseline date and will then use the calculated reporting fields to assess drift

This is very critical for us, and can't believe it's been sitting in the Big Ideas for almost 4 years. When selling the use of Aha! to the business (we are new in our journey) this has come up time and time again as a basic requirement. Roadmaps change on a semi-regular basis, if you can't baseline against how it was at the beginning of the year then you lose so much value. Taking a manual snapshot at various points is not an acceptable alternative.

I find it staggering that almost all users of Aha! haven't had a need for this requirement.