Work item statuses - Iteration 4 (Multiple lifecycles)
## [Iteration 4: Introduce per-type sets of statuses](https://gitlab.com/groups/gitlab-org/-/epics/11975#iteration-3-introduce-per-type-sets-of-statuses) _Outcome: Users can configure statuses for each planning item type, allowing them to get the right level of granularity for each type._ ### Designs **No change in UI but may change logic for things like filters (move from 1 list of statuses to having to merge all statuses from all types in use)** * _"List items" always also includes dashboards._ * Calculations for milestone and iteration burndown: Not initially included — the burndown considers open/closed which will still exist and be tied to statuses. Currently our "started" logic is tied to assignment, we could tie this instead to moving to an "In progress" category status as that is meant to convey a sense of having started. ### Acceptance criteria #### Must haves ~"custom status::must have" * [x] Create a new lifecycle * [x] Change attributes of the lifecycle like the name * [x] Assign (system-defined) work item types to a lifecycle * [x] Ask for a mapping of statuses of the old lifecycle that don't exist in the new lifecycle to a status in the new lifecycle * [x] Add a mapping from old to new statuses or perform a migration of items from old to new statuses * [x] Delete a status in use * [x] Ask for a replacement status for the to be deleted status * [x] Add a mapping from status to replacement or perform migration of items from status to replacement #### Nice to haves ~"custom status::nice to have" * [ ] Add support for status in `gitlab-triage` gem * [ ] Improve our own automations (triage-ops) to additionally use status for workflows * [ ] Add status to the types objectives and key results * [ ] Add "Duplicate" relationship types to linked items ### Non goals 1. Manage lifecycles and status at every hierarchy level ### Additional reference * See the requirements SSOT parent epic, https://gitlab.com/groups/gitlab-org/-/epics/5099, for more information * A deep dive into UX concerns can be found in https://gitlab.com/groups/gitlab-org/-/epics/11975 * [UX video walkthrough](https://www.youtube.com/watch?v=SRM_EiW0YPM) (19:06, chapters by background, iteration plan, status categories, and initial design)
epic