A way to identify and address discrepancies between items in Aha! and Jira

It is quite impossible to manage the Features and Requirements integration with Jira. There seems to be multiple ways of braking the synchronization between the items in Aha! and Jira, like:

- Deleting items in Aha! do not get deleted in Jira.

- Changes to the items do not always synchronize (may depend on what fields you change or something)

- Moving the requirements from one feature to another in Aha! does not synchronize 

- and there are more ...

- Or I just forgot to hit the Update Jira button

Please provide us a way to periodically find the discrepancies between Aha! and Jira, so that we can address the discrepancies and fix them manually. Or even better if the tool could let me choose how to handle the discrepancies.

As it is currently we can not rely on the integration. We never know whether and where Jira differs form Aha!. 

We are loosing trust in the combination of Aha! and Jira. We need a set of tools we can trust.

  • Ragnar Wessman
  • Jan 5 2018
  • Unlikely to implement
Release time frame
  • Jan 5, 2018

    Admin Response

    Thank you for your idea. Our enhanced integration with Jira provides many updates which should reduce discrepancies between Aha! and Jira. For example:

    • You can now define specifically which fields sync and the direction they sync. You have full control.
    • Updates to linked records can be set to be reviewed before sending or sent automatically (they have always sent automatically, now you have the additional option of reviewing changes first)
    • If there is an error for some reason, those are captured in an integration updates section so you can decide how to resolve them. You will be alerted as well so you know there is something that needs to be addressed.

    This article provides more details on the new integration. You can also find information on converting your existing integrations here.

    We do not currently have plans on our roadmap to provide a report of discrepancies but we will continue to monitor customer feedback here. 

  • Attach files
  • Nicole Sweeney commented
    January 6, 2018 00:51

    I agree with this idea. The integration can be very valuable. Some of the buggy things make it impossible to rely on.

    Example:

    Move stories out of an epic in Jira does not remove the requirement from the feature in Aha...

    Steps to reproduce: 1. Create a feature, push to Jira. 2. Create requirements/stories, either in Jira or in Aha. All looks good. 3. Move stories from one epic to another in Jira.

    Result: Requirements stay attached to the feature in Aha.

    Expected result: Requirements are decoupled from the feature and moved to the right one!