Consider child tags in required tags

Currently, it is possible to set required tags for a category. For example, here on meta it lists as required tags one of: bug, feature-request, discussion or support.

For meta, this works pretty well, but this is relatively limiting for communities where one wants one aspect as a required tag, but the specific tags are many. For example, if we would consider a community related to programming languages, we may want to express that specifying a programming language as a tag is required, but we don't want to specify all possible programming languages as that would be quite a long list in the UI.

I think it would make sense to allow putting the requirement on a hierarchical level and accepting child tags as well. Then in my example, programming language would be the required tag, and all child tags of programming language would satisfy the requirement. That way we could enforce that some programming language is selected, without listing all possible programming languages. New languages can just be added as children of the programming language tag to automatically be valid candidates for the required tag. An unknown-language tag or something could be added as fallback in case new languages are added (or directly adding the programming language tag).

is a duplicate

This question has been asked before and has already been answered. It should be marked as a duplicate.

Please enter the URL of the proposed duplicate in the details field below.

not constructive

This question cannot be answered in a way that is helpful to anyone. It's not possible to learn something from possible answers, except for the solution for the specific problem of the asker.

Communities

Consider child tags in required tags

1 comment thread

0 answers