Changing "Epic link" field not firing an event

[Sugandha]

Basically I was hoping to get an "Issue update" event for an story type when the Epic link field of the story is changed to link to another epic.

But it seems that's not the case.

Has somebody faced a similar situation and come up with an alternate solution.

My requirement is when an story is linked to an "new" epic then to inherit some specific fields from the new epic onto the story. I was planning to write a script listener for the same. 

I am using JIRA server 7.2.9

[Tom Lister · Accepted solution]

Hi @Sugandha 

This article might help

https://community.atlassian.com/t5/Jira-questions/How-to-send-notification-when-Story-is-assigned-to-Epic/qaq-p/799103

[Sugandha]

@Tom Lister , thankyou for the reply.

But my requirement is little different here.

I went through documents and the atlassian community solutions and found that there is bug found. So because of which If I am updating the Epic Link, the script listener is not not listening tho this change.

On the other hand, when I am changing any other field value, the the listener is responding to it.

So I wanted to know if we get any fix for this in datacenter version 7.2.9 of JIRA.

If no, then curious to know if there is any workaround for this.

Regards,

Sugandha

[Tom Lister]

Hi @Sugandha 

I can't comment on when Atlassian will fix issues. This is a community forum not Atlassians support team.

I did just try this on my server version 7.12.3 and I got notifications of data changes but not the epic change - so not fixed yet.

[Vedant Kulkarni]

Hi @Sugandha , If you are still looking for an alternative and if you are on the older version, here are the steps that we have applied and tested on 7.10

• create a dummy field(text) and add it on the edit screen
• use behavior to copy the value of Epic Link to this dummy field. 
• hide the field from the edit screen
• hide the field from view screen using javascript placing an announcement banner or add the field only on Edit screen

This bug is already fixed in 8.5+ https://jira.atlassian.com/browse/JSWSERVER-12299.

Note that this field will be recorded in Issue history