When adding a "required-tag" to a meta question, allow only one of the four required-tags to be used per single question.
No change to which or how many non-required tags can be used in addition to the chosen required-tag.
While this isn't a big issue, the change would make the tags more useful and logical, and perhaps ease any confusion less seasoned users may have from wondering which tag should be used on their question.
eg In one question, they want a discussion and some support with the bug they found.
Just the "bug" tag is required here.
(Note: Enforcing non-required tags is a debate for a separate proposal).
None of the 4 required-tags compliment each other, nor can they logically be used in relation with each other.
They each have a separate meaning and definition, and their different definitions, which denote what a question is about, do not successfully mould together in a single question to form a logical new meaning - they simply clash to form confusion.
Using any of them together in one question dilutes their individual meaning, and doesn't effectively summarise what the question is about.
- "I just want to discuss this.."
- "I want this feature implementing.."
Choosing one required-tag only is simple
It's not hard to choose only one of the 4 tags for any given scenario.
- bug - User is reporting a bug. There is no feature request, they're not asking for support on a site feature or function, and discussions will happen without the discussion tag
- feature-request - User has an idea for something new or a change to something current. There is no bug, nor any request for support, and discussions will happen without the discussion tag
- support - User is asking for support on a site feature/function. There is no bug, nor a feature request, and discussions will happen without the discussion tag
- discussion - When it is not one of the above 3. User is not sure, tags it as discussion to find out if something is a bug or not, or if they are using something incorrectly, or to discuss a potential feature request for feedback before proposing it, or anything else
There is no logical reason, or requirement, to use any of these required-tags in the same single question.
Benefits from implementing this
- Re-tagging - With this feature in place, there will only be one possible correct required-tag, making re-tagging easier
- Category - Having only one "category" per question defines the question's requirements more clearly
- Searching - This change would mean search results for a given required-tag would be only for that tag as user wanted (ie not search for discussions and get feature-request as well