Follow up from updating PM metadata defaults

What does this MR do and why?

Addresses next review comments that were moved to follow-ups:

• Use permalink
• Update feature category

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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 #424236 (closed)

changed milestone to %16.5

added Category:Software Composition Analysis Deliverable SCA:License Scanning backend devopssecure groupcomposition analysis maintenancerefactor sectionsec typemaintenance workflowrefinement labels

assigned to @brytannia

removed Deliverable label

added QA documentation labels

	1 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/settings.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

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Javiera Tapia (@jtapiab) (UTC-3, 6 hours behind @brytannia)	Sincheol (David) Kim (@dskim_gitlab) (UTC+10, 7 hours ahead of @brytannia)

Please check reviewer's status!

• Reviewer is available!
• Reviewer is unavailable!

Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

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

Generated by Danger

added 1 commit

• 4e7fd44e - Fix constant lookup

Compare with previous version

changed the description

requested review from @philipcunningham

@philipcunningham could you please review this MR?

approved this merge request

@philipcunningham, thanks for approving this merge request.

This is the first time the merge request has been approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

• rspec predictive jobs
• jest predictive jobs
• merging a merge request.

added pipeline:mr-approved label

requested review from @georgekoltsov and removed review request for @philipcunningham

approved this merge request

resolved all threads

enabled an automatic merge when the pipeline for f8a5406c succeeds

merged

mentioned in commit c29f5b63

mentioned in issue #424236 (closed)