Add to the integration report if the "Based on Template" flag is checked or on the mappings page
We currently have over 200 active integrations. Knowing which ones are using the "Based on Template" flag is really useful when planning changes to the integration and ensuring that mappings are kept consistent amd not becoming unmanageable.
Guest
Jul 4, 2025
Our organization has over 500 integrations due to teams creating custom mappings instead of using standardized templates. As we work to consolidate and standardize these integrations, we need comprehensive reporting capabilities to analyze current configurations and refine our standard templates.
Business Challenge: Without visibility into existing integration configurations, we cannot effectively:
Analyze mapping patterns across teams
Identify valid use cases for custom configurations
Standardize integrations while preserving necessary customizations
Ensure governance and compliance with integration policies
Required Integration Report Fields:
Workspace identification: Workspace Name, Parent Product Line
Integration details: Integration Name, Integration Template, Target Project Name (ADO/Jira)
Configuration status: Template-based vs. custom mapping flag, enabled/disabled status
Audit information: Creation date, last modified date, creator, last data transfer timestamp
The last data transfer timestamp is particularly important for identifying dormant integrations. Even if an integration remains enabled with no configuration changes, the absence of data transfer activity over extended periods may indicate that the source workspace is no longer in use, making the integration a candidate for deletion and reducing system overhead.
Detailed field mappings: Each Aha field (Feature, Release, Epic, Requirements) with corresponding target system field names and sync direction (unidirectional/bidirectional)
Template compliance: All configurable template field data for comparison
Current Workaround: We previously collaborated with Engineering to obtain a similar CSV report through the support team, but this manual process is not scalable for ongoing governance needs.
Requested Solution: A self-service integration report that administrators can generate on-demand, enabling proactive integration management and standardization efforts across large organizations.
Our organization has over 500 integrations due to teams creating custom mappings instead of using standardized templates. As we work to consolidate and standardize these integrations, we need comprehensive reporting capabilities to analyze current configurations and refine our standard templates.
Business Challenge: Without visibility into existing integration configurations, we cannot effectively:
Analyze mapping patterns across teams
Identify valid use cases for custom configurations
Standardize integrations while preserving necessary customizations
Ensure governance and compliance with integration policies
Required Integration Report Fields:
Workspace identification: Workspace Name, Parent Product Line
Integration details: Integration Name, Integration Template, Target Project Name (ADO/Jira)
Configuration status: Template-based vs. custom mapping flag, enabled/disabled status
Audit information: Creation date, last modified date, creator, last data transfer timestamp
The last data transfer timestamp is particularly important for identifying dormant integrations. Even if an integration remains enabled with no configuration changes, the absence of data transfer activity over extended periods may indicate that the source workspace is no longer in use, making the integration a candidate for deletion and reducing system overhead.
Detailed field mappings: Each Aha field (Feature, Release, Epic, Requirements) with corresponding target system field names and sync direction (unidirectional/bidirectional)
Template compliance: All configurable template field data for comparison
Current Workaround: We previously collaborated with Engineering to obtain a similar CSV report through the support team, but this manual process is not scalable for ongoing governance needs.
Requested Solution: A self-service integration report that administrators can generate on-demand, enabling proactive integration management and standardization efforts across large organizations.