Organization Vault does not show unassigned ciphers under "Unassigned" #2411

New Issue

Closed

opened 2025-10-09 18:04:17 +03:00 by OVERLORD · 2 comments

OVERLORD commented 2025-10-09 18:04:17 +03:00

Owner

Copy Link

Originally created by @mprasil on GitHub.

In the Organization Vault, all the ciphers that have no Collection assigned do not show under Unassigned section. The ciphers are only visible under "All items". From what I can see the API correctly returns such ciphers with CollectionIds set to [] and when editing the collections assignment, Vault correctly displays that cipher is in no collection, it's just that filtering misbehaves for some reason.

Could be that the upstream API actually returns Null instead of [] or there is some extra field indicating no collection assignment, that we don't send?

Originally created by @mprasil on GitHub. In the Organization Vault, all the ciphers that have no `Collection` assigned do not show under `Unassigned` section. The ciphers are only visible under "All items". From what I can see the API correctly returns such ciphers with `CollectionIds` set to `[]` and when editing the collections assignment, Vault correctly displays that cipher is in no collection, it's just that filtering misbehaves for some reason. Could be that the upstream API actually returns `Null` instead of `[]` or there is some extra field indicating no collection assignment, that we don't send?

OVERLORD closed this issue 2025-10-09 18:04:18 +03:00

OVERLORD commented 2025-10-09 18:04:21 +03:00

Author

Owner

Copy Link

@dani-garcia commented on GitHub:

I just tried this and I can't reproduce it. The official API returns [] like us, and in my testing it seems to work fine (the ciphers appear both in All items and unassigned). Can you find a simple example where the problem occurs?

@dani-garcia commented on GitHub: I just tried this and I can't reproduce it. The official API returns [] like us, and in my testing it seems to work fine (the ciphers appear both in All items and unassigned). Can you find a simple example where the problem occurs?

OVERLORD commented 2025-10-09 18:04:22 +03:00

Author

Owner

Copy Link

@mprasil commented on GitHub:

I'm just testing it now and it seems like that might have been issue with Vault 1.24.0, I can't reproduce this in 1.26.0 so I'm going to close this one.

@mprasil commented on GitHub: I'm just testing it now and it seems like that might have been issue with Vault `1.24.0`, I can't reproduce this in `1.26.0` so I'm going to close this one.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

test_dylint

1.34.3

1.34.2

1.34.1

1.34.0

1.33.2

1.33.1

1.33.0

1.32.7

1.32.6

1.32.5

1.32.4

1.32.3

1.32.2

1.32.1

1.32.0

1.31.0

1.30.5

1.30.4

1.30.3

1.30.2

1.30.1

1.30.0

1.29.2

1.29.1

1.29.0

1.28.1

1.28.0

1.27.0

1.26.0

1.25.2

1.25.1

1.25.0

1.24.0

1.23.1

1.23.0

1.22.2

1.22.1

1.22.0

1.21.0

1.20.0

1.19.0

1.18.0

1.17.0

1.16.3

1.16.2

1.16.1

1.16.0

1.15.1

1.15.0

1.14.2

1.14.1

1.14

1.13.1

1.13.0

1.12.0

1.11.0

1.10.0

1.9.1

1.9.0

1.8.0

1.7.0

1.6.1

1.6.0

1.5.0

1.4.0

1.3.0

1.2.0

1.1.0

1.0.0

0.13.0

0.12.0

0.11.0

0.10.0

0.9.0

Labels

Clear labels

better for forum

bug

bug

bug

documentation

duplicate

enhancement

future Vault

good first issue

help wanted

low priority

notes

pull-request

Mirrored from GitHub Pull Request

question

SSO

Third party

troubleshooting

troubleshooting

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

OVERLORD

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/vaultwarden#2411