Add mutation for moving an issue between swimlanes
Problem
In #218164 (closed) we plan to drag&drop issues between epic swimlanes, and user should be able to drop the issue to a specific relative position in the swimlane issue list. To set new epic and new epic issue relative position we need a mutation in GraphQL API which FE could use.
Based on discussion bellow, issues in swimlane should be ordered as on the normal issue board - by Issue's relative position (not EpicIssue relative position).
As discussed bellow (#241219 (comment 403745304)), we already have mutations for both operations:
mutation{
issueSetEpic(input: {projectPath: "h5bp/html5-boilerplate", iid: "8", epicId: "gid://gitlab/Epic/4"}) {
errors
}
issueMoveList(input: { projectPath: "h5bp/html5-boilerplate", iid: "8", boardId: "gid://Gitlab/Board/5", moveBeforeId: "80"}) {
errors
}
}
But it would be good if moving between swimlanes was an atomic transaction (so either both operations succeed or none of them).
Goal
Add a new mutations which (in transaction) 1. sets an epic issue and 2) changes issue's relative position
Or alternatively consider extending an existing mutation (issueMoveList?) with accepting also epic ID (if it's a good fit which I'm not sure).
Related discussion: #218164 (comment 399185433)