Prevent duplicate Jira links on a single Aha! record across multiple Jira integrations

What is the challenge?

Aha! allows a single record to be linked to more than one Jira issue through separate integrations, even when those integrations point to the same Jira Cloud site. This happens when a child record (Epic/Feature) is sent through one integration and its parent Domain Epic is sent along with it. If the parent is already linked through a different integration, Aha! creates a second Jira issue and a second link.

Aha! Support confirmed this is expected behavior and that no setting limits a record to one Jira link. Their recommendation is to always use the same integration for a Domain Epic and its child records. That isn't workable for us, because a Domain Epic has one owner team in one Jira space while its child Epics are worked by other teams in other Jira spaces.

What is the impact?

• Users end up with duplicate Jira issues pointing to the same Aha! record, which confuses teams and creates manual cleanup work.

• It keeps recurring, even when users take no unusual action.

• Status and data can diverge between the duplicate Jira issues, which weakens trust in Aha! as the system of record.

• Multi-team, multi-space Jira setups are common in large organizations, so other customers likely face the same issue.

• Administrators have no built-in way to find records that already have duplicate links.

Describe your idea.

Give administrators a way to prevent a record from being linked to more than one Jira issue across integrations. Any of the following would solve it:

1. Single-link setting: an account or workspace setting, "Allow only one Jira link per record," that blocks a send when the record already has a link through another integration.

2. Smarter parent handling: when a child record is sent, don't create a new issue or link for a parent that already has a Jira link in any integration.

3. Send-time warning: a confirmation message such as "This record is already linked to [Jira issue] through [integration]. Continue?"

4. Visibility: a filter or report that lists records with multiple Jira links, so admins can monitor and clean them up