Flag a broken JIRA integration to the Aha! admin so it can be resolved

What is the challenge?

As an Aha! admin, I want to ensure the JIRA to Aha! integration flags errors to me proactively (via email would be great), so that errors in the integration setup can be immediately addressed.

What is the impact?

As an Aha! admin, I often am unaware when a workspace JIRA integration breaks, leading to the sync back not working and artifacts from JIRA unable to be discovered by Aha!. This causes frustration for the product managers who own the Aha! workspace, and leads to reactive vs proactive work by the Aha! admin.

Describe your idea

Our Aha! JIRA integrations have a lot of complex mapping (statuses, fields etc), so if anything changes on the JIRA site, for instance if someone adds or removes a field in the JIRA schema that is mapped and needed by Aha!, the integration will break. Additionally, if someone adds a new status in JIRA, for the integration to work seamlessly, this new status would need to be mapped in Aha! to the appropriate Aha! status. Basically I'd like the Aha! admin to be notified via email whenever any new status or field is recognized in the integration, or whenever there is a broken linked field required for the integration, so that it can be immediately and proactively resolved. Even better than that, would be a way for the integration to be more self-healing, where it can continue to work around the change until the change is resolved.

This is a blocker for wider Aha! adoption across our product management team, because unintentional changes in JIRA often breaks the integration with Aha!, creating friction for product managers within Aha!.