Lines Matching refs:bug

10 Introduction - Achieving consistency in how we deal with bug reports
16 understanding of what a particular bug state actually means and what to expect
21 as the overall goal is to make it easier to work with and understand the bug
31 Furthermore, some of the metadata in the bug tracker, such as what labels we
42 See :doc:`HowToSubmitABug` on further details on how to submit good bug reports.
45 to the bug to provide extra information to make the bug easier to discover, such
46 as a label for the part of the project the bug pertains to.
58 The goal of triaging a bug is to make sure a newly reported bug ends up in a
65 * Can you reproduce the bug from the details in the report?
69 * Is it related to an already reported bug?
77 * When able to do so, please add the appropriate labels to classify the bug,
88 * Add the ``good first issue`` label if you think this would be a good bug to
100 Please remember to assign the bug to yourself if you're actively working on
102 unassign a bug by removing the person from the ``Assignees`` field.
119   * If the reported behavior is not a bug, it is appropriate to close the issue
120     with a comment explaining why you believe it is not a bug, and adding the
123   * If the bug duplicates another issue, close it as a duplicate by adding the
130   * If there is a specific and plausible reason to think that a given bug is
131     otherwise inapplicable or obsolete. One example is an open bug that doesn't
133     (e.g. not reproducible). It is fine to close such a bug, adding with the
135     reopen the bug with more information if it's still reproducible for them.