Thanks for the confirmation chris53. I will close this issue as it looks like the problem has been resolved. If you are experiencing this problem again please contact support.

I have also verified using https://requestb.in/ that Jira Cloud is sending webhooks for changes to the epic link field.

It looks like this issue was fixed recently in Jira Cloud (I had verified myself that no webhook was generated many times in the past).

I am curious if the latest Jira Server has the same fix. I am not able to test that.

I tried out this issue with Aha! directly. I was able to see updated issue within Aha! after changing it in Jira. I also dragged an issue onto a different epic, and again that was synced with Aha! At first when I created a new epic I couldn't see it synced with Aha! but then was advised to go to Settings > Integration Updates > Import new records > select imports > import selected. After that the epic appeared on Aha! and any changes thereafter were properly synced. Need more information about how this bug can be verified. 

imaduro I am having trouble reproducing the bug. I tried using my own production instance along with my own server to see if the webhook will trigger when I drag an issue onto an epic. I successfully received a POST request with the webhook event: 'jira:issue_updated' along with the changelog:

{ 
 field: 'Epic Link',
 fieldtype: 'custom',
 fieldId: 'customfield_10008',
 from: null,
 fromString: null,
 to: '10144',
 toString: 'SP2-12'
}

I was wondering if you can provide more details on how you were able to reproduce a bug?

can someone give us a time frame when this will be fixed. At least a workaround temporarily would be great.

This is also affecting our Aha! <=> JIRA integration, and is resulting in unnecessary manual work and/or missing data. Please consider increasing the priority of this issue.

This causes a major headache for the Aha! <=> JIRA integration. Please consider updating sooner than later.

This is not a minor defect.  This is a very disruptive issue that causes miscommunication and manual duplication of work.

Please understand that the severity of fixing this issue is very high. Otherwise we are losing all advantages achieved by integration to manual intervention by Product Owner and Product Manager to address the issue caused

We really need this to work as well. This is causing a business impact on our project.