You’re correct that Exalate uses a proxy user to perform actions (like creating comments) on behalf of the remote instance. On Jira Cloud, the proxy user is typically created automatically during the Exalate app installation, and it’s usually named something like ‘Exalate’.
Here are some key points and troubleshooting steps:
Proxy User Visibility
On Jira Cloud, the proxy user is not a regular user you can find in the standard user management screens.
It is an Atlassian Connect App user, which means it appears as an “App” rather than a person.
How to Identify the Proxy User
When Exalate performs an action (like creating a comment), the author will appear as something like “Exalate” or “Exalate Integration” in the issue history or comment author field.
You can check the author of a comment or change made by Exalate to see the exact name.
Permissions for the Proxy User
To grant permissions, you need to add the Exalate app user to the appropriate project roles or permission schemes.
In Jira Cloud, go to Project Settings → Permissions, and look for entries like “atlassian-addons-project-access” or “Exalate Connector” in the permission scheme.
The Exalate app user is usually part of the atlassian-addons-project-access group, which should have the necessary permissions.
If the Proxy User Is Missing
If you don’t see any actions performed by “Exalate” or similar, or if the app user is not present, try the following:
Reinstall the Exalate app on your Jira Cloud instance.
Ensure the app has been granted all required permissions during installation.
After reinstalling, check the project permissions again for the atlassian-addons-project-access group.