<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=367535) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=367535) </details> <!--IssueSummary end--> Related to https://gitlab.com/gitlab-org/gitlab/-/issues/365166 We added a new field to [Bulk Imports API](https://docs.gitlab.com/ee/api/bulk_imports.html) `destination_slug` to be used in favour of `destination_name`. However, on the database level, the column is still called `destination_name`. We should rename it on the database level for consistency. In the related issue, @carlad-gl suggested an implementation plan: * [ ] add a `destination_slug` column to the `bulk_import_entities` table on the database * [ ] populate each row's `destination_slug` with the data from the `destination_name` column * [ ] change any occurrence of `destination_slug` in the bulk_importer and api to `destination_path`, for both Groups and Projects * [ ] delete the `destination_name` column * [ ] update the api documentation (both REST and GraphQL) * [ ] update the UI (see https://gitlab.com/gitlab-org/gitlab/-/issues/347510) to clarify that the input field is for a `slug` not a `name`