Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Goal:
Evaluate an issue in the Documentation project. Decide whether it is valid, and respond appropriately. Correct and clean up the issue field values.
Skills required:
Detailed steps:
- Set up prerequisites: Log in from Common Prerequisites for Contributors.
- Browse through the Documentation issue list, and find an issue to work on. Suggestions:
- The default sort is by most recent issue first, so find something near the top of the list to start with; later on you can come back and work on some older issues that are still unresolved.
- An issue that has zero Replies (comments) indicates it is new and no one has responded to it yet.
- Click the title of the issue you choose, which will take you to the issue page.
- Read the issue and any comments it has, to understand what the issue is about. You will probably also need to read or skim the documentation page the issue is about.
- Triage the issue. The goal of this step is to figure out whether or not the issue contains sufficient details to act on, is relevant, and belongs in the Documentation project. (See Creating or updating an issue report for the mechanics of how to update an issue.) Triage evaluation:
- If the issue is actually a support question... See the Handle a support request in an issue task writeup.
- If the issue is obsolete or isn't valid... Change the issue Status to "Closed (outdated)", "Closed (cannot reproduce)", or one of the other "Closed" status values, and add a comment explaining why. See Templates for issue status changes for suggested comments, and Issue Status field for a detailed explanation of the status values.
- Search the Documentation issue list for keywords related to the issue, to see if it is a duplicate of another issue. If it is a duplicate... See the Identify duplicate issues task writeup.
- Read through Selecting the Project for a documentation issue, and see if the issue is filed in the wrong project. If the issue is in the wrong project (including issues about spam)... Change the issue's Project field to the correct project, and add a comment explaining why.
- If the issue does not have enough detail... Change the Status to "postponed (maintainer needs more info)" and add a comment explaining what additional information you would need to be able to act on the issue.
- If none of these apply... This is a valid Documentation issue, so continue with the next step.
- See if the issue needs to be cleaned up. If so, fix values and add a comment about why. Common things to fix:
- Issue title and summary unclear or incomplete -- see Creating or updating an issue report for suggestions, and use the Documentation issue summary template
- Issue component or status field values incorrect
