A custom board application is displaying inconsistent behavior when it comes to child items. While all child items are shown correctly when using the Schedule state in the settings, the Flow state fails to display all of them.
This discrepancy suggests a possible issue with how the application handles child item display specifically within the Flow state context.
SAAS
Known Behaviour
Flow states are designed to be project-specific, meaning their scope is limited to the individual project they are associated with. In contrast, schedule states are workspace-scoped, meaning they apply to the entire workspace, encompassing all projects within it.
This difference in scope impacts how data is accessed and displayed within each state.