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...
over 1 year ago
Changes between two views
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.
Allow to track project history and schedule delays
over 2 years ago
Baseline for roadmap
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...
over 8 years ago
Ability to track roadmap changes
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.
10 months ago
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.
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.
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.
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.
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.
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.
This would be a big help
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.