Update work item developer documentation
What does this MR do and why?
Updates the work items developer documentation to reflect the current architecture and implementation.
Key changes:
- Replaces outdated content - Removes legacy database migration approach and replaces with current code-based type definitions
- Clarifies custom type scoping - Documents that custom types are scoped to organizations (Self-Managed) or root groups (SaaS) with explanation of the interim solution
- Enhances architecture context - Expands Cells initiative rationale with specific technical reasons (ID consistency, mixed table problems, organization migration)
- Improves Provider documentation - Adds namespace context explanation showing how types are resolved differently for Self-Managed vs SaaS
- Removes deprecated sections - Removes BaseTypeImporter section and legacy database migration examples
- Clarifies custom type patterns - Documents two ways to create custom types (brand new vs converted)
Why:
The documentation contained outdated information about database-backed types and migration strategies that no longer reflect the current implementation where system-defined types are code-based and all configuration (widgets, hierarchy restrictions) is defined in type modules.
References
Update work items dev docs to reflect changes o... (#571384 - closed)
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
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.
Edited by Marc Saleiko