Integrations 2.0: Auto accept import records

We would like the ability to have new records created in JIRA/Rally automatically import into Aha!

Currently, they have to be accepted in Aha! prior to import. This causes an extra step in our workflow we do not wish to have to go through each time.

  • Danny Archer
  • Dec 15 2017
  • Shipped
Release time frame
  • Dec 10, 2018

    Admin Response

    We improved how our integrations work. Now when you send initiatives, releases, master features, and features to your dev system, any related child records added by engineering can be automatically imported into Aha!

    Find out how this new integration capability works.

  • Attach files
  • Max Cascone commented
    December 18, 2017 15:40

    Perhaps there could be a setting for each type of record to always import or require manual syncing. Maybe even for each field? That could get pretty unwieldy unless there are bulk operations built-in from the start.

  • Kevin Burges commented
    March 23, 2018 14:51

    I've just raised a related idea ( asking to be able to configure that no Aha! record is created at all. One option that would cover both requests would be to have a setting on the integration to configure "Automatic import", "Manual import", "Do not import".

  • Guest commented
    June 18, 2018 18:20

    If this was also enabled with the new Jira version 2 integration!

  • Guest commented
    August 16, 2018 15:34

    I'm not seeing an auto import from Jira in v2 integration - only manual. Can someone point me to the documentation for that?

  • Kirstin Maurer commented
    September 25, 2018 20:01

    This would be a great addition to really help cut down on having to manually review and approve records in the import queue, especially if a record (like a Requirement) is belongs to a Feature that is already synced between Aha! and JIRA for example.  This would be a welcome and significant time saver!

  • Stephen Morse commented
    September 25, 2018 20:58

    This would be great for 2.0 integration with AzureOps (Old VSTS),  the one ask is that we can do some configuration as to the Record Type and Integration that we want to be able to do this with.    This would really help push the Automation for our Product and Dev Teams. 

  • Hugh Casey commented
    November 14, 2018 16:14


    Saves us having to manually pull up items from VSTS on a regular basis so that we have a unified view of all ongoing work items