Add update_design permission field project level

Add update_design as field for project level userPermissions

Issue: #468426 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

1. Run the following query to see updateDesign permission field is available and not available on master.

query workspacePermissions($fullPath: ID!) {
  workspace: project(fullPath: $fullPath) {
    id
    userPermissions {
      createDesign
      readDesign
      updateDesign
    }
  }
}

assigned to @akotte

added backend devopsplan featureenhancement typefeature labels

added sectiondev label

added pipelinetier-1 label

added groupproduct planning label

changed milestone to %17.5

added documentation label

	2 Messages
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/graphql/reference/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Category	Reviewer	Maintainer
backend	@sam.figueroa (UTC+0, 5.5 hours behind author)	@pedropombeiro (UTC+2, 3.5 hours behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

@sam.figueroa Could you please do initial backend review ?

If you are happy with the changes then please forward the MR to @nicolasdular for maintainer review!

requested review from @sam.figueroa

approved this merge request

requested review from @nicolasdular and removed review request for @sam.figueroa

added pipeline:mr-approved label

added pipelinetier-2 label and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for a85efe33

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Plan        | 3      | 0      | 0       | 0     | 3     | ✅     |
| Data Stores | 1      | 0      | 0       | 0     | 1     | ✅     |
| Create      | 11     | 0      | 0       | 0     | 11    | ✅     |
| Govern      | 4      | 0      | 0       | 0     | 4     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 19     | 0      | 0       | 0     | 19    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-test-on-omnibus: test report for a85efe33

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Plan        | 9      | 0      | 0       | 0     | 9     | ✅     |
| Create      | 33     | 0      | 0       | 0     | 33    | ✅     |
| Data Stores | 3      | 0      | 0       | 0     | 3     | ✅     |
| Govern      | 12     | 0      | 0       | 0     | 12    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 57     | 0      | 0       | 0     | 57    | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

approved this merge request

resolved all threads

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label

added this merge request to the merge train at position 3

removed this merge request from the merge train because the pipeline did not succeed. Learn more.

enabled automatic add to merge train when checks pass

removed pipeline:run-e2e-omnibus-once label

started a merge train

merged

mentioned in commit 66ce5df2

mentioned in incident gitlab-org/quality/engineering-productivity/master-broken-incidents#8881 (closed)

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label