You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Checked with the latest development build (copy version output from About dialog)
I made a backup of my libraries before testing the latest development version.
I have tested the latest development version and the problem persists
Steps to reproduce the behaviour
Create a group "Group 1"
Create a subgroup "Subgroup"
Add an entry into "Group 1" -> "Subgroup"
Create a group "Group 2"
Create a subgroup "Subgroup" (aka the same name for the subgroup from Group 1)
The entry added in step 3 now shows up in the subgroup of Group 2. Although the names are the same, the subgroup is within a different group and so it shouldn't be pulling from another groups content.
Appendix
No response
The text was updated successfully, but these errors were encountered:
Thank you for your report. This problem is known, is a limitation of the current folder architecture, would require a major rewrite and has been extensively debated in the past, as it can enhance certain workflows in a very positive way, but also can put a burden on other workflows.
The more I think about it, this very characteristic might be the blurring line between what people usually associate with folders and tags and I think fixing this should only be implemented, once JabRef has separated their "tags" (= keywords) feature from the groups feature in the UI.
JabRef version
5.10 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)
Steps to reproduce the behaviour
The entry added in step 3 now shows up in the subgroup of Group 2. Although the names are the same, the subgroup is within a different group and so it shouldn't be pulling from another groups content.
Appendix
No response
The text was updated successfully, but these errors were encountered: