Features with a Red Planning Issue status do not shows as Red in the Program Board

Issue Summary

In the Program Board, some features that should show a Red status for Planning issues are showing incorrectly with other colors such as Orange or Blue. For all features showing incorrect status colors, the red planning issue involved is
"Some Stories are planned for completion after the Feature's (Jira Epic's) Planned Completion Sprint" 

The features (and child stories) are being worked in a Kanban Team and all features and stories are in the same team (or in no team yet). There a couple of red status stories that fall into the next PI, (which matches an existing bug) but does not explain why red status stories in the current PI don't get reflected in the colour of the feature. 

Note: in below description dates are in format MM/DD

Feature 7081 is Blue and should be Red

• The pop-up when hovering over the feature does show a red status
• The Quick View details of the feature also show the Red Planning issue.
• Feature has target completion sprint of S3 (10/31 - 11/11)
• Child Story 38222 is Accepted with completion date of 11/04 (Black Status)
• Child Story 80465 is In Progress with Target Completion of 11/18 (Red Status)
• Child Story 84230 is In Progress with Target Completion of 11/18(Red Status)
• Child Story 34232 is Accepted with completion date of 11/16 (Red Status)
• Child Story 89648 is Pending Approval with Target Completion of 12/02 (Red Status)

Feature 7133 is Orange and should be Red

• The pop-up when hovering over the feature does show a red status
• Feature has target completion sprint of S3 (10/31 - 11/11)
• 4 Child Stories in Progress with Target Completion 11/18 (Red Status)
• 2 Child Stories in Dev Complete with Target Completion 11/18 (Red Status)
• 2 Child Stories in Ready to Start with Target Completion 12/09 (Red Status)
• 4 Child Stories in Accepted with different, earlier dates 10/10 (Black Status)
• 1 Child Story not in the team but under the feature (causes the Orange status but listed as white)
• 2 Child Stories in Accepted with Target Completion after 11/11 (Red Status)
• 3 Child Stories in Pending Approval with Target Completion 12/16 (Red Status)
• 1 Child Story in Pending Approval with Target Completion 12/02 (Red Status)

Program Increment Y22-PI4 runs from 03 Oct 2022 to 09 Dec 2022

There are images showing the customers screens in the GSAC ticket (for data protection reasons  they cannot be added here.)

Steps to Reproduce

1. Unable to reproduce by deliberately creating stories (in a Kanban Team ) that have the same planning issues as those seen by customer..
2. Can reproduce for Scrum Teams where 2 PIs are involved - which is the subject of related bug https://jira.atlassian.com/browse/JIRAALIGN-4070

Expected Results

The red status caused by a Planning issue of "Some Stories are planned for completion after the Feature's (Jira Epic's) Planned Completion Sprint" should show against the tiles for the features in the Program Board 

Actual Results

The tile for the feature shows the colour based on the next highest planning issue status: Blue for In progress and no planning issues, Orange for a different type of planning issue etc

Workaround

No valid known workaround for the tile display in the Program Board itself.  Users can confirm the correct planning status by hovering the mouse over a feature, or by opening the Quick View