I noticed that when deleting a feature in Aha! that is linked to Jira, Aha! doesn't delete the linked ticket.
I disagree with your design decision, but the message from support makes it clear that you're firm in that direction.
Still, when an Aha! feature is deleted, that leaves an "orphaned" Jira ticket. Can we modify the integration so that these orphaned tickets are searchable to make it easier to find and remove them in Jira?
From your support:
Hope you're doing well!
The Aha!-JIRA integration will never delete issues or features. This is an intentional design to prohibit accidental deletes from happening. There is no plan to change this design. This is also why there is a prominent message telling the user the issue must also be deleted in JIRA.
In terms of how to identify orphaned tickets, there isn't a capability for Aha! to flag an issue as deleted. I do see value in Aha! leaving some type of bread crumb on JIRA issues before deleting them. If you feel strongly enough I recommend that you submit this idea directly to our product team here: https://big.ideas.aha.io/ Our product team values feedback from our users and they triage those requests for prioritization on the Aha! roadmap.
One suggestion we can make is to ensure a product manager adds a 'DELETING' comment to the feature before deleting it. This will send the comment to the JIRA issue and add visibility to the fact that it has been removed from Aha!. Another option is to move items to a specific parking lot/fix version before deleting them. This will queue the issues that have been marked for deletion in single place.
|Release time frame|