Map Jira's "Won't Fix" resolution status to Aha's "Won't implement" status

When the Jira workflow is set up to "Close" a ticket with the resolution status of "won't fix," there currently is now way to map that against the Aha workflow. 


It would be great to also access the Resolution status from Jira to handle this case.

  • Guest
  • Nov 15 2015
  • Likely to implement
Release time frame
  • Attach files
  • Alfred commented
    June 22, 2016 08:13

    Agreed.  It would be great to also access the Resolution from Jira.

  • Claudia Rudolph commented
    February 15, 2017 16:22

    I also agree with this proposal to map Jira's "Won't Fix" to Ana's "Won't implement".

    I also agree that it would be great to also access Jira's Resolution, in Aha.  We have multiple Resolutions in Jira, and it's a real limitation to not be able to see that in Aha.


  • Naill Mclean commented
    March 24, 2017 14:02

    Some of our users get confused because the case shows as ready to ship but in fact we didn't do it.

  • Guest commented
    February 06, 2018 01:07

    Can we include the webhook to a transition post function in jira, and Aha process the json response?

    On resolve screen most probably.

  • Josh Costella commented
    September 13, 2018 18:11

    It needs to be higher level than this. We have to be able to map to the resolution field otherwise how can you complete a ticket in Aha and have it reflected in JIRA when a resolution has to be set upon closing.