When I delete a feature or a requirement in Aha!, I then have to go to Jira and delete the corresponding epic or story. Would love it if deleting a feature in Aha! deleted the linked epic in Jira and all stories for that epic. Likewise, deleting a requirement would delete the linked story. Maybe the Jira API doesn't provide this function...
We intentionally do not delete any records from integrated systems when you delete a record in Aha!. If you really want the linked record to be deleted too you will need to do that manually in the other system.
The reason is very simple: there is too much risk of users inadvertently deleting data, especially when they are just getting started. For example, if you imported issues from JIRA, then decided you didn't want them and deleted the features again you would also delete all of your issues from JIRA - probably not what you wanted!
i concur with the users below. not implementing this functionality for integrations is like getting to the 10 yard line, then walking off the field.
if you're going to play the big game, you need to be willing to go all the way. that includes giving your users the tools to potentially shoot themselves in the foot. the decision to not support this type of thing is business-level (e.g. a fear of liability), not technical.
I get where you are coming from, but agree with the majority below - this just adds to a buildup of orphaned records in both systems, potentially impacting trust and process effectiveness.
My real problem though is with so many simple workaround to the issue, to simply say "we won't implement" seems to not be very customer-focused. There are some good ideas below, and I would add just a simple pop-up explicitly stating the ramifications and asking for a delte confirmation. I know plenty of systems where when there is a "no going back" situation, make you type DELETE in a box and it has to match case as well.
Again - I get where you are coming from but at lease for me it's coming off as "we know how you should use our product better than you do." At least meet me halfway.
I understand not deleting it out of an abundance of caution. But if a feature is deleted in JIRA, it would be helpful if it were at least flagged in Aha.
Saying that we have to manually delete the items from Jira does not solve the problem! How can I remember or keep track of everything I need to delete in Jira? No way! The current situation leads to discrepancies between the systems, and trust gets lost.
If the answer is that we don't want automatic deletion, we have to come up with another solution.
I would be OK with a tool that I could invoke periodically, that could find all the discrepancies between Aha! and Jira, so that I could fix them manually. Or even better if I could choose in the tool what to do with the discrepancy items.
Please address this problem.
Why did idea APP-I-2641 ship that was the same thing for Rally, but for Jira its will not implement?
In my case I have features in AHA with lots of requirements. I copied these and renamed then removed requirements to divide the work into the new features. But now in Jira I have the new feature with it's requirements but the old feature still with all the requirements. It's a lot of double handling prone to errors
Could you create a list of deleted items in AHA that have a JIRA link so we can at least take that list over and do the delete manually?
Makes sense. I’d probably regret enabling it at least a few times if it was available ☺.
Your rationale makes perfect sense. And, the popup idea would certainly be a useful reminder.
What about making auto-deletion a configurable setting? Once a team is experienced enough, the Administrator could turn on auto-delete.
Perhaps we could do something intermediate - for example popup a window in Aha! to remind you to delete the items from the integrated system?