Deleting a feature or requirement should delete the linked Jira issue(s)

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...

  • Guest
  • Oct 15 2014
  • Will not implement
Release time frame
  • Oct 15, 2014

    Admin Response

    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!

  • Attach files
  • Admin
    Chris Waters commented
    October 15, 2014 23:31

    Perhaps we could do something intermediate - for example popup a window in Aha! to remind you to delete the items from the integrated system?

  • Guest commented
    October 15, 2014 23:34

    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.


  • Admin
    Chris Waters commented
    October 15, 2014 23:41
    We are unlikely to add a configurable setting for auto-delete. Even for an experienced team the risk of inadvertent deletion is too high. 
  • Guest commented
    October 15, 2014 23:44

    Makes sense. I’d probably regret enabling it at least a few times if it was available ☺.


  • Brooke Huling commented
    October 07, 2015 04:15

    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?  

  • Stephen Jones commented
    November 12, 2015 16:09

    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

  • Gavin Jones commented
    June 05, 2017 16:00

    Why did idea APP-I-2641 ship that was the same thing for Rally, but for Jira its will not implement?

  • Ragnar Wessman commented
    January 05, 2018 13:57

    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. 

  • Rachel Goldberg commented
    May 22, 2018 20:31

    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.