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.

Need this as well for Aha <=> JIRA integration.

Same issue on our side, it makes the Aha <=> JIRA integration cumbersome and painful to use.

this makes our integration with Aha really dysfunctional 

+1 on this, our company needs this to work.

Certainly would make our process easier. Its a huge time sink for me now that this doesn't work. Would be great if you could allocate some resource to it. 

Hey guys this ticket is over three years old and it's really affecting a dependent integration

Plz send help - we are trying to use aha for Sprint/Release management and this is the key blocker.

Same issue here, hope you can take a look at it.

We're having a lot of side effects because of this issue. It'd be very much appreciated that someone take a look at it. Fingers crossed!

For my company, this bug affects a lot of our process, so would love to see it fixed!

JSW-11149 is marked "resolved" because it's a duplicate of this issue.

This issue is affecting our workflow with complimentary tools, so would love to see it fixed!

I have the same issue here. Maybe it's a regression, can you provide a solution?

JSW-11149 is marked as fixed, however I'm following the steps there and I expect the correct result but no webhook is being fired when I edit the epic link of an issue.

I see that users are still complaining about this, so I decided to comment here. This is not minor

[Additional info]
I'm running my local development JIRA instance with this command:

atlas-run-standalone --container tomcat7x --product jira --version 7.2.0-OD-04-029 --data-version 7.2.0-OD-04-029 --bundled-plugins com.atlassian.bundles:json-schema-validator-atlassian-bundle,com.atlassian.upm:atlassian-universal-plugin-manager-plugin,com.atlassian.jwt:jwt-plugin,com.atlassian.plugins:atlassian-connect-plugin,com.atlassian.webhooks:atlassian-webhooks-plugin,com.atlassian.jira.plugins.webhooks:jira-webhooks-plugin --jvmargs -Datlassian.upm.on.demand=true

This isn't a minor issue. This is hindering us from fully integrating JIRA into our corporate workflow as its web hook functionality is subpar

Hi,

We have to get this fixed, otherwise we will have to take our 100+ Jira users to another system. Please help!

Jacob

Hi,
Can you tell us when this issue will be resolved? I see it was first logged 2 years ago. But in the past two years the numbers of companies using Aha and JIRA have surely increased. We have been using JIRA over 8 years now for development and just added Aha for the product management tools.

Since using Aha with our JIRA instance we have found this issue is preventing stories from being automatically imported into Aha! The issue does not allow us to use JIRA to link stories to epics in all the standard ways and it's forcing us to do more manual work for the integration which is unacceptable.

Regards,
Karen

Hi there,

We're starting to use Aha with our JIRA instance, this issue is causing a major headache, any idea when this will be fixed?

Regards,

Simon

Hello,

Could you please inform us on when the following can be fixed or at least when could you start working on this? As far as I can see the following bug has been reported almost 2 years ago.
It is a blocker to what we are currently working on..

Regards,
Amadeusz

Hello,

This issue is preventing stories from being automatically imported into Aha! and it's forcing us to do a lot of manual work, which is unacceptable for us as it takes resources away from their real job.
You need to fix this ASAP!

Regards,
Giuseppe

Hi mark.petty,

It's still not in our short-term backlog, so we don't have an estimate yet on when we would be able to get a fix in for this.

Please do watch the issue, we'll update more once we have more information we can share on it.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

This issue is causing some issues for us. Any picture as to when this might be fixed?

Ran into this today. We wanted to have a listener setup so that on Issue Updated, if the Epic Link field value was added/changed, we'd have a bunch of other custom fields change as well. Would love to see this fixed. And it seems to be just the Epic Link field...Sprint, Epic Name, etc. all respond to the listener on change.

Indeed chris53, thanks for pointing out the duplicate

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

This looks like a duplicate of https://jira.atlassian.com/browse/GHS-11149.

However neither are fixed.

Thanks frogaczewski,

On a second read it seems like other fields work fine, so it looks like JIRA Agile is suspect here. Handing off to that bucket for further investigation.

CC: mtokar

Hey, ohernandez@atlassian.com this can be either in JIRA or JIRA Agile. Webhooks listen on issue_updated event, which might not be thrown due to some hack in epics. Or due to a bug in JIRA, someone needs to investigate this.

frogaczewski Would you know if this is a JIRA bug or a JIRA Agile bug? Thanks mate.

Cheers,
Os.