The legacy view and new experience UI for the Objective tree should behave in the same way.

Issue Summary

Currently, the Solution Objectives tab is not available in Legacy UI (ObjectivesTree) unless capability is enabled, at the platform level, for the Portfolio configured in the Tier1 bar/filter
The Solution entry in the OBJECTIVE TIER drop-down list is available in the new experience UI (ObjectivesHub) when the Portfolio, configured in the Tier1 bar/filter, is tied to a solution with one or more child programs and therefore does not take into account whether the capability is turned on.

Steps to Reproduce

Prerequisites:

• Portfolio1->Solution1->SolutionObjective1 (Capabilities enabled under JA Administration> SETTINGS > Platform > Portfolio specific configuration > Portfolio1)
• Portfolio2->Solution2->SolutionObjective2 (Capabilities disabled under JA Administration> SETTINGS > Platform > Portfolio specific configuration > Portfolio2)
• User1 should have permission to view all tiers.

Steps
1. Log in as User1
2. Go to the Objective tree
3. Select Portfolio1 in tier 1, click Apply and verify what you see in the Legacy and the New Experience UI
4. Select Portfolio 2 in tier 1, click Apply, and verify what you see in the Legacy and the New Experience UI

Expected Results

Both UI behaves in the same way if you set Portfolio 1 or Portfolio2 in the tier1 configuration bar.

Actual Results

Both UI behaves in the same way if you set Portfolio 1 in the tier1 configuration bar.
With Portfolio2 configured in tier1, the legacy and new experience UIs bring a different behavior:
The Solution Objectives tab is not available/displayed in the legacy UI while you can select 'Solution' in the OBJECTIVE TIER dropdown and view SolutionObjective2 with the new experience UI.

The following small animation shows the difference:

Workaround

Currently, there is no known workaround to get the same behavior for both UI unless you have capabilities enabled under JA Administration> SETTINGS > Platform > Portfolio specific configuration > 'Portfolio Name'

Once you have enabled the capabilities for your portfolio, it cannot be turned off afterward.
This message will appear during the enablement

Enabling Capabilities puts a layer between Epics and Features (Jira Epics). An Epic will be associated with Capabilities and Capabilities will be associated with Features (Jira Epics). The direct Epic and Feature (Jira Epic) association will no longer be possible. Once Capabilities are enabled, they cannot be turned off.

Capabilities will be turned on for this Portfolio only.

If Multi-Programs is turned on then you should not have a mixture of portfolios that have Capabilities on and off (This could result in unusual reporting rollups).