-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.7.4, 7.5.0, 7.10.0, 7.2.15, 8.0.0, 7.6.14, 8.4.0, 7.13.5, 8.3.3
-
JIRA standalone (6.3.4) on Ubuntu 14.04 w/ JDK 1.8 (Oracle)
JIRA Agile (6.7.4)
JJupin (3.0.5)
-
6.07
-
6
-
Severity 2 - Major
-
78
-
Problem summary
Changes in Epic link field does not trigger listener for "Issue Updated" event. As an example, Webhook will not fire when it is configured for "Issue Updated" and the only change for the issue is on the Epic link.
Steps to Reproduce:
- Create a listener for "Issue Updated"
- Update just Epic Link field,
Actual Result:
Listener is not triggered.
Expected Result:
Listener is triggered.
Notes
This is the only field that has the problem. All other fields (standard, custom, Agile, etc.) do not exhibit this problem.
- has a derivative of
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
MNSTR-3204 You do not have permission to view this issue
-
SSE-520 You do not have permission to view this issue
[JSWSERVER-12299] Change in Epic Link field does not trigger listener
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".
Sugandha Singh
added a comment - Any fix to this problem? This bug is also affecting some of our clients. We are looking forward to this bugfix.
Dusan
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