"This ticket remains open as issue linked or delinked events are still not part of a notification scheme. Right now, we do not have any plans for adding these events to notifications schemes. We will let you know as soon as the status of this suggestion changes."

You can't be serious.  The whole point of Jira is to keep peope up to date on changes to issues and you don't have this tied into Notification events?   BTW, Project Automation feature now exists for this to be tied into as well.

This issue is nearly 2 DECADES old.   Time to get it together Atlassian.

Ok, good news for everyone. I requested feature with the JMWE guys, and they deliver it.

Now, JMWE since 8.4.0 can do event based action, based on IssueLinkCreatedEvent and IssueLinkDeletedEvent. 

Hurray hurray hurray. 

Greeting from the middle of 2023, just wanna to ask, did anyone found any usable solution? Because of strict network rules, I am not able use webhooks at all and need to react to new links / deleted links. 

Got JMWE and ScriptRunner in my hands, but still struggling with working solution. 

How's it that still in the consideration? Stop those Las Vegas parties and get back to work, please!

🤣

My boy started grade 1 this year

I've been selected twice for the International Biennale of Glass art

And we've had a pandemic 

In November this issue will officially be allowed to buy me a beer in an Australian pub (and yes, I'm going to print this ticket out and have it buy me a beer at the end of the year).

In which universe is this a suggestion and not a bug?

Is anyone looking into this issue, since 2005 many things changed, Atlassian must also bring this change in JIRA. :-/

how many vote do you need?

Hi,

I wanted to use this listener for the "Create issue in epic" action.

Indeed this listener is called but twice! 

First time with

"sequence" -> null
 "destination" -> \{Long@45920} 10012
 "linktype" -> \{Long@45922} 10200
 "source" -> \{Long@45924} 10004
 "id" -> \{Long@45926} 10016

 
and second time with

"sequence" -> null
"destination" -> \{Long@45973} 10012
"linktype" -> \{Long@45922} 10200
"source" -> \{Long@45974} 10004
"id" -> \{Long@45975} 10017

Both times issue link type is the same ("jira_gh_epic_story") the only difference is the id of the link (10016, 10017).

Can someone explain me this? When looking at the table ISSUELINK, only the last one is created.

Thanks

Jakub...what kind of workflow you guys working with over there?  Here's a 13 yr old common sense feature request with tons of votes that you finally get around to, and you only partially implement it and then close it...and then reopen it with a Future Consideration status and a comment that basically says "try waiting another 13 years". 

I had to open JRASERVER-65906 because you guys closed this.  I would think that you could either close that other one as a duplicate, or more better...close this one with a resolution of "Partially Fixed"  and we'll wait 13 years for JRASERVER-65906 to be addressed.