Last updated May 3, 2015.
On this page:
- Skills needed
- Detailed steps
- Background and reference information
- Next steps: moving beyond this task
- Notes for reviewers
To get help completing this task, see the Getting help completing your task page.
Take an existing issue that has been reported on Drupal Core, a contributed module or contributed theme, and either close the issue, move it to another project, ask for more information, or note that it has been verified as a valid issue. This is known in the Drupal community as "issue triage".
Some familiarity with the contributed module or theme the issue was reported on. Ability to read and write understandably in English.
- If at any moment, you come across an open issue related to an old (unsupported) version of Drupal, change its status to "closed (won't fix)" with the following message: "This version of [module name] is not supported anymore. The issue is closed for this reason. Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable." (this message comes from Templates for issue status transitions).
- You must have a Drupal site to test on, and it is recommended that you setup a test environment or use simplytest.me. It is important to use a test environment so you can reproduce the issue on an up-to-date Drupal site.
- Find issues for a project.
- Find an open issue that is of category "bug report", status "active", and in the Drupal version you are using (Drupal 7.x, 6.x, etc.). Choose one that doesn't have any comments (Replies) on it yet, or only a few. If there aren't any that fit, choose another project to work with.
- Click on the issue title to open the issue page. Read through the issue. If one of the project's maintainers has already replied (or if they were the one who reported it), find another issue to work on.
- Follow the detailed steps on the Contributor task: Identify duplicate issues page.
- If the issue is not a duplicate, your goal now is to decide whether or not the issue is valid. You might need to install the module or theme on your test site in order to follow the steps reported in the issue. (If it is an issue with Drupal core, it's recommended to start from a fresh installation.) Here are some things to check, and responses (see the Background section just below for some additional instructions on how to edit issues):
- If you cannot understand what the issue says, or there are steps missing (e.g., the issue report just says "this doesn't work at all" without any details), then change the issue status to "postponed (maintainer needs more information)", with a comment explaining what information you need. You can also add the "Needs steps to reproduce" issue tag to the issue.
- If you have tried the steps and cannot reproduce the reported buggy result, change the issue status to "postponed (maintainer needs more information)", with a comment explaining what you did and what you saw. You can also add the "Needs steps to reproduce" issue tag to the issue.
- If you believe the bug is valid, but it is really due to a bug in a different module or theme, then change the Project of the issue to the other module/theme, with a comment explaining why you are making the change. (For Drupal core, any issue that requires a contributed module or theme to reproduce should be moved to the queue for that project so that the project maintainer can review the issue and determine the cause of the bug.)
- If it's an old issue, you cannot reproduce it, and there has been a new release (or several) of the module/theme since it was reported, and you believe that the issue was fixed due to those new releases, change the status to "fixed" and explain that.
- If you have tried the steps and can confirm what the original reporter saw, add a comment to the issue saying that you have verified that it is a bug. Add more information if you think it would be useful, such as a screen shot of the configuration and the result, or a description of an additional step you did that caused the bug to appear. (Also see the instructions for how to document the steps to reproduce an issue.
- Verify which version(s) of Drupal the issue is relevant for, beginning with the latest development version, currently Drupal 8 and tag for backport to any other versions it is known to exist in.
- Finally, check the issue tags, priority, category, and component to make sure they are appropriate. See links below for explanations.
Background and reference information
- In the steps above, if it says to change the status, category, etc. of an issue, the way to do that is to scroll to the bottom of the issue. You will see a Comment form. Just above the comment form, you have the ability to change the issue title, status, category, etc. Below the comment form, you have the ability to change the Tags (you will need to click the Tags link to add tags). Whenever you make changes, add a comment explaining why, and click Save to make the changes.
- Explanation of issue status settings
- List of templates for the comment to leave when you change an issue status.
- List of issue categories
- List of priority levels for issues
- Guidelines for issue tags
Next steps: moving beyond this task
- Document the exact steps to reproduce the issue.
- If you are a programmer or themer, fix an issue that you or someone else has verified.
Notes for reviewers
Specific to this task:
- The STR should be in a numbered list.
- Ideally, the STR should start from (e.g.) "Install Drupal 8.x with the standard profile."
- If the participant cannot reproduce the issue, he/she should leave a comment on the issue listing the STR he tried and add that those steps do not reproduce it.