Skip to Main Content
Status Future consideration
Categories Jira
Created by Kathy Landon
Created on Sep 5, 2018

Honor Changing Jira Issue Types

Aha now honors additional Jira Types (other than just Stories and Features) - YAY! However, when the Jira Type is changed, it breaks the sync between the Jira item and Aha item.

Example: Support reports a "Support Defect", Dev reviews, changes it to a "Support Request" or even a "Story" if it is really more of an Enhancement request that came in. Or even an item starts as a Story and is promoted to a Feature.

Request: Please honor the changing Jira type on sync - even if this loses data from the original sync, keeping the item hooked to the Jira item is really important. I have lots of Aha 'orphans' that seem to be a result of the types changing in Jira.

  • Attach files
  • Guest
    Jan 12, 2023

    Created 5 years ago.....still a must have in 2023 :)

  • Dan Kelly
    Sep 14, 2021

    This is a MUST HAVE... for Azure DevOps too.

  • Taylor Wolf
    Mar 4, 2021


  • Kote Khutsishvili
    Oct 1, 2020

    Must have!

  • Daniel Pokrývka
    Apr 30, 2020

    Hello to everyone - I would like to kindly ask you to consider reprioritizing this if possible into some quick-win area. Colleagues in our company using JIRA are starting to be in a bit anti-aha mood becuase we had to restrict changing issue types (they did 1.clone and 2.change to work efficiently before). Now they can not do that and you can imagine that it creates a problem that is not easy to solve with aha (now).

  • Daniel Pokrývka
    Feb 19, 2020

    Please implement this request. I have just encountered this scenario:


    1. We have added start date and end date to JIRA epics and I have adjusted to mapping of those fields to Start Date and Due Date on features in AHA on 10+ products

    2. So that I get those values existing in these fields in AHA to JIRA (update JIRA fields), I have filtered out epics done within releases covering Q4 2019 and Q1 2020 in aha and made bulk edit action "Send to JIRA"


    3. Action mentioned above cause AHA to sync to JIRA not only features, but also requirements (linked to stories, bugs and spikes). Unfortunately there were lots of edits in JIRA following the original synchronization of those items especially in 2 ways

    a) story/bug/spike deleted in JIRA => sync break
    *b) issue type changed in JIRA => sync break*

    Now I have to manually (not aware about a better way) relink 10+ times 10-15 story level requirements due to a) or b) (mostly b).

    This feature could literally save me tons of manual time invested into work that could have been done automatically by aha. 


    Please, plan this feature into developmen as soon as humanly possible :-).

  • Guest
    Jan 24, 2020

    It would be really useful to have this, in order to keep both Aha and Jira in sync.

    When I change an epic to a story (for example) in Jira, then the linked record in Aha is not changed from a Master Feature to a Feature. This leads to confusion, particularly when creating reports on Master Features.

  • Andrew Sweet
    Jul 18, 2019

    This is really important as developers regularly need to change these and the change doesn't sync back to Aha!

  • Amir Mukeri
    Feb 5, 2019

    Is there any movement on this request? Once the Features in Aha lands in Jira as Stories (for example) there may be need to change the issue-type to (say) Epic or Bug in jira.

  • Amir Mukeri
    Feb 5, 2019


    Anybody successful in resolving this issue?


  • +1

Integrations 2.0 record type changes in Jira

With the Jira integration setup, records can be synced from Aha! > Jira. If the record type of a mapped record is changed then right now the integration stops working for this record. Is there a more graceful way this could be handled? Right no...
Tom Bailey about 5 years ago in Ideas 2 Future consideration

2 Way integration of Structural Ticket Changes between Jira and Aha

Our team often needs to make structural changes to Stories, Features, and Requirements (ex: moving a story to a different requirement as our planning shifts). Currently when we make these changes in either Aha or Jira, the change is not reflected ...
Guest about 6 years ago in Jira 2 Future consideration