In case anyone runs in to this again, the scriptrunner IssueLinkCreated/IssueLinkDeleted catches these events. 

To verify that its an epic link that was updated, you can check: event.issueLink.issueLinkType.name

Users in our instance have reported this as a defect, and I'm inclined to agree with their reasoning. However, given that generic issue linking doesn't trigger an event, it's not surprising that adding an issue to an epic doesn't either.

Hello Michael

I had developed a Jira plugin for our comany, which makes our Issue-tracking with Jira/Confluence smoother. One part of the plugin should update the "old" "Epick Theme" field, if the "Epic Link" field was changed. In this plugin I implemented an EventListener. If an issue is added, updated ore removed from an Epic, I expect that Jira fires an Issue-Updated event.
With the call issueEvent.getChangeLog().getRelated("ChildChangeItem") the field "Epic Link" with the old and new values should then be offered.
In Jira 6.2.6 no event is fired, so my plugin doesn't work properly.

I can't imagine, that Atlassian won't fix such a ShowStopper!

Regards,
Uli

Hello, Prior to the last upgrade of Jira, this feature definitely worked. My colleague implemented an error reporting system with this functionality in mind. He tested it several times before it broke with the update.

If you have decided to remove this functionality, that's obviously your right, but it seems odd to remove functionality might be using.

When issues get added to an epic, only the added issues are changed. We add a change item to the epic, but this does not trigger an issue update event for the epic. We don't plan on adding this in the near future.

You can use the epic report to see what has changed for the epic.

Regards,
JIRA Agile team

This may be flagged as a "minor" task but it is severely affecting JIRA functionality in our deployment, as now users who need to be informed of any and all changes pertaining to an Epic are no longer getting informed.