For anyone coming here looking for a way to do updates to Epics when an Epic Link is changed on a ticket, you can start with this guidance: https://codebarrel.atlassian.net/browse/AUT-1264?focusedCommentId=107261

Basically, you have to use Issue Updated (or Multiple Issue Events) as the trigger, and then look at the special changelog smart value to see if it was an Epic Link change.

Some how-to: https://community.atlassian.com/t5/Jira-Software-questions/Jira-Automation-How-to-identify-what-Epic-a-Story-was-linked-to/qaq-p/1924599

When will it be fixed?

Thanks for the workaround idea @Konrad Garus.

@tom.shoval here's a quick Groovy script I've put together that can be built on to use as a custom script listener. Use the IssueLinkCreatedEvent. Note that the link type ID may need tweaking if your 'Epic-Story Link' link type isn't at ID 10500.

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.IssueManager

// Get data for this issue link
//
// 4 properties are available here:
// - issueLink.id = the unique ID of this link
// - issueLink.issueLinkType.id = ID of the link type
// - issueLink.destinationId = ID of issue being added to epic
// - issueLink.sourceId = ID of epic being added to
def issueLink = event.getIssueLink()

// Quit now if this isn't an 'Epic-Story Link' link type (ID 10500)
if ( issueLink.issueLinkType.id != 10500 ) {
  log.error("Not an epic link")
  return
}

// Get full issue data
def manager = ComponentAccessor.getComponent(IssueManager)
def issue = manager.getIssueObject(issueLink.destinationId)
def epic = manager.getIssueObject(issueLink.sourceId)

// You can then use eg. issue.key, issue.summary, epic.key, etc.

From here you could then do something like send alerts to Slack as described here: https://library.adaptavist.com/entity/send-custom-notification-to-slack

Hi,

Can anyone share an implementation example / print screen of the workaround using the webhooks? not sure i understand how i can achieve it using this...

"As kind of a workaround, it does fire IssueLinkCreatedEvent and IssueLinkDeletedEvent with hidden link type named "Epic-Story Link"."

Thanks!!

Tom

Would be great to see a fix! We use Jira project automation and have some teams that put programs in a single Jira project and manage them with team epics. We need to fire off automation rules when something is switched from team to team. (such as move all the sub-tasks as well)

As kind of a workaround, it does fire IssueLinkCreatedEvent and IssueLinkDeletedEvent with hidden link type named "Epic-Story Link".

Fix please

Any news on this problem please?

 Any fix to this problem?

We are Atlassian Partners in the middle a very large implementation at some customer (5,000 user tier data center), and we hit this bug that disrupts our customization. We need a fix.

+1 for fixing this and another +1 for doing it sooner than "some day". I would understand this being on the long-term backlog if there were issues with hundreds or thousands of votes ahead of it (the described reason for this being pushed down), but looking at the link provided above that is definitely not the case. This issue is a bug in foundational functionality, which means that anything downstream (like notifications, integrations and third-party plugins, etc.) are blocked from doing what they are otherwise supposed to do because of this.

This fix is deployed in Cloud already, which means you've figured it out to at least some extent. Please either change the reason for the delay or move it up in priority.

this is a bug and a lack in the product, it should be fixed quickly. 

event are triggered for all others fields and not this one? why?

we all wait since 23/Jul/2015 5:20 PM, more than 3 years from now... 

Is there any update on this bug ? 

any news or updates please guys ? 

its a bit annoying for few of my customers... 

 Any updates on it? 

This bug was reported in July 2015 and it is going to be almost  3 years  now without any resolution at all. Can this be at least assigned to someone? This issue has been resolved in JIRA's cloud version it seems, then why can't Jira push the fix to the enterprise version? Please provide update on this issue asap since this is causing extra overhead work for us.

is anybody there to update this task about what is going on? Just a quick update would be appreciated. All we need to know whether it will be fixed in any  upcoming versions or it wont be fixed soon enough.

any new updates

Stil relevant in v7.9.0 

Any update on this?

This issue is still relevant on v7.5.2. I spent some time tracking this one down .

is there a workaround for this issue ? when this will be fixed ?

This is an issue every day.  This really hurts and causes miscommunication.

Please fix it!

+1 on this issue, we need this fixed, it also affects v7.1.10.

Please reopen this issue as it is still an issue.

Please do not close this issue without fixing it. There are many times I need to take action on an item when the Epic link (and other links) change. To not have an event fire impedes my ability to efficiently do my job.

Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.

Kind regards,
Dong Hoang
JIRA Software