| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| dev:bug_wrangler:faq [2018/06/01 11:02] – [Reporting Bugs on Launchpad] rjs7 | dev:bug_wrangler:faq [2024/04/22 15:02] (current) – Added section to link to UI Accessibility Checklist lhernandez |
|---|
| |
| 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. | 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. |
