Bug when moving issues from one epic to another

  1. Enable sync epics to a work item
  2. Create an epic
  3. Create a sub-epic within that epic
  4. Create an issue within the epic
  5. Move the issue from epic to the sub-epic.
=> Errors “Something went wrong while moving item.”
Payload:
 "epicTreeReorder": {
            "clientMutationId": null,
            "errors": [
                "#123 cannot be added: already assigned to an epic"
            ],
            "__typename": "EpicTreeReorderPayload"
        }

Reasoning: in the model we check if the issue we move already has a parent_link. We error if that’s the case/not the same epic we already have. https://gitlab.com/gitlab-org/gitlab/-/blob/e42c603b25297256b0aec1120e8c80b924b5ecb1/ee/app/models/epic_issue.rb#L61

Screen_Recording_2024-02-29_at_19.02.08

Edited Feb 29, 2024 by Nicolas Dular
Assignee Loading
Time tracking Loading