Quarantine saas_user_caps_spec

added Enterprise Edition QA Quality automation:ml devopsfulfillment failurenew found:staging.gitlab.com grouputilization maintenancepipelines priority2 sectionfulfillment test typemaintenance labels

assigned to @treagitlab

marked the checklist item General code guidelines check-list as completed

marked the checklist item Quarantine test check-list as completed

marked the checklist item Code review guidelines as completed

marked the checklist item Style guides as completed

marked the checklist item Follow the Quarantining Tests guide. as completed

marked the checklist item Confirm the test has a quarantine: tag with the specified quarantine type. as completed

marked the checklist item Note if the test should be quarantined for a specific environment. as completed

marked the checklist item (Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1). as completed

changed milestone to %16.0

changed the description

mentioned in issue #408958 (closed)

	2 Warnings
	The merge request title must contain at least 3 words. For more information, take a look at our Commit message guidelines.
	a0083ab5: The commit subject must contain at least 3 words. For more information, take a look at our Commit message guidelines.

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
QA	Harsha Muralidhar (`@hmuralidhar`) (UTC+10, 17 hours ahead of `@treagitlab`)	Chloe Liu (`@chloeliu`) (UTC-7, same timezone as `@treagitlab`)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. 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

approved this merge request

merged

@mlapierre, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 6 hours ago OR finished more than 2 hours ago, you should:

Ensure the merge request is not in Draft status.
Start a pipeline (especially important for Community contribution merge requests).
Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.