Changes to issue assignment: Difference between revisions
From MoodleDocs
(Created page with "==Automatic assignment prior to Moodle 2.5== Previously, the [http://tracker.moodle.org Moodle Tracker system] required each component to have an automatic assignee. This meant ...") |
(This page will not be migrated to new devdocs) |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{Template:WillNotMigrate}} | |||
==Automatic assignment prior to May 2013== | |||
* Having a developer assigned to an issue gave an impression that someone was working on the issue. Most of the time, developers are working on only a small number of bugs in the | Previously, the [http://tracker.moodle.org Moodle Tracker system] required each component to have an automatic assignee. This meant that each reported issue was assigned to a real developer (or to an artificial user). While this did allow issues to have someone's eyes on them when they were reported, it did have some downsides. | ||
* If an issue already has an assignee, | |||
* Having a developer assigned to an issue gave an impression that someone was working on the issue. Most of the time, developers are working on only a small number of bugs in the Tracker, so this was potentially sending a false message. | |||
* If an issue already has an assignee, other developers may be reluctant to volunteer to take on an issue. We want to encourage developers to be involved in resolving issues without impediments. | |||
==The new approach== | ==The new approach== | ||
| Line 10: | Line 12: | ||
Issues are no longer automatically assigned to developers as they are reported. Developers should only assign an issue to themselves when they have a definite intention to complete the issue. | Issues are no longer automatically assigned to developers as they are reported. Developers should only assign an issue to themselves when they have a definite intention to complete the issue. | ||
Components are automatically watched by users and most newly created issues are [[Bug triage|triaged]]. | |||
In order to create a truer representation of issues and allow other developers to become involved, developers assigned to issues have the option to unassign themselves if they have no intention on working on the issue immediately. When doing so, they may use the following statement. | In order to create a truer representation of issues and allow other developers to become involved, developers assigned to issues have the option to unassign themselves if they have no intention on working on the issue immediately. When doing so, they may use the following statement. | ||
Latest revision as of 10:21, 26 April 2022
| Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable. |
Automatic assignment prior to May 2013
Previously, the Moodle Tracker system required each component to have an automatic assignee. This meant that each reported issue was assigned to a real developer (or to an artificial user). While this did allow issues to have someone's eyes on them when they were reported, it did have some downsides.
- Having a developer assigned to an issue gave an impression that someone was working on the issue. Most of the time, developers are working on only a small number of bugs in the Tracker, so this was potentially sending a false message.
- If an issue already has an assignee, other developers may be reluctant to volunteer to take on an issue. We want to encourage developers to be involved in resolving issues without impediments.
The new approach
Issues are no longer automatically assigned to developers as they are reported. Developers should only assign an issue to themselves when they have a definite intention to complete the issue.
Components are automatically watched by users and most newly created issues are triaged.
In order to create a truer representation of issues and allow other developers to become involved, developers assigned to issues have the option to unassign themselves if they have no intention on working on the issue immediately. When doing so, they may use the following statement.
- This issue was assigned to me automatically, however I will not be able to work on this issue in the immediate future. In order to create a truer sense of the state of this issue and to allow other developers to have chance to become involved, I am removing myself as the assignee of this issue.
- For more information, see https://docs.moodle.org/dev/Changes_to_issue_assignment
