Follow-up from "Add Container Expiration Policy & Service Desk Setting to GitLab Migration"

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

The following discussion from !75653 (merged) should be addressed:

  • @brytannia started a discussion: (+1 comment)

    question: I see that this is a repeating test case and it's logical because ServiceDeskSettingPipeline includes its behavior from NdjsonPipeline. It would be good to extract this test so we can reuse it to test similar behavior on different classes. What do you think, is it possible and does it make sense?

Edited Jul 29, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading