Allow Aha! to push "feature status" and "release status" updates to Jira

The Aha! integration with Jira does many things right, what is missing for us is the ability to push Status and Release updates that are made in Aha!, to Jira.  

To us, a big selling point of Aha! was the ability to manage the higher-level pieces (releases) in Aha! while allowing the dev teams to work in Jira.  While I understand Aha! not deleting Jira issues, I do think that it is reasonable that it can change statuses.  I'd also suggest that when an issue is deleted in Aha, a comment is made in the Jira issue to denote that deletion.

  • Jeremy Naiden
  • May 21 2015
  • Shipped
Release time frame
  • Dec 14, 2017

    Admin Response

    We have launched an enhanced Jira integration. This integration will allow you to set status and release to be a 2-way sync, along with several other new capabilities including the ability to:

    • Set record mappings for Aha! initiatives, releases, master features, features, and requirements and link them to nearly any corresponding record type
    • Map default or custom fields in Aha! to any “like” field and specify which direction the updates should flow (e.g. from Aha! or from Jira)
    • Automatically send outgoing changes from Aha! or choose to review and approve them
    • Import records directly from Jira to make getting started in Aha! easy
    Check out the blog post for more details.
  • Attach files
  • Tamer Sabry commented
    August 8, 2015 08:15

    This is needed. We end out of sync between jira and Aha because of that.

  • Avigail Ehrenhaus commented
    October 22, 2015 18:41

    This is huge for us.  We have a similar process to what Jeremy explained above, and we need to be able to alert developers that a feature is ready for development.  We do this by updating status.

  • Terry Matthews commented
    June 5, 2016 21:43

    This is a massive one for me too. I started my Aha features list by importing all of my Jira user stories which naturally linked the features with stories in Jira. After doing a bit of a clean up in Aha, I now find that Aha did not reflect these updates in Jira. Now the two systems are somewhat out of sync.

  • Mark Cresswell commented
    September 13, 2016 07:38

    Often our developers will request more information from PM prior to or during development. This communication occurs in the form of an update to the status of a Jira story, which is then reflected in Aha. When the feature in Aha is updated with the requested additional information, the change in status within Aha is not reflected in Jira. This means we do not really have end to end integration between Jira and Aha for our process