GitHub Community
Provide an equivalent to "labels" #19
-
WhyAt Gatsby we've made heavy use of different labels for displaying the In moving questions and feature requests over to Discussions I've already seen that a lack of overview and ability to filter things will be a problem in the future. Thus we're in need of an equivalent to "labels". HowSince Discussions isn't something completely new, there's enough previous art to draw inspiration from:
|
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 27 replies
-
|
@becca Hi! Can you give an initial comment, e.g. if this is tracked internally or questions are still open/to be discussed. As I'm not sure what 👀 means :) Appreciate any feedback, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
We're currently investigating having a shared system of Regarding the other mentioned features:
|
Beta Was this translation helpful? Give feedback.
-
That would be ideal/best solution I think! Keeps the organization of those coherent and when transferring an issue to a discussion they can be transferred with it.
Yeah, more or less an organizational thing:
It couldn't be a replacement for tags though as e.g. we have 100 of them and one shouldn't need to scroll through 100 subcategories 😅 Are there any behaviours you would expect subcategories to have? Subcategories could inherit the settings of the parent by default, e.g. when parent has setting that answered can be marked as answered the child categories would automatically also have that (but could be overriden)
As already mentioned above we'd be really happy about a shared system!
In the past I experienced prefixes like this (in forum software like https://invisioncommunity.com/4guides/how-to-use-ips-community-suite/content-discovery/content-tags-and-prefixes-r72/):
Prefix is definitely a niche thing though, I don't expect many people to know that UX pattern, especially compared to labels/tags. In the other discussion we talked about having a third state like "resolved" in addition to unanswered/answered. With prefixes you can add such toggles individually to each category. Let's say we have a category for feature requests, then one could add two prefixes called unresolved/resolved. By default unresolved gets applied and maintainers could change the prefix to resolved -- or it happens automatically. That's at least behavior in forum softwares. But as I said, labels can solve most things and are probably more common. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for expanding on your request. This is extremely helpful and I will keep you posted once we have labels available in Discussions. It's on our roadmap as we know this is a critical feature for maintainers to more thoroughly organize this space. For the "states" you mentioned- would you expect/need those as labels or perhaps believe those to be more of a feature that's available at the Category level (Q&A categories can have answerable/resolved states, for example)? |
Beta Was this translation helpful? Give feedback.
-
I'd say labels could serve the need of states, but having states like "Q&A categories can have answerable/resolved states, for example" would be complimentary for me. So it would certainly be a nice to have but labels are more important. |
Beta Was this translation helpful? Give feedback.
-
|
Noted! Thank you for that additional context regarding the prioritization of labels vs additional states at the category level. 🙇 |
Beta Was this translation helpful? Give feedback.
-
|
Would like second this request for labels (and or similar organizing features) I would hope to have for Discussions similar sorting features like for Issues: by author, by label, most recent, and maybe by Topic. A topic-label could be used in a drop down to select filter by "main topics" - these would probably have to be set by an admin. |
Beta Was this translation helpful? Give feedback.
-
|
We are aware of this feedback and are tracking the request internally. We'll keep you posted on the plan for this coming to Discussions! |
Beta Was this translation helpful? Give feedback.
-
|
Well this is promising: https://twitter.com/natfriedman/status/1379847199639564288?s=21 |
Beta Was this translation helpful? Give feedback.
-
|
We (@craftcms) have been looking into migrating feature request from Issues over to Discussions, but the lack of labels has us reconsidering it. Our main repo, craftcms/cms has over 50 labels, most of which are for specific features of the product, and we rely on our ability to filter ideas by feature. Subcategories wouldn’t work for us because there are cases where issues have 2+ labels, such as ux + authoring or ux + system administration. Ideally discussions would be able to use the same list of labels that issues (and pull requests) use. We also wouldn’t want users to have to choose which labels to add to their discussions; they should just have to select from the discussion categories, and get to writing. Let us be the ones to pick the appropriate labels, as we do with issues. |
Beta Was this translation helpful? Give feedback.
-
|
In the same boat with Microsoft Project Reunion, we have about 7 feature areas and need to easily be able to view "Ideas"/etc per feature area (like Notifications, WinUI, Packaging, etc). |
Beta Was this translation helpful? Give feedback.
-
Labels Private Beta Available 🚀Thank you for all of the feedback on labels! I'm excited to announce that we have a private beta available, where you can use your repository labels on Discussions as well. If you'd like to be included in the beta, please share the repository you'd like to be flagged in below. For now, this private beta is limited to the first 15 repositories that respond.
|
Beta Was this translation helpful? Give feedback.
-
|
@natowi @Andre601 your repos have been flagged in! @brandonkelly @jopdeklein thanks for reporting! we'll look into these :) |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu we would love love love labels on storybookjs/storybook . Their existence is well timed as we have been considering moving back to issues because of a lack of labels/organization of discussions. |
Beta Was this translation helpful? Give feedback.
-
|
@zol enabled! glad we made it in the nick of time :) |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu I'd love to have it in my repo as well. harshraj22/DeepLearning. Please 😄 |
Beta Was this translation helpful? Give feedback.
-
|
We'd love to test it out under |
Beta Was this translation helpful? Give feedback.
-
Labels available as public beta! 🚀Thanks for all of the helpful feedback and private beta testing of labels. We've now rolled out labelling capabilities to all repositories with Discussions. Happy labelling and feel free to drop any feedback in this thread. |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu is there an announcement I can share? <3 |
Beta Was this translation helpful? Give feedback.
-
|
Here's the official changelog on GitHub blog: https://github.blog/changelog/2021-05-18-github-discussions-labels-and-announcements-category-format/ And I also made a more informal announcement here: #3979 |
Beta Was this translation helpful? Give feedback.
-
|
What are the chances of getting this feature in team discussions? Or is that a different feature that I should be asking about somewhere else? |
Beta Was this translation helpful? Give feedback.
-
|
@aviflax Unfortunately, it's a different feature entirely. You can share feedback about it here https://support.github.com/contact/feedback |
Beta Was this translation helpful? Give feedback.
-
|
Got it — thank you! |
Beta Was this translation helpful? Give feedback.
Labels available as public beta! 🚀
Thanks for all of the helpful feedback and private beta testing of labels. We've now rolled out labelling capabilities to all repositories with Discussions. Happy labelling and feel free to drop any feedback in this thread.