How to Triage Issues

Initial Labels

All issues are labeled A-needs-triaging when they are created. GitHub Actions will then auto label the issue based on information provided by the user.

Automatic Actions

For the most common responses, we have several labels that will take automatic actions.

• It’s a general request for help: label it I-question (immediately auto-closes the issue with a comment and links to places to get help)
• Not enough info to try to reproduce problem because template not filled out: label it J-issue-template (auto-closes in 14 days if no response)
• Need to see logs to understand what is going on: label it J-logging (auto-closes in 14 days if no response)
• You need to clarify something before you can reproduce it: Comment with the question, then label it J-awaiting answer (auto-closes in 14 days if no response)

Evaluating Issue

If you have enough information to reproduce the issue or evaluate the request: 1. Make sure the auto-applied labels are correct with respect to OS, Language, Component and update as necessary 2. Comment with any findings about the bug and options for addressing 3. If it is a real bug or valid feature request and you don’t have time to immediately address it, label it R-help wanted and add an E label for how easy you think it would be to address it 4. Open issues should have one of 3 tags at all times (A - Selenium takes action, J - Reporter takes action, R - someone else takes action)

Label Explanation

• A: Something that a member of the Selenium project need to take action on
• B: What component(s) of the project the issue relates to
• C: What language(s) the issue relates to
• D: The Issue is specific to a browser
• E: How hard the issue is to address
• G: The issue needs to be addressed by another project (these auto-close)
• I: What kind of Issue it is
• J: Action needs to be taken by the reporter
• OS: Specific to a particular OS
• P: Specific to Pull Requests not Issues
• R: Waiting on something outside the control of Reporter and Selenium