Skip to Main Content
Status Shipped
Categories Jira
Created by Guest
Created on Oct 23, 2015

JIRA Statuses for Features and Requirements

We have different workflows in JIRA for our Epics/Charters than we have for estimates or actual work tickets.  It would be nice if when setting up the integration we could individually map both the feature and the requirements status messages individually.

Release time frame 3 months
    Dec 14, 2017

    We have launched an enhanced Jira integration. This integration will allow you to independently map features and requirement statuses to Jira statuses, 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
  • Ben Hampton
    Dec 14, 2017

    Awesome stuff!  I just converted to a 2.0 integration and it was extremely intuitive.  Thank you!

  • Giuseppe Salvato
    Aug 31, 2017

    Same here. I was planning to build reports in Aha focused on requirements, but the lack of requirement status mapping to Jira is a show stopper. I'm now forced to use Jira for this purpose and hear people questioning Aha capabilities.

  • Derek Leith
    Jun 27, 2017

    I agree with other commenters.  Since we have different workflows in JIRA for epics and stories, the statuses in Aha are not being reflected accurately.  Clearly this causes frustration for our users and pushed them more to look exclusively in JIRA.

  • Jim Sanders
    Mar 29, 2017

    We are transitioning our JIRA projects to a new workflow that has different workflows for epics and stories.  Without allowing different epic/story workflows in Aha, we will not be able to correctly reflect the status of our initiatives.  This will greatly impact our use of Aha-JIRA.  Please change this now.

  • Sara Llanes
    Mar 25, 2016

    I second Karen's comment, we also have different workflows in JIRA for Epics and Stories so our stories' statuses are not being updated to reflect what their statuses are in JIRA. Our need for this feature is extremely urgent.

  • Guest
    Mar 1, 2016

    We also have different workflows in Jira for epics and stories. So most of our stories do not reflect the correct status in Aha which is greatly problematic when reporting to/collaborating with stakeholders!  We need this now.