How to Clear a User's Profile Settings via Direct Database Query for on-premise installtions

Description

Spira stores user-specific profile settings across several database tables. These settings control personalized UI behavior such as dashboard layouts, filter preferences, sorting options, and other customizations. Over time, these settings can become inconsistent or corrupted, leading to display issues or unexpected behavior.

There is no built-in UI option to clear all of a user's profile settings at once, so direct database intervention is required.

The Query

DELETE FROM TST_REQUIREMENT_USER WHERE USER_ID = <user_id>
GO
DELETE FROM TST_RELEASE_USER WHERE USER_ID = <user_id>
GO
DELETE FROM TST_USER_COLLECTION_ENTRY WHERE USER_ID = <user_id>
GO
DELETE FROM TST_PROJECT_COLLECTION_ENTRY WHERE USER_ID = <user_id>
GO

Consider to replace `<user_id>` with the numeric User ID of the target user. You can find the User ID in View/Edit Users admin menu or on the user's profile page. 

Query Explanation

DELETE FROM TST_REQUIREMENT_USER WHERE USER_ID = <user_id>  
Clears the user's personalized requirement view settings (e.g. expanded/collapsed nodes in the hierarchy). Does not remove ownership or assignments.

DELETE FROM TST_RELEASE_USER WHERE USER_ID = <user_id>  
Clears the user's personalized release view settings (e.g. expanded/collapsed nodes in the hierarchy). Does not remove ownership or assignments.

DELETE FROM TST_USER_COLLECTION_ENTRY WHERE USER_ID = <user_id>
Clears the user's global settings such as My Page layout, dashboard preferences, color mode, and language.

DELETE FROM TST_PROJECT_COLLECTION_ENTRY WHERE USER_ID = <user_id>
Clears the user's project-specific settings such as saved filters, column layouts, and sorting preferences.

When this query can be used

- A user reports broken page layouts, missing widgets, or UI elements not displaying correctly.
- A user experiences persistent display or navigation issues that cannot be resolved through the application interface.
- You want to reset a user back to the default "out of the box" experience.

Important Notes

- Back up first: We recommend taking a backup of the affected data before running the DELETE statements.
- This is irreversible without a backup: Once deleted, the user will lose all their personalized layouts, saved filters, and UI preferences. They will see default settings on their next login.
- No application restart required: The application reads these settings dynamically. The user will see fresh default settings on their next page load or login.
- No business data is affected: These queries only remove UI personalization settings. They do not remove artifact ownership, assignments, or any project data.
- Database access required: You will need direct access to the Spira database (e.g. via SQL Server Management Studio) with permissions to run DELETE statements.