Migrate "Purchase storage" button in alert

changed milestone to %15.1

added devopsfulfillment groupsubscription management maintenancerefactor pajamasintegrate priority4 sectionfulfillment severity4 typemaintenance workflowproduction labels

assigned to @mvanremmerden

Suggested Reviewers (beta)

The individuals below may be good candidates to participate in the review based on various factors.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Suggested Reviewers
`@stanhu`, `@engwan`, `@gitlab-bot`, `@allison.browne`, `@a_akgun`

If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".

	1 Warning
	You've made some app changes, but didn't add any tests. That's OK as long as you're refactoring existing code, but please consider adding any of the maintenancepipelines, maintenanceworkflow, documentation, QA labels.

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	Roy Zwambag (`@rzwambag`) (UTC+2)	Thong Kuah (`@tkuah`) (UTC+12)
frontend	Coung Ngo (`@cngo`) (UTC+1)	Simon Knox (`@psimyn`) (UTC+10)

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.

Generated by Danger

@arfedoro Would you mind reviewing this tiny migration?

requested review from @arfedoro

Allure report

allure-report-publisher generated test report!

review-qa-blocking: test report for d3a8a961

expand test summary

+-------------------------------------------------------------------+
|                          suites summary                           |
+----------------------+--------+--------+---------+-------+--------+
|                      | passed | failed | skipped | flaky | result |
+----------------------+--------+--------+---------+-------+--------+
| Create               | 23     | 0      | 2       | 23    | ❗     |
| Manage               | 36     | 0      | 2       | 38    | ❗     |
| Plan                 | 41     | 0      | 1       | 41    | ❗     |
| Verify               | 12     | 0      | 1       | 12    | ❗     |
| Protect              | 2      | 0      | 0       | 2     | ❗     |
| Package              | 0      | 0      | 1       | 0     | ➖     |
| Configure            | 0      | 0      | 1       | 0     | ➖     |
| Version sanity check | 0      | 0      | 1       | 0     | ➖     |
+----------------------+--------+--------+---------+-------+--------+
| Total                | 114    | 0      | 9       | 116   | ❗     |
+----------------------+--------+--------+---------+-------+--------+

approved this merge request

@arfedoro, thanks for approving this merge request.

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

For more info, please refer to the following links:

requested review from @psimyn and removed review request for @arfedoro

resolved all threads

merged

@psimyn, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline 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.

(Improve this message?)