Very similar use case as Evan Hollohan - we want to power our most important source of truth marketing launch calendar report with Aha data, and a key part of that report is knowing if an end date has changed from last week. I do see some functionality of reporting on if Feature Status has changed - would love to have it here for end date. For now, we have to export to a GSheet and adjust manually.
We would like to use this for variance reporting (actual end date - original end date) on initiatives. Right now this is a manual process. This is prone to error and sometimes skipped/overwritten.
We're essentially looking to gain visibility on when start/due dates change for epics and features to understand if we're tracking according to plan or potentially getting delayed. As of now, unless it is brought up among the team, we don't have a way of seeing if epics/features are delayed from the original planned dates.
Our use case is that we would like to be able to run a report week over week on any changes to the end date field. Without this ability, we have to ask teams reach out directly every time a date changes on the 90ish features that we are currently tracking for our program. It would also be helpful to have this data compiled in one report vs receiving individual messages and manually compiling data.
Very similar use case as Evan Hollohan - we want to power our most important source of truth marketing launch calendar report with Aha data, and a key part of that report is knowing if an end date has changed from last week. I do see some functionality of reporting on if Feature Status has changed - would love to have it here for end date. For now, we have to export to a GSheet and adjust manually.
We would like to use this for variance reporting (actual end date - original end date) on initiatives. Right now this is a manual process. This is prone to error and sometimes skipped/overwritten.
We're essentially looking to gain visibility on when start/due dates change for epics and features to understand if we're tracking according to plan or potentially getting delayed. As of now, unless it is brought up among the team, we don't have a way of seeing if epics/features are delayed from the original planned dates.
Our use case is that we would like to be able to run a report week over week on any changes to the end date field. Without this ability, we have to ask teams reach out directly every time a date changes on the 90ish features that we are currently tracking for our program. It would also be helpful to have this data compiled in one report vs receiving individual messages and manually compiling data.
Just to clarify, I submitted this idea on behalf of my team for the Data Center Transformation (DCT) Program.
To be able to report and track change history of existing date fields would be a very valuable tool for change control.