Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "clone"/"copy" suffix when creating a copy of an entry #284

Open
OculiViridi opened this issue Mar 23, 2023 · 2 comments
Open

Add "clone"/"copy" suffix when creating a copy of an entry #284

OculiViridi opened this issue Mar 23, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@OculiViridi
Copy link

What I'd like

Like other KeePass managers do, I'm asking to add a simple suffix like "clone" or "copy" to the name of an entry when copied.

Why

It would make the original entry distinguishable from the newly created cloned one.

@OculiViridi OculiViridi added the enhancement New feature or request label Mar 23, 2023
@keepassium
Copy link
Owner

Thank you for the suggestion! I'm not quite sure about the rationale, though…

As I see it, a user copying an entry either wants to 1) have an exact copy (including the title) or 2) plans to rename it. Currently, the first action is pretty much immediate; we cannot speed up the second one anyway. Automatically adding "copy" means everyone will have to rename the cloned entry. So this would hinder the first action without improving the second one.

What am I missing?

@OculiViridi
Copy link
Author

@keepassium When I was writing the suggestion I was thinking about how the same functionality is already implemented in KeePass and KeePass XC for PC! 😛

So you will know for sure that in KeePass, when you clone an entry, a popup appears asking:

  • if you want to append the suffix "- clone"
  • if you want to copy the history too
  • if you want to replace username and password with references

Since the functionality I would be more interested in would be the second one, then at that point it will be explained why the first one would also make sense.
Maybe this could be the final implementation of the clone functionality. I don't know if you may plan to do it like that...
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants