Seamless Sync for Epics and Features Between Aha! and ADO when changing types

What is the challenge?

Currently, when an Epic is changed to a Feature or vice versa in Azure DevOps (ADO), this change is not accurately synced with Aha!, leading to misalignment and inefficiencies.

What is the impact?

Epics and features are misaligned between AHA and ADO. Epics and features capture different information and that information is lost.

Describe your idea

Make the webhooks/integrations work better with any work item type when it changes so they remain aligned. Develop a robust synchronization mechanism between Aha! and ADO that ensures changes in item types (Epics to Features and vice versa) are accurately reflected in both systems. This includes:

Automatic detection of item type changes in ADO.
Immediate and accurate update of the corresponding item in Aha!.
Bidirectional sync to maintain consistency regardless of where the change is made.

Benefits:

Enhanced data integrity and alignment between Aha! and ADO.
Improved project tracking and management efficiency.
Reduced manual updates and potential for errors.
Streamlined workflow for product managers and development teams.

Attach files

Enter a subject

Mats Hultgren

Reply
| Jul 19, 2024

Great idea! Are "suffering" from the same problem in our Aha - ADO integration. Would also love a better way to manage "orphaned" workitems (in my case Requirements/User Stories) in ADO, that aren't connected to an Aha/ADO synched parent. Only way now is to manually walk through the Import new Records list in Integrations updates, and manually "connect" each orphan to suitable parent in ADO. I know that it's in large part an process issue, but then there's reality to consider. ;-)

0 reply Hide replies