Creating issues with the Bulk endpoint will result in incorrect issueLinks

Issue Summary

If we have 2 issue link types with the same outward and inward descriptions, let’s say A and B, and we use the REST API Bulk create issue to create issues using the update clause to add an issue link of type B to a newly created issue, the id and name parameters are ignored and the first issue link type by alphabetical order with the same inward and backward descriptions is used instead - on this case, A is used instead of B.

This behavior was observed for versions 2 and 3 of the bulk create issues endpoint of the Jira Cloud API.

Steps to Reproduce

1. Create two issue links with the same outward and inward descriptions, let’s say ECOHELP-38295-01 and ECOHELP-38295-02 
2. Use the bulk create endpoint to create one or multiple issues with an update clause that adds an issue link, specifying in the type the id or name for issue link type B;
3. If we check the issueLinks property on the created issue by getting it through the api Get issue link types we actually see that the linked issue link is actually of type "name": "ECOHELP-38295-01" 

Expected Results

Issue should be linked to the target issue using the ECOHELP-38295-02 issue link type.

Actual Results

The issue is linked to the target issue by the first issue link type with the same description, in this case ECOHELP-38295-01. The issue link type chosen seems to be done by choosing the first issue link type in alphabetical order rather than the id or name.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available