RELATED IDEAS
Need the ability to pull Logs within our Aha instance via API
We would like the ability to pull audit logs via API within our Aha instance. Currently this is a manual process where someone needs to extract the information via excel or contact Aha support. We want to extract audit on every transaction done in our Aha instance via automation (hence via API). Since this is data we're putting in our environment, we would like an automated way to extract this data as well. Some examples of useful log data are: who disabled a specific user, when a specific product/idea/etc was deleted, etc. We will be using this feature extensively within our instance. Not only will it improve our transaction history but it will also reduce time and cost for Aha support
11
MERGED
Add ability to retrieve History records via REST API
We'd like to pull our History records into a reporting tool in order to review change control.
Specific Application: I need a report that can show me the Features in product <product> where field <system/custom field> was changed sinc...
7
Future consideration
12
MERGED
Ability to pull logs from AHA over an encrypted medium
Currently the only way to receive logs from AHA is via the "Activity Webhook" as part of the Account integrations. This allows me to send all product or account activity to a generic HTTP webhook via a POST command to a local listener. I am reques...
5
Future consideration
My need and vote is to be able to report against the History of Features etc By extracting this info via the REST API. Being able to do within the normal reporting UI would be even better.
It would also be useful if you make a mistake on a bulk edit and need to find the items you need to fix.
This option will be definite helpful for accountability and track changes
This should be combined with https://big.ideas.aha.io/ideas/APP-I-3384
Should these votes be combined with this Idea:
https://big.ideas.aha.io/ideas/APP-I-3668
We have two use cases for this functionality:
1. To be able to see how long work items (features, master features, releases, initaitives) have been in a given workflow status - over time we want to build a database of how long things typically take and be able to proactively identify potential issues.
2. We need to be able to do more easily complete release and initiative replans - we have a lot of cross product dependendies and nee to see how many times a date or scope changes, what the old date or scope was, and flag when dates change to ensure all dependent teams on board with new dates