Issue Summary

The end user encounters a warning message while accessing the Risk ROAM report from the Portfolio Level > Status Report > Health field. (from the little scales icon).
Even if the user selects a single Program Increment from the drop-down on the Portfolio Level the warning states "Select one program and one program increment"

Steps to Reproduce

1. Select a Portfolio that has more than one Program
2. Go to Portfolio > Select a single Program Increment
3. Go to Reports > Status Report
4. Select an Epic from the Status Report list and click the Epic for details
5. Now, click the "Health" field where there are 5 small icons visible
6. Click the small scales icon, this will route the user to the Risk Roam Report Page (by default to xxxx.jiraalign.com/RiskRoamReport?FirstTime=True)
   You can test it by hovering over these little icons to see the links
7. Now, on the Risk ROAM page, you will see a warning message will be seen as "Select one program and one program increment"
8. The issue is that the Risk Roam Report is on the program level. The Status Report is accessible at both the Portfolio Level and Program Level. When the user navigates the Status Report from the Portfolio Level > Epic > Health and clicks the little scales (Risks) icon, the new page routes the user to the Risk Roam Report with the Portfolio filter in the URL. This populates the error "Select one program and one program increment" even though a single PI is selected.
9. By following the same steps from the Program Level the user can see the Risks without a warning by selecting a single PI

Expected Results

This is confusing for the end users, either the user should not be able to access the Risk ROAM report from the Portfolio Level Status Report or the report should work properly

Actual Results

When the user navigates the Status Report from the Portfolio Level > Epic > Health and clicks the little scales (Risks) icon, the new page routes the user to the Risk Roam Report with the Portfolio filter in the URL. This populates the error "Select one

Workaround

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