Bulk Operations of next-gen issues does not allow you to assign a parent (Epic)

Summary

when I try to move an issue to that Epic from ‘Bulk Operations’ it lists the Epic as “unlabelled-NG-75

Steps to reproduce

1. In a next-gen project
2. Create an epic
3. via JQL Search, select some stories
4. choose Bulk Operations
5. select Epic Link
6. see the Epic names are unlabelled

Expected Behavior

the epic names are used instead

Workaround

Use multi-select on the board or the backlog to bulk assign stories to epics:

If you want to update issues that are already in "Done" status instead, you can then use the below workaround. However please keep in mind that it is using an internal endpoint not officially documented/supported and this workaround might stop working without prior notice:

Send a POST request to the REST API endpoint https://INSTANCE.atlassian.net/rest/internal/simplified/1.0/projects/PROJECT-ID/issues/EPIC-ID/children providing a list of issue-ids in the request body.

Example:

• IDs of the issues to be updated: 10405, 10203
• Project ID: 10303
• Epic ID: 10519
• Curl command to set the Epic (10519) as a parent to the desired issues (10405 ,10203). Please replace all the things in CAPITAL with the proper values:

  curl -D- -u EMAIL:API_TOKEN -H "Accept: application/json" -H "Content-Type: application/json" -d '{ "issueIds" : ["ISSUE-ID-1", "ISSUE-ID-2"] }' -X POST https://INSTANCE.atlassian.net/rest/internal/simplified/1.0/projects/PROJECT-ID/issues/EPIC-ID/children
  

In order to get the list of issue-id to update you can:

1. Run a search to get the list of issues to update
2. Switch to the list view
3. Select to display only the issue-key column and export to CSV current columns only. This way you get a CSV file that only contains issue-key and issue-id. You can parse this file in many different ways to just get a coma separated list of issue-ids surrounded by double quotes

For details on how to authenticate REST API calls using API TOKENS please refer to the API tokens documentation page.