RELATED IDEAS
Aha history to include deletes
As an an admin or product operations manager, record history is important when understanding who may have done what when it seems that the outcomes/results are not supporting the processes so that we can identify who is making any updates or deletions and provide appropriate education.
Today, deletions are not recorded in an Aha record's history - and this can be one of the most important actions to be able to understand who did it so as to
know what was deleted in the event we need to recreate the item
understand who did it so as to understand why and provide the appropriate education
when using Aha to as a source of record for product features and any activities associated with a product feature's release and then any time tracking, the data is often then used to support capitalization expenditure details and other financial record needs since product departments are resources that contribute to the creation of new products and improvements, and thus, their work is appropriate for such financial/tax options.. Therefore, it is critical it is correct and history is available to understand potential discrepancies associated with any reporting to either restore or make the appropriate adjustments. Without this auditing, it is difficult to utilize Aha as the system of choice or primary source.
when using Aha! to track approvals, often these approvals are part of a broader process that again, is essential to understand if an approval were changed or deleted; as more companies utilize to support ISO and HiTrust processes, without having this auditing, it is different to utilize Aha as the system of choice or primary source of truth.
To desired outcome is providing:
the entire activity stream within the Aha! record's history which means surfacing records were deleted - whether they are commented, associated to-do's, related records, etc.
a more robust method for restoring items in the recycle bin - at least increasing the logs to 30 days vs 7 as it can often take awhile for someone to notice a deletion. 7 days, especially when around various holidays, is definitely too short. Then, if it exceeds that time frame, ability to submit a request to get the details from Aha! (similar to what is required to support HIPAA requirements- we may make individual record activity streams available in the UI, providing reporting of events in the UI for a period of 'x' months, then providing options to obtain audit log history for up to 6 years). Aha! may not be a source of record for HIPAA data, requiring and supporting this level of auditing and history is often required for various purposes, especially when working with larger customers.
