What is the challenge? |
Our organization has strict reporting coming out of Aha! that requires records to only be connected with 1 record in downstream systems (Jira in our case). Aha! currently allows you to intentionally link multiple Aha! records to the same item in Jira. This previously was prevented years ago as Aha! did not allow multiple records to be linked. |
What is the impact? |
As we use Aha! as the source for critical financial reporting this causes errors in that report and has the potential to double count the children in Jira. Right now our finance team has to manually de-duplicate this relationship. |
Describe your idea |
Two potential approaches here. Aha! team could revert this in isolation for given accounts that request it through a feature flag. Alternatively, and more robust, would be to enable this as an administrator setting -- this would need to be account wide and not by integration. |