Issue Summary

Users are unable to disassociate a Theme from an Objective when using the New OKR Experience. The process to remove the Theme appears to work initially, but the Theme is still associated with the Objective. This issue is evidenced by Audit Log entries showing that the Theme is removed and re-added during the save process, even though the user takes no manual actions to re-add the Theme.

Steps to Reproduce

1. Create a new OKR (on the objectives page, select the Add Objective button from the top-right of the page) using the updated OKR creation experience;
2. Select the Portfolio tier
3. Set the mandatory fields
4. On the "Align Work Items" step, select a Theme
5. Publish the Objective
6. Under the Theme "section", click on the "three dots" menu and the "Remove" option
7. Click Save or Save & Close button
8. Reopen the Objective

The same behavior is presented when editing an existing Objective using the New OKR Experience.

The problem is reproducible in version 10.133.3 but not in version 11.0.1.

Expected Results

When a user removes a Theme from an Objective using the New OKR Experience and clicks on Save or Save & Close, the Theme should be disassociated from the Objective, and this change should be reflected when the Objective is reopened.

Actual Results

When a user removes a Theme from an Objective using the New OKR Experience, the Theme appears to be removed initially. However, after clicking Save or Save & Close, the Theme remains associated with the Objective when reopened. The Audit Log shows that the Theme is removed and re-added during the save process without manual user actions.

Workaround

Users can remove the Theme from an Objective using the legacy experience, where the issue is not present. This workaround ensures that the Theme is successfully disassociated from the Objective.