Add take ownership feature to refactor
What does this MR do and why?
We are in the process of refactoring the pipeline schedules feature to use Vue/GraphQL. This MR is part of a larger effort that can be seen below. In this MR I'm adding the take ownership of a pipeline schedule feature and making the old modal legacy.
Task/issue | MR |
---|---|
Create feature flag / lay groundwork - #371986 (closed) | !99155 (merged) |
Build table component - #371990 (closed) | !99293 (merged) |
Loading state / query error handling - #376169 (closed) | !100209 (merged) |
Build tabs component - #371989 (closed) | !100749 (merged) |
Hook up mutations - #375787 (closed) | !100735 (merged) |
Take ownership - #375797 (closed) |
|
Build form component - #371987 (closed) | TBD |
Screenshots or screen recordings
flag off | flag on |
---|---|
![]() |
![]() |
How to set up and validate locally
- Enable the feature flag
Feature.enable(:pipeline_schedules_vue)
- Visit
CI/CD > Schedules
- Create test schedule with one maintainer
- Create test schedule with a different maintainer
- Impersonate one of those users and try to take over ownership through the table
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #375797 (closed)
Edited by Payton Burdette