Skip to content

Commit

Permalink
Merge pull request #1064 from hamidayubdev/patch-1
Browse files Browse the repository at this point in the history
Update triage.md
  • Loading branch information
andrewnicols authored Jun 30, 2024
2 parents ce81163 + 1170e85 commit c25bf61
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion general/development/process/triage.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ First of all, identify the issues that should be closed or placed under investig
- **Does the problem seem rational?** If not, then the problem may simply be a misunderstanding on the part of the reporter. It might be a problem exclusive to the reporter's server set-up. If you can replicate the problem quickly, do so. If you can't replicate the problem, ask the reporter to attempt to replicate the problem on [https://sandbox.moodledemo.net/](https://sandbox.moodledemo.net/). If the problem seems persistent but strange, consider asking a developer with experience working in the area to consider the problem and determine if it could be a real problem.
- **Can the problem be replicated?** If not, or information on the issue is insufficient, ask the reporter to add error messages, screenshots, environment information (OS, web server, browser) and exact replication instructions

As a result of this initial screening, up to 20% of new issues may be closed. When closing the issues make sure to set the correct resolution and write a polite comment with explanation, refer to the templates below. If you have doubts, ask the questions and always add the [`triaging_in_progress`](https://tracker.moodle.org/issues/?jql=labels%20in%20%28triaging_in_progress%29) label. Subscribe to the [My old issues in triage](https://tracker.moodle.org/issues/?jql=labels%20in%20%28triaging_in_progress%29%20AND%20project%20%3D%20MDL%20AND%20resolution%20%3D%20Unresolved%20AND%20Participants%20%3D%20currentUser%28%29%20AND%20updatedDate%20%3C%20-30d) filter and you will receive notifications after 30 days of inactivity on such issues. See [Tracker tips](../tracker/tips) about how to subscribe to filters. Often reporters never follows up on their own issues and this is a good way to find such issues. Ping the reporter again or make a final decision about closing.
As a result of this initial screening, up to 20% of new issues may be closed. When closing the issues make sure to set the correct resolution and write a polite comment with explanation, refer to the templates below. If you have doubts, ask the questions and always add the [`triaging_in_progress`](https://tracker.moodle.org/issues/?jql=labels%20in%20%28triaging_in_progress%29) label. Subscribe to the [My old issues in triage](https://tracker.moodle.org/issues/?jql=labels%20in%20%28triaging_in_progress%29%20AND%20project%20%3D%20MDL%20AND%20resolution%20%3D%20Unresolved%20AND%20Participants%20%3D%20currentUser%28%29%20AND%20updatedDate%20%3C%20-30d) filter and you will receive notifications after 30 days of inactivity on such issues. See [Tracker tips](../tracker/tips) about how to subscribe to filters. Often reporters never follow up on their own issues and this is a good way to find such issues. Ping the reporter again or make a final decision about closing.

### Confirming the issue

Expand Down

0 comments on commit c25bf61

Please sign in to comment.