I would expect the question is referring to bugs when:
- The OP has code with a bug, and doesn't know where it is.
- The OP wants to write a workaround for a function/method provided by a framework, and which contains a bug.
In the first case, if the question didn't have a bug, there would not be a question at all, except when the OP wants to optimize existing code.
In the second case, the question could be seen as a question about writing code for a specific purpose without using
Class::buggedMethod(). In such case, the question is not different from a question asking what code to write for a specific purpose, with the extra requirement of not using a specific function/method; the same type of question could be asked, for example, about PHP and how to write code that doesn't use a function which is available since PHP 5.3, when the OP's website is still using PHP 5.2.x.
What I find confusing is the description given for the tag, in its tag page.
Usually, bugs are reported into a bug- or issue-tracker. A good bug report should at least consist of a description of the environment (e.g. version number, the operating system it occured on) the minimum, quantifiable steps to reproduce the problem the expected and observed behavior.
If I am doing a bug report, in which way is that a question? If it were a meta site, a bug report would be fine; on the main site, it doesn't make much sense.
On Drupal Answers, questions that are about a module are closed as off-topic, and the user is suggested to report the bug on Drupal.org, in the issue queue for the module containing the bug; if there is already a bug report open for that module, the OP sometimes get a link to the bug report already open. This is possible because in the Help Center, in the section about the topics of the site, we explicitly said bug reports are off-topic. We consider a question like "The X module is throwing a warning about a not defined variable in a module hook; what should I do?" as off-topic, since Drupal modules are supposed not to throw PHP warnings, and there is nothing that can be done, if not fixing the module code; that is only possible by opening a issue report for that module.
In most of the cases, there is a place to report bugs for a framework, and that is the place where to report bugs.