-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature request: add "no ranking" subgroup automatically #10264
Comments
very low priority, as a workaround exists. |
Hello, Can you assign this issue to me? I already add this feature. |
👋 Hey @lych2001, it looks like you're interested in working on this issue! 🎉 If you'd like to take on this issue, please use the command |
/assign-me |
👋 Hey @lych2001, 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. 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! 🚀 ⏳ Please note, you will be automatically unassigned if the issue isn't closed within 30 days (by 22 November 2024). A maintainer can also add the "📌 Pinned"" label to prevent automatic unassignment. |
When creating a ranking group based on the "ranking" keyword like this
there is no subgroup created for entries without ranking. Since it's useful to easily find the entries without rank, having a subgroup for this is nice.
As discussed here https://discourse.jabref.org/t/groups-read-status-and-ranking/3953/5
there is a workaround but I would like to request a "no ranking" subgroup that is created automatically, next to the subgroups "rank1" -> "rank5"
Thank you
The text was updated successfully, but these errors were encountered: