Not sure, but I think this should be opt-in rather than opt-out. In my case, I want the timestamp to reflect when I acquired an entry, and the date I last modified it doesn't really matter.
For others the priorities may be different. However, if a new version suddenly starts updating timestamps without the user being aware of it, users who use it the way I do may lose information. If we introduce it, but leave it off by default there should be no surprises.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This feature should be working in the latest development version. Please find a snapshot of JabRef 2.10dev at http://ge.tt/9Idc446 .
Not sure, but I think this should be opt-in rather than opt-out. In my case, I want the timestamp to reflect when I acquired an entry, and the date I last modified it doesn't really matter.
For others the priorities may be different. However, if a new version suddenly starts updating timestamps without the user being aware of it, users who use it the way I do may lose information. If we introduce it, but leave it off by default there should be no surprises.
I agree. Fixed in master branch.