Skip to Main Content
120 VOTE
Status Future consideration
Categories Reports
Created by Zach Rose
Created on Jan 12, 2017

History for Reports

We use reports often to tailor Aha data for different audiences. Recently, those audiences have been looking for summaries of how the data in that specific view has changed over time. 

The changes can be pieced together manually by looking through the /audits section or manually reviewing the History of each individual Feature or Requirement in the report. We haven't found a way to make either of these practically feasible.

This idea is to bring History to reports, so that from the Report itself, there could be a way to access a History view just like the one for Releases, Features, requirements, etc; but showing all changes to the data captured in the report.

Ideally this History would be accessible to all roles, but if it needs to be limited to Product Owners and Contributors, then I'd request that it be exportable so that there's a way to share a summary of changes with stakeholders.

  • Attach files
  • Lindsay Zandy
    Jun 4, 2022

    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.

  • Guest
    Mar 31, 2022


    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?

  • Guest
    Jul 28, 2021

    This would be extremely useful for auditing purposes.

  • Catherine Dumas
    Mar 17, 2021

    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!

  • Pamela Stephens
    Nov 10, 2020

    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.

  • Janet Havens
    Aug 13, 2020

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

  • Evan Polley
    Aug 13, 2020

    Please add this functionality!

  • Guest
    May 15, 2020

    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.

  • Steve Brunt
    May 5, 2020

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

  • Guest
    Dec 17, 2019

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

  • Guest
    Oct 11, 2019

    Should include changes to report format too

  • Guest
    Jul 12, 2019

    The most important feature to implement!

  • Guest
    May 13, 2019

    Capturing changed report content/formatting would be key too.

  • Alex Moffatt
    May 8, 2019

    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.

  • Angie Easter
    Apr 24, 2019

    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.

  • Jennifer Rogers
    Apr 19, 2019

    I second this comment from Jana Decker: "Throwing my vote here- we're looking for a "last modified by" field to add to reports- what's already listed would be very helpful as well!" Thank you!

  • Jana Decker
    Apr 19, 2019

    Throwing my vote here- we're looking for a "last modified by" field to add to reports- what's already listed would be very helpful as well!

  • Matt Seitz
    Sep 27, 2018

    As a a first step, a simplified version of this could be a "blame" report.  Rather than listing all changes to each field, just list the most recent change for each field:  old value, new value, who made the change, date the change was made.  That would address most of my use cases.

  • Evan Sanders
    Aug 9, 2018

    This would be really helpful to enable things like a cumulative value flow for features.  We could show how long features are in different stages, to track the flow from market research to market value.  

  • Tammy Connell
    Aug 6, 2018

    Our company would really benefit from this feature!

  • Load older comments
  • +24