Enhance the Audit History API to provide complete user information for both custom User-type fields and system User-type fields. For custom User-type fields, in addition to the existing raw_value (user IDs), expose the corresponding user email addresses (similar to the email_value field returned by the entity retrieval APIs). This would eliminate the need for additional user lookup API calls and keep the Audit History API consistent with the entity retrieval APIs. For system User-type fields (such as Assigned To, Created By, etc.), enhance the Audit History API to expose the underlying user identifiers and email addresses, rather than only the display names. Providing user IDs and email values would enable reliable processing of audit records, avoid ambiguities caused by duplicate display names, and offer a consistent experience across all User-type fields. These enhancements would improve API consistency, reduce integration complexity, and make audit history processing more reliable for customers integrating with Aha!.

What is the challenge?

• The Audit History API currently provides limited information for User-type fields. For custom User-type fields, it exposes only the user IDs (raw_value) without the corresponding email addresses. For system User-type fields (such as Assigned To), it returns only display names, with no user IDs or email values. As a result, integrations must perform additional API calls to resolve user information, increasing implementation complexity and making audit processing less reliable.

What is the impact?

• Customers integrating with the Audit History API must perform extra lookups to map user IDs to email addresses for custom fields and cannot reliably identify users for system User-type fields when only display names are available. This increases API usage, development effort, and the risk of ambiguities when users have identical display names.

Describe your idea.

• Enhance the Audit History API to provide complete user information for all User-type fields:

• For custom User-type fields, expose the corresponding email addresses alongside the existing raw_value (user IDs), similar to the email_value field returned by the entity retrieval APIs.

• For system User-type fields (such as Assigned To), expose the underlying user IDs and email addresses in addition to the display names.

• This would make the Audit History API consistent with the entity retrieval APIs, eliminate unnecessary lookup requests, and enable more reliable and efficient processing of audit history records.