Issue Summary

Feature Backlog from the Product Management area doesn't show Value Stream Kanban

This is reproducible on Data Center: yes

NOTE: The following works.

• The Value Stream Kanban view does appear for the same set of Features when user goes to the Program level module >  Backlog >  Features Backlog
• The same also works within Portfolio level module > Backlog > Feature Backlog
• Also, this works if user navigates to Product Management module > Backlog > Feature Backlog > List view, the same feature is displayed fine there
• Also, in the same Product Management module > Backlog > Feature Backlog > Kanban > State View, this state-based kanban is also working

Therefore, the issue seems to be specific to the Product Management module > Backlog > Feature Backlog > Kanban > Process Flow (Value Stream) view.

Steps to Reproduce

1. Navigate to Portfolio > Select a Portfolio > Process Flows (Value Streams)
2.  Create a Value Stream for Level: Feature for a given Program. Also in the same Value Stream slide out > Process Steps tab, add a Process Step
3. Create a Feature that is assigned to the above same Program (and thus the Value Stream). Also assign a specific Product to that Feature (don't assign it to a PI)
4. Make sure in the above Feature slide out > Details panel, the Process Step field is set to the above-created Step 2 process step 
5. In the new JA UI, go to the Product Management module and choose the Product that was assigned to the Feature.
6. In the left hand menu under the Product module, choose the Backlog option
7. In the Backlog view, when viewing the Feature backlog, click on the Kanban button and select Value Stream View
8. When the screen refreshes, expand the unassigned Backlog

Expected Results

A Kanban board view of the Features based on the Value Stream will appear

Actual Results

An error message appears "No Value Streams defined for this level (click here to set this up)" appears for the Product module as shown in the attached screenshot

Workaround

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