Issue Summary

There is a discrepancy between the logic used to color Feature cards on the Program Board and the logic used to populate the "Planning Issues" flyout/list.

When a story is assigned to a Sprint but has a NULL value in its own TeamID field (often occurring during Jira synchronization where only the sprint is mapped), the Program Board color logic treats the story as "not assigned to any team," which triggers the Orange status for the parent Feature.

However, the Planning Issues list uses a different validation rule that appears to respect the team inherited from the Sprint, resulting in the list showing "None" despite the card being Orange. This creates confusion for users who see a warning color with no explanation.

Steps to Reproduce

1. Create a Feature and assign it to a Program and PI.
2. Create child stories for the Feature.
3. Assign the stories to a Sprint, but ensure the Team field on the story record itself remains empty/null (e.g., via API or specific Jira sync configurations).
4. Navigate to the Program Board.
5. Observe the Feature card color.
6. Click the Feature to view the Planning Issues list.

Expected Results

The Program Board color logic and the Planning Issues list should use the same validation rules. If the card is Orange due to a missing team, the Planning Issues list should explicitly state that a child story is missing a team assignment.

Actual Results

Feature Card: Displayed as Orange (indicating planning issues).

Planning Issues List: Displays "None", providing no guidance to the user on how to resolve the orange status.

Workaround

Users must manually open each child story and explicitly select/save the Team in the Team field, even if the UI already appears to show a team inherited from the sprint.