Generate BibTeX key does not work in "BibTeX source" panel

[koppor]

I pasted the following bibtex entry - and wanted to generate the key using Ctrl+G.

@Article{Saatkamp201ddd9,
  author    = {Karoline Saatkamp and Uwe Breitenb{\"{u}}cher and Oliver Kopp and Frank Leymann},
  journal   = {Computer Science - R{\&}D},
  title     = {An approach to automatically detect problems in restructured deployment models based on formalizing architecture and design patterns},
  year      = {2019},
  number    = {2-3},
  pages     = {85--97},
  volume    = {34},
  bibsource = {dblp computer science bibliography, https://dblp.org},
  biburl    = {https://dblp.org/rec/bib/journals/ife/SaatkampBKL19},
  doi       = {10.1007/s00450-019-00397-7},
  timestamp = {Sat, 19 Oct 2019 19:13:28 +0200},
  url       = {https://doi.org/10.1007/s00450-019-00397-7},
}

Note that it sometimes works - I haven't found out. Here a video where it did not work:

[bulmust]

JabRef 5.0-beta.1--2019-12-15--0b8b1d6
Linux 4.15.0-72-generic amd64
Java 13.0.1

If you change BibTeX key generator option to empty one, the problem still occurs.

Also, If you fetch a article from a database (for example inspire), the original inspire bibtex key is changed by BibTeX key generator. This behavior does not occur at JabRef 4.3.1.

It seems like, key generator has a priority no matter you want to do.

[koppor]

I think, the behavior with the bibtex key overwriting thing is intended. We want JabRef do to more magic. However, that change is not included in the CHANGELOG 😕

The thing with the empty one not.

[bulmust]

We should keep our hope until stable version is released.

[github-actions]

This issue has been inactive for half a year. Since JabRef is constantly evolving this issue may not be relevant any longer and it will be closed in two weeks if no further activity occurs.

As part of an effort to ensure that the JabRef team is focusing on important and valid issues, we would like to ask if you could update the issue if it still persists. This could be in the following form:

• If there has been a longer discussion, add a short summary of the most important points as a new comment (if not yet existing).
• Provide further steps or information on how to reproduce this issue.
• Upvote the initial post if you like to see it implemented soon. Votes are not the only metric that we use to determine the requests that are implemented, however, they do factor into our decision-making process.
• If all information is provided and still up-to-date, then just add a short comment that the issue is still relevant.

Thank you for your contribution!

[Siedlerchr]

Works fine in the current master.