What is the challenge? |
Currently, automatic workflow syncing between records only works with the built-in status categories. Teams that create custom status categories to better reflect their workflow stages cannot leverage automatic status syncing for those custom categories. This limits the flexibility of workflow customization and forces teams to either:
|
|---|---|
What is the impact? |
Teams need more granular workflow stages that still benefit from automatic parent-child status syncing. Without this capability, teams must choose between workflow flexibility and automatic status syncing - limiting the value of both features. Custom status categories allow teams to model their unique workflows, but the lack of automatic syncing means parent records don't stay aligned with child record progress when using these custom categories. |
Describe your idea |
Extend the automatic workflow syncing functionality to work with custom status categories in addition to the built-in categories. When a child record (Requirement, Feature) moves to a status within ANY status category (built-in or custom), the parent record's status should automatically update to the first status in the matching category name - just as it does today with built-in categories. This would give teams full control over their workflow stages while maintaining the powerful automatic syncing that keeps parent and child records aligned. |