Bulk issues update mutation
What does this MR do and why?
Adds a new IssuesBulkUpdate
mutation to the GraphQL API. New mutation is behind the bulk_update_issues_mutation
feature flag and also released as an alpha feature in the event we need to make some changes when frontend starts using it.
How to set up and validate locally
- On the rails console enable the feature flag
Feature.enable(:bulk_update_issues_mutation)
- Go to GraphiQL at http://localhost:3000/-/graphql-explorer and run a query like the following
mutation {
issuesBulkUpdate(
input: {ids: ["gid://gitlab/WorkItem/499", "gid://gitlab/WorkItem/498"], assigneeIds: ["gid://gitlab/User/1"]}
) {
errors
updatedIssueCount
}
}
That should update those 2 WorkItems to have the specified assignee. Work Item IDs should be from work items the current user can update, they will be ignored otherwise
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #327247 (closed)
Edited by Mario Celi