RELATED IDEAS
Merged idea
This idea has been merged into another idea.
To comment or vote on this idea, please visit APP-I-4755 Release and Feature Management Change Log Reports.
Release History (associated features)
Merged
Release History tracks changes in the object, as Feature History tracks changes in the feature itself. If year roadmaps it is quite common that a feature that is meant to be implemented in Release 1 passes to Release 2.
The idea is to see a history of the features that were/are part of a release throughout its history with the possibility of exporting it to a notebook.
3
MERGED
Release history should show features that were moved *out* of a release
When a feature is moved from one release to another, it shows up in the history of the moved-to release as a new feature. For tracking purposes (our documentation folks want to have an easy way to show what has changed in a release), it would be g...
0
Shipped
© 2024 Aha! Labs Inc.•All rights reserved
Hello Pablo, Anoop - look at this idea - it is supposed the solve this issue as well. What do you think? https://big.ideas.aha.io/ideas/A-I-8865
This visualization request is one of the missing information which we are finding it extremely difficult to share with the Management Board and explain the rationale for the features being moved out from originally planned to later release due to various factors such as Regulatory Enforcement, Market Demand, Low Priority Demand, etc. There is no way to generate a report that captures an aggregated log of previous and revised change. Below information is extracted from Release History View but cannot be extracted into a simple reporting or presentation purpose
Let us know if there are any recent development updates on this front.