Program Board: Dependencies in the Program Board showing the wrong color (RED) with no planning issue

Issue Summary

Dependencies in the Program Board showing the wrong color (RED) with no planning issue

Steps to Reproduce

• Preconditions:
  • Program and Release#1 and Release#2 with anchor sprints created
  • 2 Kanban Teams (Kanban Team_A and Kanban Team_B) are created under the Program
  • Feature in Program and Release#2 is created
  • Story_A is created and assigned to Program, Release#2 and Kanban Team_A
  • Kanban Team_A should have a throughput value (e.g. 1)
  • There should be a Dependency_A associated with the Feature requested by Kanban Team_B and dependent on Kanban Team_A (Committed)
  • Story_A should be assigned to Dependency_A
  • Make sure the Story Target Completion date is before Dependency committed by date

• Steps:

1. Select Program and Release#2 from preconditions in Tier 1
2. Go to Program Board report
3. Check the dependency color on the board
4. Check the planning issue message on the Dependency quick view panel

Expected Results

1. Dependency displays in blue (might be different, depending on the conditions)
2. There are no red planning issues

Actual Results

1. Dependency displays in red
2. There are no red planning issues
   after moving features on the board the dependency color changes to blue until the page is reloaded
   (Note: in some cases, the Dependency shows in blue but with a red warning message.)

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available