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. 

  • Guest
  • Nov 10 2015
  • Future consideration
Release time frame
  • Attach files
  • Guest commented
    November 10, 2015 20:15

    This is totally important.  Our company needs to coordinate changes between PLMs and tries to "lightly freeze" roadmaps at the beginning of every quarter (so that our sales teams know what to expect).  During that quarter if roadmap items change for the quarter in progress, we need a way to track that and message it out to the field.  We DESPERATELY need this --- a way to track changes.  The problem is that Aha makes changes "too easy".  (a good thing) --- but with it comes its own issues.  

  • Cy Caine commented
    November 11, 2015 04:10

    This would be a big help

  • Nicolas Quesne commented
    November 30, 2015 16:09

    History already exist but we need to open feature/requirement on after the other to see if there were some changes. not very convenient.

    My need: I create a Product Requirement Document to be send to engineering. When I release a new version of document, I would like to highlight the change versus previous version.

    1) can be with a tag associated with the feature/requirement

    2) can be the full history of change with a before and after (title, description, date...)

     

    I need it.

  • Paul Edge commented
    January 20, 2016 18:27

    I just wanted to note that I've been explicitly asked for change reports by one of my clients. There is a foundation for what I think is needed (at least for my client) in the Progress burndown chart (see linked screenshot http://imgur.com/sYk7KDE), we just need a way to show what changed in more of a list type report.

    Perhaps this is possible in a pivot table now but I don't see how: there are lots of workflow status change fields in the Select Data list but nothing that tells you about a feature moving in or out of a release.

  • Guest commented
    November 16, 2016 14:14

    This is very similar to a request I just submitted so I'm glad to see this idea getting some traction! My company currently runs a very manual report by cutting a list review report on the first of each week so we can compare what features and initiatives have moved week over week. At the moment we're relying on some excel magic to highlight the differences but it would be great to have this automated. 

  • John Seifert commented
    September 13, 2017 20:42

    I have submitted versioning of a notebook to try to address this need.  This idea is more detailed.  Having this is extremely important for my company.  Internal audit want to know when roadmaps are reviewed by stakeholders, changes to the roadmap, who did the change.

  • Rex Keith commented
    28 Feb 20:40

    I agree this is an important feature. What I would like to be able to do would be to pick 2 different dates(i.e. today and 30 days ago) and have Aha generate a report of the changes for each release that occurred between those dates. Specifically I want to know...1) what new features were added to the release, 2) what features were removed from that release, 3) Did a level of effort change? If yes, by how much up or down, and 4) who made the change to each of the first 3 items and when.

  • Mark Taylor commented
    20 Mar 09:27

    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. 

  • Dave Tucker commented
    02 Apr 12:47

    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

  • Maciej Kaminski commented
    10 Jul 17:11

    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.