Aha! integration with DevOps Plan (bidirectional)

Aha! is a comprehensive product management software that empowers teams to build and market products customers want, by providing robust tools for strategic planning, roadmapping, and collaboration. The integration between Aha! and DevOps Plan is designed to streamline the management of the records. The bidirectional synchronization ensures that the items (defined in the mapping configuration) created in Aha! are automatically reflected in DevOps Plan and vice versa, enhancing visibility and coordination across platforms.

In DevOps Plan 3.0.4 release, this integration is supported only for Agile and FullSafe business flows.

To perform a bidirectional Aha! integration with DevOps Plan:

  1. You need to enable the Mapping package for the integration to work in existing applications. For new Agile or FullSafe applications, it is enabled by default. For existing applications, you must set up a group called MappingConfigAdmins. Only users in this group can create the Mapping configuration.
  2. In the DevOps Plan application, configure the record mappings. This mapping is essential because it establishes the connection between Aha! and DevOps Plan, ensuring that the two systems can communicate and synchronize data effectively. For more details, see the Configuration in DevOps Plan topic.
  3. In the Aha! application, configure the webhook URL and then, create a record. Subsequently, review the log messages for any errors. If you find errors, resolve them. Ensure that the error resolution process includes checking for common issues such as incorrect field mappings, authentication failures, or network connectivity problems. For more details, see the Configuration in Aha! topic.

Thereafter, navigate to the DevOps Plan application. Utilize the query functionality to verify that the created records are created or listed. Confirm that the synchronization process has successfully transferred all relevant data attributes, including status, priority, and assignee information. Additionally, validate that the timestamps and unique identifiers match between the Aha! application and the DevOps Plan application to ensure data integrity.