Deleting a JIRA issue (story, epic) that is linked in AHA, should be deleted in AHA

When you have items linked from JIRA to AHA (example STORY->FEATURE, EPIC->MASTER FEATURE), the items deleted in JIRA should be deleted in AHA

  • Carlos Palminha
  • Feb 5 2020
  • Will not implement
Release time frame
  • Feb 7, 2020

    Admin Response

    We intentionally do not delete any records based on updates from integrations.

    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 send all of your records to Jira and then decide you do not want them there and delete them, this would delete them in Aha! -- which is probably not what you wanted.

  • Attach files
  • Carlos Palminha commented
    07 Feb 16:14

    That is argument is lame. If someone deleted in JIRA then we should reflect it in AHA.


    We have a feature that is syncing both systems except for some conditions.

    If you want to avoid it, at least implement the feature with an "option" to update on DELETE.

  • Thomas Jespersen commented
    16 Feb 09:34

    I agree with Carlos... this argument does not hold. We use Azure DevOps and Aha!. Some people clean up features in Azure DevOps, sometimes in Aha!. If a story or epic is deleted in one system it must reflect in the other.

    I'm just getting started with Aha!, and for a tool that collects ideas it just plain wrong that you mark something important like this as "Will not implement". Don't take ideas so literal, find out what is the root problem. and solve that problem.


    E.g. as a minimum, you must make a feature that makes it possible to find all features & epics in Aha! that is no longer linked to Azure DevOps and allows for manual bulk delete. Or you might make a feature that disables unlinked features & epics and require reactivation to allow continued work.

    At least move it to "Future consideration" or even "Unlikely to implement" instead of turning the idea flat down :)