Issue Summary

When a new sandbox instance is created, the customer account ID (portal-only) doesn't remain the same as the production instance. This is expected behavior as customer account is created at site level, but user account is created at org level.

However, some inconsistencies are noticed:

1) Customer account ID does not contain qm part:

However, the discrepancy is that customer accounts in sandbox are being created without "qm" mention, which is not the default for customer accounts - this behavior is not noticed in production instance.

As a result, when trying any simple action in the user as revoking access, we can the error message:

Something went wrong / Try again later. 
In the inspect mode we have the following message:

"message": "Request validation failed: Parameter (accountId) does not match required pattern: ^qm:[a-zA-Z0-9-]+:[a-zA-Z0-9-]+$" 

2) Duplicate customer accounts are created:

In sandbox, if we access admin.atlassian.com > Jira Service Management, we will be able to notice duplicate customer accounts (for users without Atlassian Account) for the same email address, what can cause confusion.

3) Customer account export does not work:

When using customer export option in the sandbox, only a few users are exported, and most of them don't appear in the file.

Steps to Reproduce

1. Create a sandbox instance;
2. In the sandbox site > Admin panel > Under JIRA SERVICE MANAGEMENT > Portal-only customers
3. Try to revoke customer access.

Expected Results

The access should be revoked, and all the users should be exported to the file in the sandbox instance.

Actual Results

That's not possible to revoke access, and only a few users are exported.

Workaround

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