<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=559001) </details> <!--IssueSummary end--> From https://gitlab.com/gitlab-org/gitlab/-/issues/556113#note_2665885308 If someone creates a new lifecycle as the first action within the context of the status feature, we need to migrate to custom statuses, too. That's necessary because the new lifecycle will be a custom one and we said a namespace can only exclusively use system-defined or custom statuses. So that action needs to walk through existing lifecycles first, make them "custom" and then add the new lifecycle. If the template was that former system-defined and now custom lifecycle, we'd need to exchange that with the custom version. So reverse look up the system-defined statuses and find the custom ones. But that should be it, no more additional actions that make a switch from system-defined to custom necessary :laughing: