Adds work_item_custom_status_mapping table and model
What does this MR do and why?
This is the first MR of a series that will introduce mappings from one custom status to another for given work item types. It's based on the work in this POC MR so you can see details, examples and implementation details in the description of that MR.
You can read more about the need for valid_from and valid_until columns in this thread that handles edge cases.
The MR adds the table for the new mapping model, indexes and foreign keys. Follow up MRs will contain the actual logic to resolve statuses based on this mapping.
Query pattern to access rows from this table can be found here and here in the POC. The idea is that we use request store and fetch mappings by namespace and access mappings based on an indexed hash for fast lookup.
References
- Add model and table (#566526 - closed)
- BE: Add mapping (#558275 - closed)
- Add status mapping (&18748)
Screenshots or screen recordings
backend only
How to set up and validate locally
Only migrations and model files
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.