Duplicated issuelink events when creating issues in epic

awieczorek · March 1, 2021, 12:33pm

When an issue is created by using button ‘Create issue in Epic’

Atlassian is sending the below 3 events with payload:

issue link created

{
  "timestamp": 1614599231629,
  "webhookEvent": "issuelink_created",
  "issueLink": {
    "id": 42566,
    "sourceIssueId": 403815,
    "destinationIssueId": 403816,
    "issueLinkType": {
      "id": 10201,
      "name": "Epic-Story Link",
      "outwardName": "is Epic of",
      "inwardName": "has Epic",
      "style": "jira_gh_epic_story",
      "isSubTaskLinkType": false,
      "isSystemLinkType": true
    },
    "systemLink": true
  }
}

issue link deleted

{
  "timestamp": 1614599231728,
  "webhookEvent": "issuelink_deleted",
  "issueLink": {
    "id": 42566,
    "sourceIssueId": 403815,
    "destinationIssueId": 403816,
    "issueLinkType": {
      "id": 10201,
      "name": "Epic-Story Link",
      "outwardName": "is Epic of",
      "inwardName": "has Epic",
      "style": "jira_gh_epic_story",
      "isSubTaskLinkType": false,
      "isSystemLinkType": true
    },
    "systemLink": true
  }
}

issue link created

{
  "timestamp": 1614599231731,
  "webhookEvent": "issuelink_created",
  "issueLink": {
    "id": 42567,
    "sourceIssueId": 403815,
    "destinationIssueId": 403816,
    "issueLinkType": {
      "id": 10201,
      "name": "Epic-Story Link",
      "outwardName": "is Epic of",
      "inwardName": "has Epic",
      "style": "jira_gh_epic_story",
      "isSubTaskLinkType": false,
      "isSystemLinkType": true
    },
    "systemLink": true
  }
}

I think there should be only one event dispatched to addon infrastructure.

BeataSzturemska · March 1, 2021, 2:00pm

Hi @awieczorek,
thanks for your report.
I was able to reproduce the issue and I agree with you that it looks like a bug. I’ve redirected it to a team that owns that feature. I will keep you updated.

BeataSzturemska · March 3, 2021, 8:11am

Hello again,

I’d like to inform you that the public ticket was created to track the bug. It was added to the long-term backlog, so I encourage you to watch it.

Have a nice day.

NikolaNedoklanov · June 9, 2022, 9:56am

Hi @BeataSzturemska ,
The linked issue suggests it is resolved by another issue which I cannot see but a customer reported to us the same problem and I managed to reproduce it today.