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

New Issue

2026-03-07T19:01:17-06:00

GiteaMirror commented

2026-03-07 19:01:17 -06:00

Originally created by @mprasil on GitHub (May 16, 2018).

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 (May 16, 2018). 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?

GiteaMirror closed this issue

2026-03-07 19:01:17 -06:00

GiteaMirror commented

2026-03-07 19:01:17 -06:00

@dani-garcia commented on GitHub (May 19, 2018):

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 (May 19, 2018): 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?

GiteaMirror commented

2026-03-07 19:01:18 -06:00

@mprasil commented on GitHub (May 19, 2018):

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 (May 19, 2018): 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.

GiteaMirror referenced this issue

2026-04-20 13:52:55 -05:00

[GH-ISSUE #3646] New Version Version: 2023.3.0 Unable to import the csv of keepassX, there is no response after clicking. #10443

GiteaMirror referenced this issue

2026-04-23 06:10:15 -05:00

[GH-ISSUE #3646] New Version Version: 2023.3.0 Unable to import the csv of keepassX, there is no response after clicking. #14420

GiteaMirror referenced this issue

2026-04-25 20:35:31 -05:00

[GH-ISSUE #3646] New Version Version: 2023.3.0 Unable to import the csv of keepassX, there is no response after clicking. #18403

GiteaMirror referenced this issue

2026-06-17 08:42:23 -05:00

[GH-ISSUE #3646] New Version Version: 2023.3.0 Unable to import the csv of keepassX, there is no response after clicking. #29121