Oliver Kopp

This refs https://github.com/JabRef/jabref/issues/11026#issuecomment-2370583648.

For a structured approach, one needs to write down what existing tools are doing. For instance: BibDesk. They are are good in distinguishing automatic and non-autoamtic groups:  I think,...

To really come up with a solution, one needs to have a minimal example showing the different options. One can start with `Chocolate.bib`. In other words [requirements analysis](https://en.wikipedia.org/wiki/Requirements_analysis) 😅

We need "Draft issues" 🤣🤣 I personally use OneNote for such things, but in the Web Browser, its aweful 🙈.

> Im not so sure about the fix. This seems to be a bit hacky to me. Yeah, but improves workflow while working with JabRef > The dialog now choses...

> I am not sure about the "and the user did not do any manual changes" part of the issue if it would require any special handling, When the decision...

Let's see what users will report. On the first load, I had a long respoonse time from Grobid - and could have typed something in the dialog. The subsequent runs...

I inlined a variable at [`95b50f9` (#13309)](https://github.com/JabRef/jabref/pull/13309/commits/95b50f9554146462615e208db639c4f233d2b4b1). Since the code could cause questions while reading, I added some [requirements](https://devdocs.jabref.org/requirements/) text. I think, our team agrees to have "Requirements" first and...

I added to the merge queue to keep things going. We can fix the text as a follow up.

> Thanks for the help on this issue. I wanted to ask you if it is ok if I make a Linkedin post about JabRef and this issue, Sure! Go...