Keepassxc: Find REF origin/usages in search box

[ftorto]

The way to answer my 2 following use cases is a bit complicated and I think look for REFerences directly from the search box could help :

• I want to know what is the original entry pointed by the reference of my current entry
• I want to find all the entries referencing my current entry

Expected Behavior

• Paste the reference to check in searchbox
• Entries depending on this reference AND entry matching this reference are displayed in results

Current Behavior

Currently, to know what is the original entry, I change {REF:U@I:<reference_id>} by {REF:T@I:<reference_id>} (note the U changed to T) as detailed in #433 and try to find the corresponding entry
The second usecase can't be done

Possible Solution

Searchbox could be the easy way to implement but UX could be improved with right-click (as suggested in #433 too for a similar behaviour: copy the ref to clipboard)

Context

Context already detailed in summary above

[TheZ3ro]

For the first point: "I want to know what is the original entry pointed by the reference of my current entry" should be nice to have an entry UUID option in the search engine, so you can search an entry by pasting his UUID (it's the <reference_id> in your examples). ping @droidmonkey

For the second one: "I want to find all the entries referencing my current entry" it's more complicated and I think will need some time to develop

[droidmonkey]

This would be better implemented as a GUI element. I have an idea for a "meta" database class that contains dynamically computed relationship and other information about the database after it is opened and/or changed.

[Felixoid]

Hello. Is there some progress?

[nniesen]

In KeePass2, I can click on the {REF:...} to navigate to the source entry. I make extensive use of refs, especially with SSO/OAuth systems and when the login url is different, so its useful for me to be able to navigate to the source of the ref. I like that you show the resolved value of the ref but would like some means to navigate to it. I think this would negate the OPs first need but not their second need to see all children.

[gaensler]

Any news on this topic? I worked a lot on building databases with references lately and found the two mentioned features very useful:

Search entries by UUID - maybe showing both the entry with that UUID and entries using that UUID as reference would be confusing. I think there should be some kind of search-flag "don't) resolve in references", so you can toggle if references should be resolved during searching or not. This would make the search-behaviour more precise.

Copy UUID from right-click-menu would save a lot of clicks!
Or maybe add an "copy attribute as reference" sub-menu to the right-click-menu like the existing "copy attribute" one.

I think those are actually two separate features for the whole reference thing... If this get's more attention i would open a request for the right-click-menu thing.