Allow setting default group for database

[thgreve]

The entry which had been accessed last before shutdown of the database shoud be stored and when the database is reopened the next time it should be reselected

Expected Behavior

see general description

Current Behavior

When reopening a database the selected group in the left pane is always root

Debug Info

KeePassXC - Version 2.3.4
Revision: 2cc52a8
Distribution: Snap

Libraries:

• Qt 5.9.5
• libgcrypt 1.8.1

Operating system: Ubuntu Core 18
CPU architecture: x86_64
Kernel: linux 4.15.0-34-generic

Enabled extensions:

• Auto-Type
• Browser Integration
• Legacy Browser Integration (KeePassHTTP)
• SSH Agent
• YubiKey

[droidmonkey]

We do not save state between database tab close and reopen. This could be saved in the per-database settings that I've wanted for a while, but what is the purpose? I could see many people not wanting this behavior at all.

[thgreve]

Rationale for that proposal: It's quite likely that the last selected entry is also the most used one (e.g. password of the e-mail-account). It's also pretty likely that the first entry which should be selected is also the most used one. So a preselection of the last selected entry or at least of the group (including its display) would be a quite comfortable option.

An better alternative to reach the goal of easy selection would be a MFU-list (most frequently used) of entries being selected. But I guess that this is more hard to implement.

[TheZ3ro]

I agree with @droidmonkey

There is no purpose in this. Many users only use the browser extension or autotype so having a selected entry after unlock isn't a big priority.
Also storing this information outside the database is only possible if you store the entry uuid and the database path so isn't really easy to implement.

[reitffunk]

If I remember correctly selecting the last used folder is also standard behavior for the original KeePass. Basically this is the only noticeable difference for me, since I switched to KeePass XC.

I would like this feature too, especially at work, where most of my stored passwords are not for some web accounts, but server passwords, keys and other stuff.

[ba32107]

I second the others - I am missing this minor "feature". This is something I really liked in the original KeePass. I have a group called "Most used", which I'd prefer to be pre-selected.

[droidmonkey]

Perhaps we can add a "default group" database setting. When the db is unlocked that group is selected.

[reitffunk]

I have the feeling that this was not a database setting but a "setting per KeePass instance".

I think so, because I am using the same database for private and work related stuff but on different computers hence different KeePass installations. Nevertheless after opening the database different folders were selected for both computers.

But yeah, I see that this is some edge case and not that high of a priority.

[sander85]

I remember some older version selecting last used folder and it helped a lot. Selecting last used item would help even more. One example - I have a laptop where I need TOTP every time I want to connect to VPN and that happens a lot. I can use Ctrl + T to easily get the TOTP but I always have to select the correct folder and then correct item, which is really cumbersome. If there would be a per client option to remember the last used item on db unlocking it would be great (doesn't have to be activated by default).

[droidmonkey]

You can just move the most used items directly to your root folder. You can even clone them and just move the clones to root. This doesn't require cumbersome settings.

[controlrepo]

You're saving a number of recently opened databases in ~/.config/keepassxc/keepassxc.ini anyway, adding the last used folder in the same place shouldn't be that disruptive, no one expects this to be saved within the database itself.

Due to new job arrangements I cannot use KeePass here, and apart of this one thing KeePassXC looks like perfect replacement, it's just constant need to click for the last used group->subgroup that becomes real PITA (I keep more than a handful of logins, notes, keys and tokens in the database, it's infeasible to just throw out the subset of these to the Root only because "I won't be using it myself, therefore I am right" approach. It disrupts the whole idea of using folders to organise entries.

Thanks for the great product otherwise (I especially love AutoOpen feature as it saves me tons of time due to the fragmentation of credentials organisation in my company).

[droidmonkey]

We remember the last used group if you are just locking the database. The first time you open it we go to the root group.

[reitffunk]

You're saving a number of recently opened databases in ~/.config/keepassxc/keepassxc.ini anyway, adding the last used folder in the same place shouldn't be that disruptive, no one expects this to be saved within the database itself.

Due to new job arrangements I cannot use KeePass here, and apart of this one thing KeePassXC looks like perfect replacement, it's just constant need to click for the last used group->subgroup that becomes real PITA (I keep more than a handful of logins, notes, keys and tokens in the database, it's infeasible to just throw out the subset of these to the Root only because "I won't be using it myself, therefore I am right" approach. It disrupts the whole idea of using folders to organise entries.

Thanks for the great product otherwise (I especially love AutoOpen feature as it saves me tons of time due to the fragmentation of credentials organisation in my company).

Jep, that would be the way to go from my perspective. That way we would have the "last used group" saved per installed KeePassXC instance. This means one could use the same database on lets say work and private computer and it opens up the preferred (and different) group for both of computers. For example at work I always want to start with my companies folder but at home it is another one.