<!--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=329639) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=329639) </details> <!--IssueSummary end--> The following discussion from !59978 should be addressed: - [ ] @kassio started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/59978#note_563625054): (+3 comments) > @georgekoltsov, I noticed now that this proposal exports all the group relations by once. From https://gitlab.com/groups/gitlab-org/-/epics/5769, I had understood that the endpoint would be something like: `groups/:id/export/:relation`, to export relations individually to accomplish the [mixed approach](https://gitlab.com/groups/gitlab-org/-/epics/5769#mixed-approach) and the ability to retry individual relation exports when needed. Exporting all the relation by once, seems unnecessary since some of the relations won't be imported by `ndjson` files. ### Proposed solution 1. Update [`project_export.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/3c27037c418a73d0d921f3ab996b543b3958f7d9/lib/api/project_export.rb#L130-138) & [`group_export.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/3c27037c418a73d0d921f3ab996b543b3958f7d9/lib/api/group_export.rb#L83-91) to accept an optional `relation` param 2. If optional relation param is passed - export only relation specified, without exporting anything else