Issue Summary

When you clone an issue with issue links in cloud, the JSON you get with the issue created event for this operation doesn't include any "issuelinks". That's because in Jira creating issues and establishing links isn't an atomic operation.  The links are created after the issue is created and then trigger their own issue link webhooks/events.

This is problematic for apps (like Automation for Jira), that want to do things like deleting all issue links after an issue has been cloned (or perhaps do something with the linked issues immediately after create). There's no way of knowing when an issue is really fully 'created' including all issuelinks etc.

Steps to Reproduce

1. Create an issue with some issue links
2. Create an Automation rule in Automation for Jira like this:
   1. Trigger: Issue created
   2. Action: Delete issue links (all of them)
3. Then go ahead and clone that issue
4. Check the rule's audit log.  The rule runs but most of the time no issue links will be deleted.  It can be a bit arbitrary and timing related, but most of the time no issues links are deleted

Expected Results

The issue JSON included in the issue created event on 'clone' should always include all issue links part of the clone.

Actual Results

The issue JSON included with the issue created webhook doesn't include any issuelinks yet.

Workaround

• It's a bit of a shitty work-around, but the only thing one can do is to re-fetch the issue JSON after the issue:created event in the hope that all links have been established. But depending on the number of links being created or timing issues, that might still not be all issue links.
• In Automation for Jira you can insert a 're-fetch issue data' action immediately after the trigger to do the above.  But as I mentioned it's not always a workaround.