Map Aha! final score to JIRA priority

We manage the product through Aha! and the priority of features with Aha! Score. Product management can be easier and more efficient with an option to inform developers about priorities directly from Aha! to JIRA (We use JIRA Standard and Agile integration.

Another related idea is JIRA to Aha! integration - when developer change priority in JIRA, it will send value to custom field in Aha! (Only 1 way, JIRA to Aha!) or map it to custom Score feature param - something like 'Developer LOE estimate'.

  • Sahar Ben-Attar
  • Jun 10 2015
  • Likely to implement
Release time frame
  • Attach files
  • Florian Leray commented
    June 18, 2015 15:54

    What they need is the priority as you are saying, that priority is the rank, not the score, isn't it?

  • Admin
    Ron Yang commented
    November 4, 2015 21:30

    Today, we have the ability to inform developers of feature priorities directly from Aha! to JIRA. This is done through the Feature Rank - you can see details through this post: http://support.aha.io/hc/en-us/articles/204755559-Send-the-Aha-feature-rank-to-JIRA

    The best way to achieve this would be to sort your cards in order (based on your Aha! score) and send this to JIRA.

    Because of this, we are unlikely to implement a specific integration point relating the Aha! score to JIRA rank, but this workaround should help with the end goal. I hope you can understand.

  • Jason Slaughter commented
    November 5, 2015 14:21

    Ron,

    The workaround proposed is not useful because while you can see that "Aha! Rank" on the issue detail pages, you can't actually do anything about it. You can't even see it from the backlog view, which is where you could manually re-arrange features within Jira.

    The fundamental problem here is that the rank of features is really important for product management priorities, and it's also really important to Jira agile, but the two ranks are completely disconnected. You need to work with Atlassian to allow a change to Jira rank via the API. The workaround proposed is a) extremely manual and time-consuming and b) a recipe for miscommunication between product management and development.

    I'm very disappointed that Aha! aren't taking this issue seriously.

  • Paige Tippett commented
    March 3, 2016 02:50

    I'm a new user to aha! and i have to agree with Jason - I am REALLY struggling with the product because ultimately it doesn't matter how I rank it in Aha! - I have to reorder it in Jira.  When I tried to change my backlog filter in Jira to use the Aha! rank - Jira was NOT happy! (I couldn't move anything around in Jira - including any defects that don't live in Aha!)

    I hate to ditch this product but it's very frustrating....

  • Josh Liberty commented
    June 13, 2017 10:16

    This would be very helpful. The current "solution" is completely useless.

  • Joe Andreana commented
    October 10, 2017 18:04

    I would strongly urge to reconsider this issue.  

     

     

    The score mapping would be ideal. I have created a custom field and map it but it is causing issues when trying to sort the priorities. 

    Allowing this mapping can be more efficient for teams to use, especially with the ability to type in the score going forward.

  • Admin
    Chris Waters commented
    October 11, 2017 22:06

    We are working now on an improvement to the JIRA integration which will allow mapping built-in Aha! fields to any field in JIRA, including custom fields.

  • Sarah Laracy commented
    October 26, 2017 20:58

    Very happy to hear about this improvement - is there any ETA at this stage?

  • Cathy Sherwin commented
    March 28, 2018 20:23

    My current solution: Added custom field in Aha for "Priority", and mapped this to Jira priority. 

    My desired solution: Remove the custom field and use Aha Score to map to Jira priority.