Jabref 2.10 seems to have changed which fields are considered Required and Optional for common BibTeX entry types such as Article.
In addition, when you try to over-ride the new defaults by using the "Customise entry type" dialogue, the changes that you apply with this dialogue are soon reset by Jabef (possibly at the next Autosave of a .bib file, but I'm not sure of this).
It also seems that you can no longer change the default order for Required entry types (as they appear in the tabbed panel below the entry table).
For example, the default order for Required entry types for an Article is now alphabetical: Author, Journal, Title, Volume, Year. If you add Pages as a Required field for Article, then no matter where you choose to customise its position in the Required list, JabRef will at first show your chosen order and then a few minutes later, without exiting JabRef or doing any further editing of the file except to navigate to other entries in the .bib file, the displayed order of the Required fields will be reset (apparently spontaneously) to alphabetical order. When this happens, Pages will be relocated to lie in alphabetical order between Journal and Title, which is an absurd order to use.
This may not be a fatal, or even data-threatening, bug, but it is intensely annoying.
Can the previously stable behaviour of the "Customise entry types" dialogue be restored, please?
In particular, can JabRef be prevented from over-riding the user's customised choice and order of entries?
None of these problems were noticed with any previous version of JabRef: I've used every version since 2.4.
Log in to post a comment.