Skip to Main Content
229 VOTE
Status Shipped
Categories Roadmaps
Created by Guest
Created on Nov 10, 2015

Track changes of the roadmap

I would like to track the changes that were done to the roadmap/specific features. I would like to see who made the change and when.

Release time frame 3 months
  • ADMIN RESPONSE
    May 1, 2024

    We are excited to share an update on this idea! A new history panel has been added to the features roadmap. The panel provides an overview of adjustments to scope and timing — making it easy to see what has changed. See the blog post for more details.

    We have now also added the history panel to all Gantt charts. We will be adding to the following roadmaps in the near future:

    • Strategic roadmap

    • Custom roadmap

    • Portfolio roadmap

  • Attach files
  • Tricia Kelly
    Reply
    |
    Jan 25, 2024

    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.

    1 reply
  • Valentina Morales
    Reply
    |
    Dec 11, 2023

    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.

  • Admin
    Austin Merritt
    Reply
    |
    Dec 1, 2023

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

    2 replies
  • Heather Boatwright
    Reply
    |
    Nov 29, 2023

    Do you have any idea on timeline for implementation?

  • George Smyth
    Reply
    |
    Oct 27, 2023

    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.

  • Sophia Papadopoulos
    Reply
    |
    Aug 3, 2023

    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

  • Kalyndra Craven
    Reply
    |
    Jul 11, 2023

    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.

  • Jason Hollis
    Reply
    |
    Jul 10, 2023

    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.

  • Gwen St. Pierre
    Reply
    |
    Jun 19, 2023

    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.

  • Sophia Papadopoulos
    Reply
    |
    Apr 18, 2023

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

  • Guest
    Reply
    |
    Jan 11, 2023

    Tracking changes made to release phases is also missing.

  • Prasad GVS
    Reply
    |
    Apr 28, 2022

    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.

  • Andy Hawkins
    Reply
    |
    Jan 14, 2021

    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.

  • Guest
    Reply
    |
    Jul 29, 2020

    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.

  • Dustin Ingram
    Reply
    |
    May 15, 2020

    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)

  • Guest
    Reply
    |
    Jan 27, 2020

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

  • Guest
    Reply
    |
    Jan 16, 2020

    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. 

  • Guest
    Reply
    |
    Jul 10, 2019

    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.

  • Dave Tucker
    Reply
    |
    Apr 2, 2019

    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

  • Mark Taylor
    Reply
    |
    Mar 20, 2019

    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. 

  • Load older comments
  • +130
2 MERGED

Allow a baseline to be set for a schedule

Merged
There is no way to recognize that a schedule has slipped in Aha. It would be beneficial to allow saving of a baseline once a schedule Gantt has been built so you can recognize slips just by looking at the Gantt. Baseline should collect start/end d...
Guest over 2 years ago in Schedules 0 Shipped
49 MERGED

Changes between two views

Merged
The Sales team would like to be able to see the clear differences between two published notebook roadmaps so that they can inform the customers about the changes in features, release dates, etc.
Guest almost 7 years ago in Presentations 0 Shipped
55 MERGED

Baseline for roadmap

Merged
It would be great to have the possibility to set a version of the roadmap, so that users that log into aha can review the latest approved roadmap. You can achieve similar result by use of notebook, but there you do not have the posibillity to cli...
Johan Lindblom about 9 years ago in Reports 0 Shipped
4 MERGED

Ability to track roadmap changes

Merged
A critical part of tracking & reporting on roadmaps, especially for management, is the ability to report on changes to roadmap. We need to be able to understand when items slip.
Guest almost 2 years ago in Features 2 Shipped