Issue Summary

When creating a sandbox deployment, JSM "Service Space Agent" space permission entries are not carried over to the destination environment. The deployment completes successfully with no errors reported in the deployment log for Permission Schemes.

Steps to Reproduce

1. On the source site, confirm a JSM project has "Service Space Agent" configured in space permissions (with roles such as Administrator and Service Desk Team).
2. Go to admin.atlassian.com > Apps > Sandboxes.
3. Create a deployment.
4. Wait for deployment to complete.
5. On the destination site, navigate to the Permission schemes.
6. Check for the "Service Space Agent" permission entry.

Expected Results

The "Service Space Agent" permission entry (and its associated roles/groups) should be present in the sandbox after deployment, matching the source environment.

Actual Results

The "Service Space Agent" permission is not copied as expected. Some Roles might be missing, e.g. Service Desk Team and Administrators.

The deployment log does not report any error or warning related to Permission Schemes, making this a silent failure.

Workaround

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

The permission scheme can be updated manually to restore the expected permission entries.