Differences

This shows you the differences between two versions of the page.

--- dev:bug_wrangler:faq [2014/05/02 09:17] – Start milestone portion bshum
+++ dev:bug_wrangler:faq [2024/04/22 15:02] (current) – Added section to link to UI Accessibility Checklist lhernandez
@@ Line 15: / Line 15: @@
   * What you expected to happen.
-Frequently, users have questions regarding the different statuses and importance values assigned to bugs on Launchpad.  This page provides general definitions for the various tags that bugs get assigned as they move throughout their lifecycle.
+Frequently, users have questions regarding the different statuses and importance values assigned to bugs on Launchpad.  This page provides general definitions for the various attributes that bugs get assigned as they move throughout their lifecycle.
 ===== Bug Status Definitions =====
@@ Line 24: / Line 24: @@
   * **Invalid** - Bug is unreproducible by multiple users, other than the submitter.
   * **Won't Fix** - Bug will not be fixed.  Reasons may vary.
-  * **Confirmed** - Bug is confirmed by one or more users, other than the submitter.  Should be assigned an importance at this time, if not already set.
+  * **Confirmed** - Bug is confirmed by one or more users, other than the submitter.  Bug wrangler team members should assign an importance, if not already set.
   * **Triaged** - Bug has been acknowledged. It isn't new or confirmed, but we'll assign a real status later.
   * **In Progress** - A developer is actively working on a solution to this bug, or may be awaiting commit/release.
@@ Line 50: / Line 50: @@
 Bug reports and fixes may be assigned to the actual milestone where we plan to include the fix.  These normally only get specific milestones now when there is working code to test and there is a "pullrequest" tag applied to the bug ticket.  Occasionally, we may also add specific milestones where we intend to apply a bug ticket as a "blocker" against the release of that particular milestone, but this is reserved for only the most severe bugs.
+===== Tags =====
+Look for the "Tags" block on the right sidebar of the main [[https://bugs.launchpad.net/evergreen|bugs list]] on Launchpad. The counts only include bugs in an "open" status (excluding things like "Fix Released", "Invalid" and "Won't Fix"). You can click on a tag to search for all bugs with that tag. If you want more complex search features, go to the Advanced Search and look for the "Tags" section near the bottom.
+There are a few tags that we use in a special way:
+  * **pullrequest**: Added when code that is believed to work has been posted to the bug. If that code is proven to have problems, this tag is removed and usually replaced with "needsrepatch".
+  * **needsrepatch**: Added when code has been posted but needs work before it will be ready to review or test.
+  * **signedoff**: Added when code has been tested and approved (by adding a Git "signed-off-by" line, or by posting the equivalent in a comment).
+  * **needstest**: Added when code probably needs [[dev:contributing:qa|an automated test]] included.
+  * **needsreleasenote**: Added when code needs a [[contributing:release_notes|release note]] included.
+  * **bitesize**: Added to bugs that someone new to Evergreen development should be able to fix.
+A list of tag definitions in use as of 2020 can be seen [[dev:lp_tags|here]].
+===== Accessibility Testing Tools =====
+Use the [[accessibility:testing#ui_checklist_for_accessibility|UI Checklist for Accessibility]] to identify potential accessibility problems. Accessibility problems can often be spotted by just looking for things that seem glitchy or odd to you. If you have a few minutes, a keyboard, or an accessibility testing browser extension, you could help spot even more! Some tips and details on some optional tools are available on the Evergreen wiki under Accessibility Testing. The details on the top half of the [[accessibility:testing|Accessibility Testing]] page can be used in conjunction with this list.