Skip to Main Content
Status Shipped
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.

Release time frame 3 months
  • ADMIN RESPONSE
    Dec 4, 2023

    Aha! Roadmaps now honors changes to Jira issue type.

    In order to maintain the bi-direction integration when an issue type is changed in Jira, your Jira integration settings within Aha! need to define a mapping for all of your Jira issue types. For example, you may have mappings for Feature -> User story, Feature -> Defect, and Feature -> Support escalation all defined within your Jira integration. Each of these mappings can contain different fields and behaviors, allowing you to share the most important information for each type of work.

    Note that Aha! Roadmaps does not currently support changing the Aha! record type via an integration (i.e. changing an issue from a user story to an epic in Jira will not cause the feature in Aha! to be converted to an epic). This ensures you do not lose critical information in Aha! due to changes happening in Jira. If this functionality is important to you, please share details about your use case in https://big.ideas.aha.io/ideas/A-I-15789.

  • Attach files
  • Guest
    Reply
    |
    Nov 15, 2023

    Is there any documentation for this change? I haven't seen a Release Notes about this, and I'm still having the links break when the Type is updated in Jira. Now that this is shipped, how do I actually implement this?

  • Tiffany Cartwright
    Reply
    |
    Oct 23, 2023

    This affects planning for a Product Manager when it appears that complete work is still sitting in the backlog due to updates not occurring once the type has been changed. It also affects reporting, as the % complete for epics and releases are then inaccurate due to statuses not updating to complete.

  • Guest
    Reply
    |
    Oct 23, 2023

    This is a vital part of our workflow in Jira, and for integration to work for us, we NEED this. We cannot unlink and re-link between Aha and Jira every time an issue type is changed. It is not out of the ordinary to use different types (otherwise it would not be a heavily used feature in Jira). If Aha has the field available standard, then it would seem you understand the need to identify based on issue type. I cannot understand why that field exists and why the option is available in the integration setup if it doesn't actually work (and actually breaks things). This issue has been around for years - why is it not in a higher status than Future Consideration? This is not making Aha a very "lovable" product.

  • Guest
    Reply
    |
    Oct 20, 2023

    Depending on Aha to accurately track the status of Requirements linked to Jira issuetypes that have changes is unreliable without supporting the ability to synch to the changed issuetype (that would also be mapped in the integration). I would have thought this would be thought of and implemented early on in the tool, but I see this request is many years old now. I hope you realize the importance of this need. I'd like Aha to be a source of truth across Jira & Aha. Without supporting this capability, that will not be the case.

  • Guest
    Reply
    |
    Jul 5, 2023

    I took me some time to figure out why capacity monitoring of Jira Boards in aha is totally unreliable and thus useless: Time tracked on Jira Tickets is not updated anymore in aha after the issue type changed. 😒

    Please fix this.

  • I R
    Reply
    |
    Jun 14, 2023

    Please for the love of pasta, implement this.

  • Guest
    Reply
    |
    Jan 12, 2023

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

  • Dan Kelly
    Reply
    |
    Sep 14, 2021

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

  • Taylor Wolf
    Reply
    |
    Mar 4, 2021

    MUST HAVE!

  • Kote Khutsishvili
    Reply
    |
    Oct 1, 2020

    Must have!

  • Daniel Pokrývka
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    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
    Reply
    |
    Feb 5, 2019

    Hello,

    Anybody successful in resolving this issue?

    -Amir

  • +2
13 MERGED

2 Way integration of Structural Ticket Changes between Jira and Aha

Merged
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 7 years ago in Jira 2 Shipped
19 MERGED

Integrations 2.0 record type changes in Jira

Merged
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 6 years ago in Ideas 2 Shipped