I know that Atlassian has JSWCLOUD-26129 outstanding for this issue, but was wondering if anyone has a work around until Atlassian has a resolution.
Thanks
Hi @Nita Brumbaugh
The REST API endpoints only supports adding one link at a time and that is likely the cause of the limitation.
I recall other posts where this how-to article on importing links with a CSV file for Jira Data Center also works for Jira Cloud. Perhaps give it a try:
https://confluence.atlassian.com/jirakb/how-to-import-issue-links-from-a-csv-file-in-jira-740262715.html
Kind regards,Bill
Hi @Nita Brumbaugh,
In the ticket comments, you mention that you want to link multiple issues to a release. That is quite a different use case than linking issues.
Bulk change allows you to assign multiple issues to a release in one go: create a search that contains all the issues, start a bulk operation, edit the issues and fill out the desired fix version.
Since you seem to be on the premium plan, Jira Plans also contain a bulk update feature that is even more flexible. If you have your issues in a plan, select the ones that should go in the desired release and then trigger a bulk update of the release for the selected issues.
Hope this helps!
Thanks - we will try this!
It is actually linking multiple issues to a certain type of issue. The release is just a change management issue that was created and the teams want to link all the issues under that Change Management issue.
Have you ever had the same issue in automation where Atlassian won't allow more than one issue to be linked. I keep getting this error in automation:
Too many operations (2) provided for field 'issuelinks'. We support at most 1 operation for this field. (issuelinks)
Do you know if automation will be fixed with JSW-26129?
It looks like you're new here. Sign in or register to get started.
