JabRef version
6.0-alpha.4
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Follow https://docs.jabref.org/setup/customentrytypes
How to reproduce
- Type "Book" and press the + button

- Notice there are now two entrytypes with the name of "Book".
- Press "save"
Result:
The custom entry type "Book" overwrites the standardtype "Book", hence instead of two books, there will only be one book and all fields will be gone.

Solution
At the very least, if users type in the field for custom entry types, they should not be able to press the + button, if this entrytype already exists. There are should be a tiny tooltip that tells the user duplicate entry types are not supported. Something along the lines of "It is not possible to have two entry types with the same name".
I am not quite sure yet, what implications this has for migrating from old versions of JabRef to new Versions of JabRef with updated entrytypes or even what happens, if users with custom entry types open a library with unique entry types.
Appendix
...
Log File
Paste an excerpt of your log file here
JabRef version
6.0-alpha.4
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
Follow https://docs.jabref.org/setup/customentrytypes
How to reproduce
Result:
The custom entry type "Book" overwrites the standardtype "Book", hence instead of two books, there will only be one book and all fields will be gone.

Solution
At the very least, if users type in the field for custom entry types, they should not be able to press the + button, if this entrytype already exists. There are should be a tiny tooltip that tells the user duplicate entry types are not supported. Something along the lines of "It is not possible to have two entry types with the same name".
I am not quite sure yet, what implications this has for migrating from old versions of JabRef to new Versions of JabRef with updated entrytypes or even what happens, if users with custom entry types open a library with unique entry types.
Appendix
...
Log File