Add Iteration Cadences to Group Import/Export

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
`@kassio`, `@georgekoltsov`, `@ashmckenzie`, `@smcgivern`, `@ayufan`

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".

added backend featureaddition typefeature labels

1 Warning

featureaddition and featureenhancement merge requests normally have a documentation change. Consider adding a documentation update or confirming the documentation plan with the Technical Writer counterpart.

For more information, see:

The Handbook page on merge request types.
The definition of done documentation.

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	Mehmet Emin Inac (`@minac`) (UTC+2, 1 hour ahead of `@georgekoltsov`)	Stan Hu (`@stanhu`) (UTC-7, 8 hours behind `@georgekoltsov`)

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

Allure report

allure-report-publisher generated test report!

review-qa-blocking: test report for 92d433cc

expand test summary

+-----------------------------------------------------------------------------------------+
|                                     suites summary                                      |
+------------------------------------+--------+--------+---------+-------+-------+--------+
|                                    | passed | failed | skipped | flaky | total | result |
+------------------------------------+--------+--------+---------+-------+-------+--------+
| Plan                               | 47     | 0      | 1       | 47    | 48    | ❗     |
| Verify                             | 12     | 0      | 1       | 12    | 13    | ❗     |
| Create                             | 28     | 0      | 1       | 28    | 29    | ❗     |
| Manage                             | 46     | 0      | 3       | 39    | 49    | ❗     |
| Package                            | 0      | 0      | 1       | 0     | 1     | ➖     |
| Protect                            | 2      | 0      | 0       | 2     | 2     | ❗     |
| Configure                          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Version sanity check               | 0      | 0      | 1       | 0     | 1     | ➖     |
| Feature flag handler sanity checks | 9      | 0      | 0       | 9     | 9     | ❗     |
| Secure                             | 2      | 0      | 0       | 2     | 2     | ❗     |
+------------------------------------+--------+--------+---------+-------+-------+--------+
| Total                              | 146    | 0      | 9       | 139   | 155   | ❗     |
+------------------------------------+--------+--------+---------+-------+-------+--------+