Deprecate issues GraphQL mutations
We implemented a couple of mutations that updates single fields like:
SetDueDate
SetConfidential
Now we have a new mutation for issues called IssueUpdate
that can accept multiple parameters so
we should merge due_date
and confidential
arguments into it and deprecate the old ones.
Problem
Until now there is no way to add deprecation_reason
to GraphQL mutation arguments.
Looks like it is a work in progress on https://github.com/graphql/graphql-spec/pull/525.
We can either wait until it is implemented or do our own.
Tasks
We can break this into tasks:
-
Move confidential
,due_date
,title
anddescription
toUpdateIssue
- Done on !25268 (merged) -
Deprecate SetDueDate
andSetConfidential
mutations
Edited by 🤖 GitLab Bot 🤖