Issues without matching labels
jayvdb opened this issue · comments
yoda is designed around labels, that match established patterns.
If an issue doesnt have all the appropriate labels, it falls through the cracks.
So a tool is needed to find them and add the missing labels.
Sorry for not responding earlier. Somehow E-mail notifications went to my spam folder. Will consider and respond soon.
Yes, a "label convention checker" tool is a good idea. We need to consider how to describe the policing to be done.
For example, we require strictly that all issues have a "T# - <type text" label. But only some types strictly require a severity/priority. Need to think how to express this in a good way.
(the actual checking is probably not a big deal).
Only then, the workaround is to export all (open) issues to excel and filter/check there, or use GitHub native issue searching. Of course the searching cannot easily find e.g. issues without a "T# - " label set...
Will put as enhancement and priority high.
I have not forgotten about this... The work-around I used for now is to brutely export into Excel. The Yoda exporter will further complain if e.g. there are multiple where by convention there should only be one. One example could be several "T# - <type text" labels at the same time....