RELATED IDEAS
Aha should delete the integration link when receiving a delete trigger from a webhook
We have Aha linked to JIRA. When we delete an issue in JIRA, this triggers our Webhook to send a message to Aha. I understand and agree that this should not cause Aha to delete the Feature connected to it for security reasons. But I would expect Aha to remove the integration link which connects the Feature to a Story in JIRA.
Because this doesn't happen currently, any subsequent updates to the Feature in Aha will result in errors while it's trying to update a JIRA issue which doesnt exist anymore. Even clicking the "Update JIRA" option manually will result in an error which is only resolved by manually deleting the integration link.
© 2024 Aha! Labs Inc.•All rights reserved
Regularly cleaning up records that are not present across 50+ product workspaces is not fun. Please implement this.
Same issue here, but with reference to an integration with Azure devOps instead of JIRA. It's frustrating to see features that appear complete but still have open items showing in Aha due to de-linked requirements that must then be manually removed in Aha.
Agree as well, and agree on the other side as well if you have an object in Aha and you push the information to Jira (including the Aha URL) when deleting the Aha integration should send null or delete the content of the Aha Web URL in Jira
We are using Aha roadmapping and communication and Jira for all our workflow. Aha not supporting the delete webhook causes distrust of the Aha data. If a delete action in Jira cannot then also be performed in Aha, having the integration link deleted would be a good solution for us to periodically perform a bulk deletion based on this search criteria.
(I meant sent TO Jira)
I like to keep the backlog in Jira small and so if a task that I've sent from Jira doesn't get done, it would be useful to be able to simply delete it and have the integration link removed (rather than having to do this manually, or not do it and end up with lots of broken links)
We have a similar issue in the case where an Epic with a link to JIRA, has the link deleted in Aha, and the link is removed on the Aha side, but the Aha Reference still appears in JIRA. This results in orphaned Epics on the JIRA side whose updates don't sync back to Aha.
Yes, I agree. Delete the integration link and set the Corresponding Aha! Reference in Jira to null