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
  • Future consideration
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.

  • Guest commented
    08 Feb 09:35

    This comment is for the request of the 'Resolution status' from JIRA.

    We have several projects that need to have a workflow which has a Resolve Screen. With a Resolve screen, there would be  multiple conditions and validators. As part of the validators, there would be a check to see if there is a 'Resolution' field chosen from a list of options.

    We have a 2 way sync between Aha and JIRA. When we mark a feature on Aha as shipped, it needs to mark the corresponding Epic on JIRA as Done. Now, this never happens because, there is an integration update error on Aha, that says "'resolution': Could not find valid 'id' or 'name' in resolution object.". So, basically even after removing the validator on JIRA workflow for the resolve screen, this doesn't work. 

    Also, on a similar note, on JIRA, we have an IN REVIEW state, which is mapped to Ready-to-ship state on Aha. This transition also never goes through from Aha to JIRA, as there is no Reviewer field in Aha for a feature. And on the screen to move a JIRA ticket from some status to IN REVIEW, there is a validator that ensures a Reviewer is assigned for the ticket. So, again, this state transition from Aha never makes into JIRA. 

    If there is a supported integration on Aha for JIRA, it needs to support these basic functionalities.

  • Daniel Pokrývka commented
    12 Feb 10:51

    Absoutely necessary. This makes JIRA sync basically unusable as there are so many constellations of stars with JIRA resolution configuration when it does not work, that it must be an issue for most of AHA customers. I consider this more than a design flaw then new feature request. This is a comment coming from experience with aha and JIRA, no theory.

  • Emily vargas commented
    31 Jul 17:26

    My team just ran into this issue and it's completely halted our integration. We require a field at the close of a JIRA project which is what is breaking the links. We cannot un require that field because we need to report on that data and we struggle to get those fields populated without a requirement. However requiring that field breaks the integration so we're stuck. If anyone has any ideas on possible workarounds we're all ears!

  • Matt Howard commented
    20 Sep 16:33

    As our engineering team requires the Resolution field in Jira to be required when closing out an Issue, we need the ability to create a custom field in Aha! and map it to the Resolution field in Jira, so we can specify the reason why a Feature in Aha! is being set to "Will not implement". It is a good idea for us to track and report, in Aha!, the reasons why a Feature was not implemented.

  • Alex Henry commented
    16 Oct 16:20

    Definitely a big problem when it comes to Jira integration. It would be great to be able to expose the resolution status, and also add some status transition logic in Aha!. The best workaround I've found (which is quite messy indeed) is to add a new 'Won't implement' status in Jira, with a transition that sets the resolution status to 'Won't Do'.  Shouldn't make a huge difference in Jira if you adjust your board filters to ignore the 'Won't implement' status just like  the Closed status.