Setting a Single PI on the Configuration Bar of a Program Board fails to show a Red Status for a Feature

Issue Summary

In a Program Board when the Configuration Bar filters are set to 1 Project and 1 PI, then an Epic shows with a non-Red Status. However if the filter is changed to include a later/next  PI as well, then the Epic shows with a Red Status. The correct status should be Red for both filter choices.

This happens because at least one of the stories in the Epic is scheduled for a sprint that is under a later PI and this sprint falls after the Team Target Completion Sprint  of the Epic (which is in the first PI). Note: If the later sprint is after the target completion sprint but within the same PI, then the status will show correctly (as Red) when only filtered on the one PI

Reporting customer is indicating that NOT displaying a Red Status when using a single PI filter, where the Target Completion Sprint  for the Epic is inside the filtered PI dates but one or more stories are in a sprint for a later PI, is a problem as a missed feature target could easily be overlooked when discussing the success of a single PI.   
 

Steps to Reproduce

Note: all images are from a test environment

1. Create two consecutive PIs in Jira Align, where the last sprint of the first PI will be covering the current date and the second PI is for a later date
2. Create Anchor sprints in both PIs
3. In Jira (in a project and board that is already configured to synchronize with Jira Align), create a sprint that matches the last anchor sprint in the first PI
4. In Jira create a sprint that matches the first anchor sprint in the second PI
5. In Jira , create an Epic
6. In Jira create 4 stories that are associated to that Epic add them to the first sprint
   
7. Start the first sprint
8. In Jira Align check that the 4 stories have appeared
9. In Jira Align check that the Feature / Jira Epic has appeared
10. In Jira set all 4 stories and the Epic to In Progress 
11. In Jira Align open the Program Board (filtered for 1 Program and just the first PI) and click on the feature to open the details
12. Set the Team Target Completion Sprint to the first sprint
13. The colour status of the Epic will not red (and is probably blue) - +this is correct at this point
    
    +
14. Back in Jira set the first 3 stories to Done, but move the 4th story to the 2nd sprint (1st sprint of the second PI)
15. In Jira Align open/refresh the program board, the feature will still not show a Red status. This is incorrect
16. Click on the feature to open the details, the Stories list will show 3 accepted stories and 1 story in progress with the Target completion highlighted in red, showing that a Planning Issue has been identified for the feature against the story that is now in the later PI
    
17. Close the details tab and change the Configuration Bar filter to include both PIs - the Feature now displays in Red. +This is correct but should not need the filter setting to 2 PIs to be correct.
    +
     

Expected Results

The Red Status against a Feature in the Program Board should be displayed when ONLY the PI for the target completion sprint is set as a filter, if any story associated with the feature is assigned to a sprint (in a later/different PI) 

Actual Results

The feature displays that Status Colour based on the stories that are in the filtered PI and does not take into account that there may be stories linked to the feature that are in another PI. 

Workaround

Changing the Configuration bar filter to include the PIs covering the stories linked to all features in the program board will show the correct status colours, but does not help with a review of a single PI and the user also has to manually identify all the required PIs by checking every feature.