Skip to Main Content
Status Future consideration
Categories Jira
Created by David Vins
Created on Oct 31, 2018

Map JIRA Fix Version to Aha Release Phase

We would like to be able to map a JIRA fix version (and its dates) to an Aha Release phase

Why? We like to plan in Aha using a monthly program increment primarily with features, similar to SAFe. But as a continuous delivery shop using Kanban key to this is the notion that a story for a given feature, as long as it provides value, need not be held back from shipping until the rest of its counterparts are ready. Therefore, we ship on a weekly basis (and soon on-demand) and use JIRA fix versions to collect the assortment of stories, fixes, tasks, test results, that went into that release. 

However, with the current integration we end up having an Aha Release <-> JIRA Fix Version This makes it hard to plan features that are delivered over the course of a program increment. If we could map an Aha Release Phase to a JIRA Fix Version we could easily plan features at the monthly program increment (call it major release if you would) and use phases to signify the actually delivery events/milestones stories were actually shipped/delivered within.

  • Attach files
  • John OLeary
    Dec 30, 2021

    This exists in the latest Aha!, if I'm understanding your need correctly. Couldn't find any documentation for this so spent a few hours figuring it out. To do it you need to:

    1. Edit the JIRA integration and on the Mapping screen choose to add a New Record mapping: Release -> Version

    2. For Field mapping I stripped this back to just map on Names so as not to change too much data right now. Save this change.

    3. Then go to one of the other Mappings e.g. Feature -> Epic and add the below "Links to" section - from step 2 above you should now have Release <-> Fix Version available.

    To enable & synch this in Aha!

    1. Go to Releases and click on the desired release e.g. Y22.1 and click on the ellipses at the right end and choose "Edit Release Details".

    2. Go to the Integrations field in the right side pop-in and click on the + icon on the right end of it.

    3. This will load a choice of:

      1. "Send to "Your JIRA Instance" OR

      2. Link with existing record in "Your JIRA Instance"

    4. Choose b.

    5. This will load a "Link Release to JIRA" popup and you need to enter the Version Id for the Release in JIRA (go to the Releases tab in JIRA and rollover the desired release e.g. "JIRA Release Y22.1" and note the number that appears at the end of the URL in the lower left corner.

    6. Enter this value into the "Link Release to JIRA" popup "JIRA Version" field and click Find Version.

      1. This will pickup the Mapping of the Record to Version in the JIRA integration Mapping screen from above and show you options to overwrite Aha! values or JIRA values - we chose to overwrite Aha! with JIRA whilst proving this to ensure consistency as the Aha! value is only a label.

    7. Change the Release a Feature is allocated to in Aha! and Send to JIRA to see it update to the newly mapped Fix Version value. We had it set Bi-directional so this was going both ways nicely.

    Aha! Take note and update your documentation as this wasn't anywhere on there and I spent HOURS working this out today.

    John O

  • David Vins
    Jun 10, 2021

    And another.

  • David Vins
    Jun 10, 2021

    And another...

  • David Vins
    Jun 10, 2021

    And another...

  • David Vins
    Jun 1, 2020

    And another year goes by... :(

  • Josh Tambor
    Feb 14, 2020

    As it relates to this, is it possible (as a workaround) to create a Free Text Field called "Fix Version" and map to that field in JIRA? Free text fields are supported for mapping, and assuming the 'Fix/Version" field is available in Create and Edit Screens in JIRA, this may serve as a workaround.

     

    Has anyone tried this yet?

  • Kote Khutsishvili
    Apr 22, 2019

    Is there any workaround to do it?

  • Guest
    Feb 15, 2019

    This is a real problem for using Aha! effectively, not being able to bring over Fix Version , even into a Custom field like we used to do.  it makes planning impossible with the intention to move the data to Jira and vice versa