Add BoardEpicConnection type policy for pagination
What does this MR do and why?
Add BoardEpicConnection type policy for page results merging on Epic Swimlanes to ensure that pagination doesn't break.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch. -
The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes). -
This MR has a severity label assigned (if applicable). -
Set the milestone of the merge request to match the target backport branch version. -
This MR has been approved by a maintainer (only one approval is required). -
Ensure the e2e:test-on-omnibus-ee
job has either succeeded or been approved by a Software Engineer in Test.
Note to the merge request author and maintainer
If you have questions about the patch release process, please:
- Refer to the patch release runbook for engineers and maintainers for guidance.
- Ask questions on the
#releases
Slack channel (internal only).
Merge request reports
Activity
changed milestone to %17.5
assigned to @kushalpandya
added sectiondev label
added pipelinetier-1 label
3 Warnings 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, maintenancerefactor, maintenanceworkflow, documentation, QA labels.Backporting to older releases requires an exception request process The e2e:test-on-omnibus-ee
job needs to succeed or have approval from a Software Engineer in Test.
Read the "QA e2e:test-on-omnibus-ee" section for more details.Reviewer roulette
Category Reviewer Maintainer frontend @fernanda.toledo
(UTC-8, 3 hours behind author)
@mfluharty
(UTC+0, 5 hours ahead of 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.
QA
e2e:test-on-omnibus-ee
@kushalpandya, the
e2e:test-on-omnibus
job must complete before merging this merge request.*If there are failures on the
e2e:test-on-omnibus
pipeline, ping your team's associated Software Engineer in Test (SET) to confirm the failures are unrelated to the merge request. If there's no SET assigned, ask for assistance on the#test-platform
Slack channel.If needed, you can retry the
danger-review
job that generated this comment.Generated by
DangerEdited by ****E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-omnibus:
test report for 4694e0b4expand test summary
+---------------------------------------------------------------------+ | suites summary | +----------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +----------------+--------+--------+---------+-------+-------+--------+ | Manage | 25 | 0 | 18 | 1 | 43 | ✅ | | Data Stores | 42 | 0 | 10 | 0 | 52 | ✅ | | Plan | 66 | 0 | 4 | 0 | 70 | ✅ | | Systems | 6 | 0 | 1 | 0 | 7 | ✅ | | Create | 521 | 8 | 79 | 0 | 608 | ❌ | | Govern | 92 | 0 | 6 | 0 | 98 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Package | 20 | 7 | 12 | 0 | 39 | ❌ | | Verify | 36 | 0 | 12 | 0 | 48 | ✅ | | Analytics | 3 | 0 | 0 | 0 | 3 | ✅ | | Fulfillment | 4 | 0 | 3 | 0 | 7 | ✅ | | GitLab Metrics | 2 | 0 | 1 | 0 | 3 | ✅ | | Monitor | 10 | 0 | 9 | 0 | 19 | ✅ | | Configure | 1 | 0 | 3 | 0 | 4 | ✅ | | Ai-powered | 0 | 1 | 1 | 0 | 2 | ❌ | | Secure | 4 | 1 | 1 | 0 | 6 | ❌ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | +----------------+--------+--------+---------+-------+-------+--------+ | Total | 837 | 17 | 164 | 1 | 1018 | ❌ | +----------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-gdk:
test report for 4694e0b4expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 128 | 0 | 18 | 0 | 146 | ✅ | | Plan | 75 | 0 | 1 | 0 | 76 | ✅ | | Govern | 71 | 0 | 2 | 0 | 73 | ✅ | | Verify | 45 | 0 | 2 | 0 | 47 | ✅ | | Fulfillment | 2 | 0 | 0 | 0 | 2 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Data Stores | 33 | 0 | 1 | 0 | 34 | ✅ | | Manage | 0 | 0 | 2 | 0 | 2 | ➖ | | Package | 0 | 17 | 18 | 0 | 35 | ❌ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Secure | 2 | 2 | 0 | 0 | 4 | ❌ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 371 | 19 | 44 | 0 | 434 | ❌ | +-------------+--------+--------+---------+-------+-------+--------+
Edited by ****added pipeline:mr-approved label
added pipelinetier-3 pipeline:run-e2e-omnibus-once labels 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.
- Resolved by Kushal Pandya
@deepika.guliani
, thanks for approving this merge request.This is the first time the merge request has been approved. Please ensure the
e2e:test-on-omnibus-ee
job has succeeded. If there is a failure, a Software Engineer in Test (SET) needs to confirm the failures are unrelated to the merge request. If there's no SET assigned to this team, ask for assistance on the#test-platform
Slack channel.
removed pipeline:run-e2e-omnibus-once label
changed milestone to %17.8
added missed:17.5 label
changed milestone to %17.5
removed missed:17.5 label
added 13 commits
-
d9e8501c...fb3e7f0d - 12 commits from branch
17-5-stable-ee
- 73640060 - Add BoardEpicConnection type policy for pagination
-
d9e8501c...fb3e7f0d - 12 commits from branch
@kushalpandya similar to !177140 (comment 2287663882), the issue in
rspec-ee system pg14 8/16
appears to be related to #511235, so would likely be unrelated to this backportThe failures in
ai-gateway
show issues with code suggestions and Duo Chat responses (ex: 500 errors). While I haven't been able to trace this back to a specific issue, these should be unrelated to the functionality you are trying to backport herechanged milestone to %17.8
added missed:17.5 label
changed milestone to %17.9
added missed:17.8 label
added 3 commits
-
73640060...3ff2ff47 - 2 commits from branch
17-5-stable-ee
- 4694e0b4 - Add BoardEpicConnection type policy for pagination
-
73640060...3ff2ff47 - 2 commits from branch
changed milestone to %17.5
@nolith Can you merge this backport please? You can learn more in background of this request in https://gitlab.com/gitlab-org/release/tasks/-/issues/16158#note_2301175298.
requested review from @nolith
changed milestone to %17.9
started a merge train
mentioned in commit de126608
changed milestone to %17.5
removed missed:17.8 label
removed missed:17.5 label