fixed issue 298

[grotepfn]

fixed issue 298

• Change in CHANGELOG.md described
• Tests created for changes
• Screenshots added (for bigger UI changes)
• Manually tested changed features in running JabRef
• Check documentation status (Issue created for outdated help page at help.jabref.org?)

Credit (for an exercise):
Florian Grotepaß

[tobiasdiez]

Please change the capitalization in the changelog to proper English sentence case. Apart from this, +1 for merge.

[Siedlerchr]

For future PRs you should specify a short title describing the content of the PR.
(github takes the title from the first line of the commit)
In the body of the PR you should add Fixes #xxx then github will close the corresponding issue (if it's in the main repo) automatically

[lenhard]

Thanks for the contribution. For the record, this is the issue we are talking about: JabRef#298

Next time, just use the link so that github can make the connection.

I am merging now.

[lenhard]

After merging, I realized that this PR did not build on master. The branch this built on will eventually also be merged into master, which will get the change in. Nevertheless, with an issue like this there is no reason to base on a branch different from master.

Next time, please make sure that you base on master.

[koppor]

The changelog should be

... [koppor#298](https://github.com/koppor/jabref/issues/298)

No space and koppor in front. We will fix that in master as soon as comment-tab is merged :)

Nevertheless thank you for the quick action taken @grotepfn. Hope to see another issue fixed.