Removing the link between an Aha Feature and a Jira Epic should clear all fields included in the sync.

What is the challenge?

When a Feature in Aha! is unlinked from its corresponding Epic in Jira, fields that were previously synced—such as the Aha! URL—remain populated in Jira. This creates a false impression that the records are still connected and actively syncing.

What is the impact?

This behavior causes confusion across cross-functional teams, particularly during audits, reviews, or ongoing delivery work. It undermines confidence in the Aha! <> Jira integration and increases the risk of teams acting on outdated or inaccurate information. From a user perspective, this feels like a bug rather than expected behavior, especially as our workflows rely on accurate integration signals.

Describe your idea

When a record is unlinked, any fields in Jira that were populated solely through the Aha! integration—especially ones like the Aha! URL—should be cleared or flagged as disconnected. This would maintain data integrity and ensure teams aren't misled by stale references. If full clearing isn't possible, a fallback option could be marking the field as "Unlinked" or providing a visible indicator that the sync has been removed.