Anyone having an issue when creating a new item in a folder, it doesn't set the folder

gooseleggs · July 20, 2025, 11:14pm

I am running 2025.6.1. When I am in a folder, and click the + for a new item, I can create the new item, but the Folder location does not represent the current location, ie it is set at No Folder. Haven’t logged it as an issue yet. Just wanting to know if it is me, or a general problem.

Neuron5569 · July 20, 2025, 11:27pm

This bug:

github.com/bitwarden/clients

When inside a folder of logins, and you click "New login" it does not automatically assign folder anymore

opened 01:52PM - 17 Jul 25 UTC

Ben-xfg

bug desktop

### Steps To Reproduce 1. Open BitWarden Desktop 2. Click on a folder to show t…he folders contents. 4. Click on the "+" icon at the bottom of the folders 5. Click on "Login" ### Expected Result It should now open a new login page and automatically assign the folder to the folder you are currently in. ### Actual Result You will notice that it does not automatically assign the folder to the one that you are currently in. It used to do this before the last update. Another thing that it used to do is when you click on the "+" icon it just automatically created a login which is what I usually want to create - can you make Login the default action again please? If not, then let us choose the default action when clicking on the "+" button. ### Screenshots or Videos _No response_ ### Additional Context _No response_ ### Operating System Windows ### Operating System Version Win 11 Pro ### Installation method Direct Download (from bitwarden.com) ### Build Version 2025.6.1 ### Issue Tracking Info - [x] I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

gooseleggs · July 21, 2025, 12:05am

Yes that bug. Why didn’t I see that!!

Thanks

a1ex · November 14, 2025, 7:19pm

That’s a super annoying bug. When will it be fixed? anyone knows?

grb · November 14, 2025, 7:33pm

Evidently there was a (community-contributed?) pull request to fix this, but it is still awaiting code review by Bitwarden developer Jason Ng.