mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #6747] Nested collections and items remain as artifacts after parent collection deletion #2528
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#2528
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Smarak4b on GitHub (Jan 22, 2026).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/6747
Prerequisites
Vaultwarden Support String
Your environment (Generated via diagnostics page)
Config & Details (Generated via diagnostics page)
Show Config & Details
Failed HTTP Checks:
Config:
Vaultwarden Build Version
1.35.2
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
traefik
Host/Server Operating System
Linux
Operating System Version
No response
Clients
Web Vault
Client Version
No response
Steps To Reproduce
Describe the bug
When deleting a parent collection that contains nested sub-collections and items (logins, etc.), the deletion does not cascade. The nested sub-collections and items are not removed from the database, but they become inaccessible through the normal UI and behave inconsistently.
The remaining artifact collections (e.g., ParentName/SubCollection/SubSubCollection) appear empty (items are hidden/removed from view). However, if a new collection is created with the exact same name as the originally deleted parent, the entire previous hierarchy and all its items reappear, attached to the new collection. This indicates the data is not truly cleaned up and leads to data ghosting and confusion.
To Reproduce
Steps to reproduce the behavior:
Create a collection hierarchy. Example:
Collect_1
Sub_Test1
Sub_Test1_1
my_login
my_login2
Delete the top-level collection (Collect_1).
Now, create a new collection named Collect_1.
Observe the bug: The entire original hierarchy (Sub_Test1 -> Sub_Test1_1) and all login items (my_login, my_login2) reappear under the newly created Collect_1.
Expected Result
Collect_1 and all its contents (Sub_Test1, Sub_Test1_1, my_login, my_login2) are completely deleted.
Actual Result
Collect_1 is removed from view. An artifact named something like Collect_1/Sub_Test1/Sub_Test1_1 may remain visible but appears empty. The items are not visible anywhere.
Logs
Screenshots or Videos
STEP 1




STEP 2
STEP 3
STEP 4
Additional Context
No response
@Smarak4b commented on GitHub (Jan 22, 2026):
Oh, the order of the screenshots is messed up, sorry