Issue Summary

Rovo subscriptions are reactivated during org consolidations and site transfers to another organisation. After the changes, the reactivation of Rovo fails. 

Steps to Reproduce

1. Deactivate Rovo on a site.
2. Move the site from one organisation to another organisation.
3. Try to reactivate Rovo on the site, which is in the new organisation.

Expected Results

Rovo gets activated on the site.

Actual Results

Rovo doesn't get activated on the site, which is in the new organisation. 

Rovo site-level entitlements have a one-on-one relationship with the org-level entitlement. So the reactivation of Rovo on the site fails, as it's still mapped to the org-level Rovo entitlement of the old org.

Workaround

Contact Atlassian support to fix this from the backend.