Originally created by @florian-bellencontre on GitHub (Apr 19, 2023).
Subject of the issue
I don't know if it's a Bitwarden or Vaultwarden bug but if in doubt I post it here, because I couldn't test it on Bitwarden.
The problem is a bad selection of the default owner when creating an item in a collection. This is more an enhancement request than a bug to improve the final user experience.
Deployment environment
Diag:
vaultwarden version: 1.28.1
Install method: Installation from releases and with a compilation
Clients used: Browser (firefox, chrome)
Reverse proxy and version: haproxy
Steps to reproduce
Go to the Vaultwarden home page
Check that we are in "All vaults".
Select a collection
Create an item in this collection
Expected behaviour
It would be better if the selected owner is the organization and the collection where I am is selected.
Kind of like if I did this:
Go to the Vaultwarden home page
Check that we are in my needed organization "Outsourcing" at the top
Select the collection
Create an item in the collection
We can see here that the owner is the organization and that the right collection is selected
Screenshot:
Actual behaviour
The default owner is my user "noc..":
Originally created by @florian-bellencontre on GitHub (Apr 19, 2023).
### Subject of the issue
I don't know if it's a Bitwarden or Vaultwarden bug but if in doubt I post it here, because I couldn't test it on Bitwarden.
The problem is a bad selection of the default owner when creating an item in a collection. This is more an enhancement request than a bug to improve the final user experience.
### Deployment environment
Diag:

* vaultwarden version: 1.28.1
* Install method: Installation from releases and with a compilation
* Clients used: Browser (firefox, chrome)
* Reverse proxy and version: haproxy
### Steps to reproduce
1. Go to the Vaultwarden home page
2. Check that we are in "All vaults".
3. Select a collection
4. Create an item in this collection
### Expected behaviour
It would be better if the selected owner is the organization and the collection where I am is selected.
Kind of like if I did this:
1. Go to the Vaultwarden home page
2. Check that we are in my needed organization "Outsourcing" at the top
3. Select the collection
4. Create an item in the collection
We can see here that the owner is the organization and that the right collection is selected
Screenshot:


### Actual behaviour
The default owner is my user "noc..":


Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @florian-bellencontre on GitHub (Apr 19, 2023).
Subject of the issue
I don't know if it's a Bitwarden or Vaultwarden bug but if in doubt I post it here, because I couldn't test it on Bitwarden.
The problem is a bad selection of the default owner when creating an item in a collection. This is more an enhancement request than a bug to improve the final user experience.
Deployment environment
Diag:

Steps to reproduce
Expected behaviour
It would be better if the selected owner is the organization and the collection where I am is selected.
Kind of like if I did this:
We can see here that the owner is the organization and that the right collection is selected
Screenshot:


Actual behaviour
The default owner is my user "noc..":
