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.

  • Michal Anderson
  • Oct 23 2015
  • Shipped
Release time frame 3 months
  • Dec 14, 2017

    Admin Response

    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
  • Karen Starrett commented
    March 1, 2016 20:57

    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.

  • Sara Llanes commented
    March 25, 2016 23:50

    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.

  • Jim Sanders commented
    March 29, 2017 17:18

    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.

  • Derek Leith commented
    June 27, 2017 15:59

    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.

  • Giuseppe Salvato commented
    August 31, 2017 16:53

    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.

  • Ben Hampton commented
    December 14, 2017 21:02

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