Explicitly sync initiatives with integrations

Allow initiatives to sync to integrations as a first class object like features, requirements and releases.

For the JIRA integration this would involve:

1. Allow the user to choose the JIRA issue type to sync initiatives with in the integration configuration. Also allow mapping of initiative status to JIRA issue status. Allow custom fields to be mapped between Aha! and JIRA custom fields separately from feature custom fields.
2. Add a "Send to JIRA" option under the Actions menu for initiatives.
3. Sync changes to the linked JIRA issues back to Aha! (i.e. update initiative name and description in Aha! if it is changed in JIRA).

  • Brian Carr
  • Jun 21 2015
  • Shipped
Release time frame 3 months
  • Feb 9, 2018

    Admin Response

    We have launched an enhanced Jira integration. This integration will allow you to explicitly sync initiatives with Jira, 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
  • Mark Petty commented
    August 11, 2015 15:32

    I have a similar requirement.

    To us Features = Epics and Requirements = Stories. That means information entered into Aha Initiatives cannot be imported into JIRA. The context included in Initiatives is lost to developers. 

    The hierarchical view is exactly what we require. 

    We would like a JIRA issue type called Initiative. In our case a Jira link between Initiative and Epic would be sufficient. 

    Rather than a required dropdown (which would be an great addition btw) the Initiative issue type could be linked to or related to the relevent Epic. Also ideally the statuses would be tracked between the Aha and JIRA – On Track, In Development etc. That way we could pop Initiatives onto a Kanban Board for all in the development team to see!

    The additional benefit of having Initiatives in JIRA is for importing into JIRA Portfolio for resource planning. 

  • Mark Petty commented
    August 11, 2015 15:36

    In short:

    Add the ability to map Initiative with JIRA Issue Type other than Epic. Then provide a link to all associated Features.

  • Paul Edge commented
    October 19, 2015 19:33

    Worth noting that JIRA Portfolio has a concept called "Initiative" that seems like it is trying to meet the same need as Aha's similarly named field. Any integration with JIRA should probably account for the scenario where JIRA Portfolio is in use https://www.atlassian.com/software/jira/portfolio/ 

  • Michal Anderson commented
    December 18, 2015 00:17

    Is there an  ETA of when this is planned for?  I believe the workaround I am using with releases isn't the most ideal way of handling things.  Since that is all I have currently that's what I'm going with but I don't want to go too far down this rabbit hole if this is going to be coming to a release soon.  Even if you can't give an exact date, timeframe of weeks or months would be helpful.  thanks!

  • Kristi Robison commented
    June 07, 2016 20:24

    I need way to link initiatives created in Jira to initiatives in Aha. Would be great to get an update on when/if this might become available.

  • Vikram Kanitkar commented
    February 13, 2017 22:45

    We want to use Features as Epics and requirements as stories. We need the initiatives to be imported into JIRA as market problems. We need to import initiatives into JIRA, but with the option of mapping them to a JIRA type other than Epic.

  • James Claridge commented
    February 23, 2017 04:49

    ETA please this is two years old

  • Michelle Markosky commented
    August 28, 2017 15:57

    Is there an updated timeline for this? It looks like it has been "Planned" for 2 years.

    With the concept of Initiatives in JIRA (introduced by JIRA Portfolio or custom built), it would be immensely helpful to map Aha Initiatives to JIRA Initiatives (or ideally, an issuetype of choice similar to how features and requirements are implemented). This is the mapping we need and currently it is being done manually, which means duplicate work and potential for misaligned systems.