History for Reports

We need the ability to build custom reports on Features’ change history information. This applies to other records too but Features is the top priority at this time. The inability to report on changes to Features over a given timeframe is causing major concerns for us.

• Example use case: For Tracking Level 1 and 2 (custom field) Features we need to be able to see changes to certain fields over a given period of time. For example, for Level 1 & 2 features over the last two weeks, show changes to Due date (standard field), GA target date (custom field), Risk Status (custom field), Private Preview target date (custom field) and Public Preview target date (custom field).

  • Different Leadership teams review the live Aha reports bi-weekly and monthly but can’t see what changed since the last time they reviewed it. This includes what changed, when it changed, the previous value and new value. Clicking on each feature in a long list and manually scrolling through the history tab is not a viable option for leadership.

  • Product Marketing reviews these reports bi-weekly and has a similar request but may be interested in additional data fields beyond those listed above.

• Example use case: Track changes when Features are linked or unlinked to Marketing events (aka activities like Feature records). This relationship is how we track what is planned to be showcased at a particular event. Several teams outside of product management need to be aware of these changes and not just the current state. Today Aha's record history doesn't even track links being created or removed (separate Aha big idea https://big.ideas.aha.io/ideas/A-I-18299).

Another vote for something like this. In my case, amongst other things I would like to see:

1. The number of times a feature has been 'bumped' to a later release (with dates)

2. The number of times a feature has moved back in a workflow (for example, from a failed review).

Hi, It would be very helpful to have report history.
I would like to see how many Epics do we have in each statuses from specific areas (that one is simply pivot table) but also I would like to see what change since last time (example week or month) to better control what is going on in my Portfolio.

So to know that from last time I have 1 more epic in Epic Refinement status and 5 less Epics in Collection status.

To generate that kind of the report you just simple use Pivot option but you are not able there to track the changes.

I would like to have everything in Aha because now I need to extract data manually, keep historical snapshot and transform them in Excel.

We'd love to be able to see the history of adds and changes to data in features such as when requirements (stories) are added or removed. We'd also like to have reports that show when custom fields are changed - we have a field that we tie to an important field in Jira. We'd like to have a report that shows when that field is changed in Jira or Aha and by whom.

This would be helpful for us to show progress against roadmap over time

I desperately need this functionality, especially given the gaps in the automation and approval workflow functionality. Several use cases here:

• We need to be able to pull a baseline of the first end date applied to a record (feature, release, epic, etc), which can later be compared to the actual end date to determine on-time delivery. We’d also need to analyze how many times dates are changing to measure our forecasting health.

• We need to pull history of how many times a record went off track (watch or at risk status) throughout its lifecycle to measure how well we’re managing risk.

• We need to be able to tell when certain fields were first populated, such as end date, so we can measure forecasting quality (how far in advance are we able to determine an end date).

• We need audit reports of who changed certain fields in a record to conduct a reactive review for governance purposes. There are certain strategic records that have high visibility to executives and we need proper change management for those records. We have a governance process to review and approve changes to dates and statuses for those records. Without the ability to create an approval workflow for dates or to lock down certain fields to specific contributors, being able to pull a history of any changes to those fields as an audit will avoid changes being made that didn’t go through governance.

  Ideally history could be leveraged in a list report, specific changes in history through filters in the report and also calculated columns which allow you to leverage certain values or historical change types in formulas.

Hello!

My team is experiencing issues with reports being changed by multiple "Contributors" but without a method to determine who has been making the changes, and how to restore the report to it's original form. Are there steps that we can take that would allow limited admin rights to make changes?

This would be extremely useful for auditing purposes.

the primary objective for a PM is also to show how his roadmap is advancing. But to show how the roadmap is progressing, it is necessary to demonstrate to the Management that there have been changes in priorities in the RELEASES. The objective is therefore to show in an easy way (with a new REPORT - FOLLOW UP RELEASE?) over a year, what the RELEASE is composed of (features initially planned and delivered in TIME, but also NEW features that appeared AFTER the first release declared, and features that have been DELETED (DELAYED to a new release, pushed into the parking lot, deleted)

Please add this functionality!

Our stakeholders want more visibility into how specific dates, including data entered into custom data elements, have changed overtime by feature and by release. Allowing us to pull "History" by data element into a report would be very useful.

This functionality would be extremely helpful for providing data to stakeholders.

Please add this functionality!

This would be extremely valuable for mid and post sprint reporting. We provide our prioritized list to dev before each sprint, and we want to be able to retroactively look at what our priorities were at the beginning of the sprint, how/if they changed mid-sprint, and if any high priority items were not picked up.

Love this idea - would really help flag to stakeholders the changes made to master features/releases over a period of time.

Agree with Susan Roberts about there not being a way to "lock" something - this would really help

Should include changes to report format too

The most important feature to implement!

Capturing changed report content/formatting would be key too.

This would be a huge benefit for understanding when Feature and Release dates change. Currently we are exporting a list report weekly and doing manual excel data comparisons to yield the evidence of dates shifting and the resultant impact to other work.

Our team is looking to be able to identify who last modified a record (specifically a Release but would also apply to Products and Product Lines). It would also include the date it was last modified and in a report view.