Groups not visible in the vertical left bar even if correctly visibile in the groups field in each record

[koppor]

Details at https://discourse.jabref.org/t/issue-groups-not-visible-in-the-vertical-left-bar-even-if-correctly-visibile-in-the-groups-field-in-each-record/5659/2

Task:

1. Create A.bib with one entry belonging to group "A". Save. Close.
2. Create B.bib with one entry belonging to group "B". Save.
3. Import "A.bib" into "B.bib"
4. Expect: Groups "A" and "B" exist

Fix JabRef to fulfill expectiation.

Documentation:

Fix https://docs.jabref.org/advanced/main-window

1. Link back to https://docs.jabref.org/getting-started for an overview
2. Explain File -> Open vs. File -> Import

---

After the task is done

• [ ] Ask at the forum that the user should test by following https://blog.jabref.org/2025/05/31/run-pr/
• [ ] Reply to the user that import is import into current library (meaning adding) while "open" means opning a new file. JabRef can handle multiple libraries

[ennymojje]

/assign-me

[github-actions[bot]]

👋 Hey @ennymojje, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

[ryan-carpenter]

• Import "A.bib" into "B.bib"

• Expect: Groups "A" and "B" exist

What would happen in case of conflict, where "B.bib" already contains a group named "A" (which may have the same or different attributes compared group "A" in "A.bib")?

[github-actions[bot]]

⏰ Assignment Reminder

Hi @ennymojje, this is a friendly reminder about your assignment to this issue.

[!WARNING] This issue will be automatically unassigned in 11 days if there's no activity.

Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef. Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.

How to keep your assignment

If you are working on it, you can prevent automatic unassignment by:

• Submitting a draft pull request with your progress within 11 days
• Asking for the 📌 Pinned label if you need more time

We appreciate your contribution and are here to help if needed!

[koppor]

• Import "A.bib" into "B.bib"
• Expect: Groups "A" and "B" exist

What would happen in case of conflict, where "B.bib" already contains a group named "A" (which may have the same or different attributes compared group "A" in "A.bib")?

The existing group takes precedence. No group altering done.

[koppor]

We need to check: On a fresh install of JabRef, is the groups panel displayed? IMHO, it should. As well as the web search.

On Windows, one can try out with the Sandbox (https://github.com/oOblik/CustomSandbox) - or just reset the preferences to a default value.

This also refs the welcome screen @Yubo-Cao -- Maybe this somehow refs https://github.com/JabRef/jabref-issue-melting-pot/issues/1046; but I think, we cannot say: CS is always with groups and humanities not. I think, all of them should see the features. Maybe, we need following:

1. Do not display groups on start
2. If a library has groups, automatically show groups panel
3. Automatically close groups panel if there are no gropus
4. Add a preference for auto show and high (enabled as default)

[Siedlerchr]

I would show groups on first startup only (default preference) and then let the user hide or show. Nothing else. Any other assumption is confusing, especially when you have multiple libraries. As a User I would not expect that my groups panel is closing or showing randomly. Even if there is a preference.

[github-actions[bot]]

📋 Assignment Update

Hi @xIshanSandhux, due to inactivity, you have been unassigned from this issue.

Next steps

If you still want to work on this:

• Submit a pull request showing your current state. You will be automatically assigned again.
• Ask a maintainer to assign you again.

[omkarrr2533]

/assign-me

[koppor]

/assign @omkarrr2533

[jabref-machine]

👋 Hey @omkarrr2533, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.

In case you encounter failing tests during development, please check our developer FAQs!

Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.

Happy coding! 🚀

[koppor]

I have no clue why GitHub actions did not trigger "on issue comment" for https://github.com/JabRef/jabref/issues/13684#issuecomment-3621590626

[omkarrr2533]

Thank you, Mr. Koppor. Yesterday I tried to assign the issue to myself using /assign-me, but it didn’t seem to trigger the action. I appreciate you assigning it to me directly.

[jabref-machine]

⚠️ Issue Already Assigned

Hi @omkarrr2533, this issue is currently assigned to @omkarrr2533.

[!NOTE] If no progress is made within 21 days, the issue will be automatically unassigned.

Options for contributors

• Wait for availability: The issue may become available if auto-unassigned
• Collaborate: You can ask the assignee if they want help
• Maintainer assistance: A maintainer can add you as co-assignee if appropriate