-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
High
-
Component/s: Site Performance - Site Optimiser
-
None
-
Severity 3 - Minor
Issue Summary
Site Optimizer fails to delete JSM portal-only customer accounts from space roles and cannot remove orphaned "Deleted roles".
Steps to Reproduce
- Step 1 Navigate to Settings > System > Site Optimizer (or Site Cleaner).
- Step 2 Scan space/project roles on a Jira Service Management space containing:
Portal-only customer accounts (qm:... UUIDs) assigned under the Service Desk Customers role.
Role assignments referencing deleted project roles (e.g., Deleted roles (2)).
Select the affected space role entries and attempt to delete/clean them up.
Refresh or re-run the Site Optimizer scan
Expected Results
Site Optimizer successfully deletes all selected space role entries, including portal-only customer assignments and orphaned references to deleted roles.
Actual Results
The UI reports successful deletion, but the backend silently fails/skips removing portal-only customer accounts because standard Jira role-actor deletion APIs cannot remove accounts managed through JSM's customer access layer. Orphaned records referencing deleted roles also remain stuck in the database, and subsequent scans continue to show the same entries.
The below exception is thrown in the xxxxxxx.log file:
...
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available