Revision as of 01:11, 21 July 2008 by David Somers-Harris (talk | contribs) (Logging new issues or improvements: fixed section header)

Jump to: navigation, search

Note: You are currently viewing documentation for Moodle 2.3. Up-to-date documentation for the latest stable version is available here: Tracker.

Tracker.jpg is Moodle's Issue Tracker MoodleOrg link.JPG

Issue tracking is an important part of a continuous quality control process. It involves the reporting of problems (bugs), ideas for improvement and new features. Unlike most proprietary software programs, Moodle issue reporting and tracking information is open to everyone. Moodle's issue tracking system is called Moodle Tracker. We welcome your requests for new features, improvements, or even constructive criticism of existing features.

The beauty of open source is that anyone can participate and help to create a better product for all of us to enjoy. Please help us by using Moodle Tracker!


Logging in to Tracker

  • If you're a new Tracker user, create a user account here. It is strongly suggested your Tracker username is the same name you use at
  • If you've forgotten your password, go here and select 'forgot password' which is just under the 'log in' button. Follow the prompts.

Summary: How to report a bug, improvement, or new feature request

NB See the section 'Tracker fields' below for a full description of every field.

  • Login to Tracker
  • Select "Create New Issue" from the menu under the Moodle Tracker logo
  • From the dropdown menu select the "Issue type": Bug, New Feature, Task or Improvement
  • You will see a series of dropdown and free text fields. Complete as many as you can. Some fields are required while others are optional.
  • Press the 'Create' button at the bottom of the page to create the bug.

How to write a good Tracker entry

A good report will include:

  • Summary (describe the issue in 1 or 2 sentences)
  • Description (a concise yet complete summary of the problem or improvement)
  • Steps to Reproduce: A detailed, easy-to-follow sequence of steps a developer can follow to reproduce the problem. If possible, provide a URL so a developer can see the problem with one click.
  • Actual Results: What the application did after performing the above steps.
  • Expected Results: What the application should have done, were the bug not present. Provide as much detail as possible. Your expectation might mean that help instructions need to be improved or interface changed.

If possible, include additional information that may be helpful to the developer:

  • Moodle version (there is a dropdown menu on the top of the form, if that does not have what you want, add it in the description)
  • If you have an error message, or information in your PHP or web server logs, copy and paste it into the bug report. If you can, turn on "debug" in your Admin configuration page and reproduce the problem to get the best possible error message.
  • Screen shots are very helpful for some bugs, but please write a textual description of the problem too.
  • Provide details about your setup including operating system, database, etc. If you run out of room in the environment section, add more detail in the description. The full set of information that might be relevant is:
    • Server operating system type and version number
    • Web server type and version number
    • PHP version number (and whether you are using an accelerator)
    • Database type and version number
    • Client-side operating system type and version number
    • Web browser type and version number
  • You don't need to provide details all the time. For example, for a layout rendering problem, you need to give only the client-side OS and browser info, and if it is a server-side problem you only need to describe the setup there. Use your judgment. Here are some examples:
    • I see this bug with the latest Moodle HEAD running on PHP5.1.2/Apache 2.2.3 on Linux. My database is Postgres 8.1.
    • This rendering problem happens using Internet Explorer 6.0 on Windows XP.

In summary stick with facts and present enough facts so someone else can duplicate the problem.

Here are some examples of good bug reports: MDL-6030, MDL-5688, MDL-12505

"What’s the hardest thing about a bug report?" Most of the time fixing the problem is the easy part, the hard part is reproducing the bug. The developer needs to see how it is broke to be able to fix it. If they can't reproduce the error you can be sure they won't be able to fix it!

Good bug reports contain as much detail as possible and are specific. Don't generalise or leap to conclusions.

For example, a bug report that only says "The RSS feed doesn’t support UTF-8" is not helpful. The developer knows that UTF-8 and RSS feeds are compatible. The developer has no idea of what the person sees and why they reported this bug. In this case more time and effort needs to be expended to determine the problem.

Consider a bug report which says that the descriptions for the specific RSS feed XYZ@abc shows unrecognisable characters rather than expected characters.

Tracker process

Logging new issues or improvements

Anyone with a Tracker account can log issues. See instructions above for writing good quality bug reports. It is important that you search Tracker to determine if your problem or suggestion for improvement has already been reported. If it has you are encouraged to add more information (use the "comment" function), vote for the issue, or watch it (more on this later).

You will receive an email when you log a new bug or make updates to bugs you've reported. You'll also receive notification when updates are made to bugs you're watching.

You can monitor, or watch issues reported by others. To do this, open the issue, then select "Watch it" from the left hand navigation panel. To add others to the watchlist for your issue, open the issue, select the option "Watching" from the left hand navigation panel. These people will receive email notification when the issue is updated.

Tracker provides a facility to Link issues. Any user logged onto Tracker may link issues. Multiple link types are defined in the system; you will be required to select one when linking bugs. See [insert section name] for detailed list of link types.

Vote for bugs you want to see addressed in Moodle. Any user can vote. To vote for a specific bug, browse to the bug, then select "Vote for it" from the left-hand navigation panel. Developers may consider the number of votes a bug has when weighing the merits of two or more bugs.

The Tracker Dashboard is flexible and customisable depending on your area of interest. For instructions on configuring the Tracker dashboard click here.

The Tracker Issue Navigator is used to find and filter bugs. For instructions on configuring the Issue Navigator click here.

Tracker's Quick Search function is explained here

Resolving issues

(this section should be reviewed)

Issues are resolved in Tracker to show that they've been actioned. Only Moodle core developers and testers are permitted to change the status of bugs in Tracker to "resolved" or "closed".

This is the general process a developer will follow when actioning a Tracker issue:

  1. Issues are automatically assigned at the time they're created based on component type; they may be reassigned by developers or Component Leads.
  2. Developers fix, modify or add code and check into CVS. The Tracker issue number is included which automatically links the CVS change to Tracker.
  3. Patches are attached to Tracker issues so that they may be verified and possibly included in CVS.
  4. Appropriate comments should be added in Tracker describing the fix. The bug's status is changed to Resolved.
  5. The developer should indicate which version of Moodle the change will be included in using the Fix Version/s. You should use this to indicate which branch(es) you checked the fix into (example below).
  6. The only exception to not moving a bug to Resolved is if a developer believes there is no value in testing the resolved issue, in which case the bug status can be changed to Closed.

Testing issues

All users are encouraged to be active participants when it comes to testing Moodle. Anyone with a Tracker user account can log, view, comment on, vote, and watch bugs. If you find bugs or problems, have ideas for improvements, or want additional functionality added to Moodle, please log a bug in Tracker.

We've formalised a group of testers in Tracker who are responsible for verifying the accuracy of changes made by developers. These testers have responsibilities and authority in Tracker beyond that of standard users. Testers normally have a good understanding of Moodle, and are active in the Moodle community. Obviously testers should have the skills and knowledge to sufficiently test the issue - experience is important - but don't forget there are others in the Moodle community who may be willing to lend a hand. If you are interested in becoming a member of the Moodle Testing team, make yourself known by logging a request through Tracker. We'd love to have you join the team! Log your request at the Sites Tracker project.

Testing a bug in Tracker

NB This is the process members of the moodle-testers group should follow to move bugs from 'resolved' to 'closed'.

  • Testers test bugs with Status=Resolved. Global filters have been created based on upcoming releases (eg 1.7 Resolved) to make identification simple.
  • Use the QA Assignee field to identify yourself as the tester of a particular bug.
  • It's a good idea to add your name to the watch list for all bugs you test. (see "Tracker watch list", below.)
  • If the bug passes testing, close the bug using the "Close Issue" button. You must add appropriate comments describing your testing methods, any issues that were found, etc.
  • If the bug fails testing or if you feel the fix is incomplete, reopen the bug using the "Reopen Issue" button. Ensure the bug is assigned to the correct developer. Work with the developer to find a mutually agreeable resolution to the bug.
  • A release will be deemed ready when all bugs fixed for a particular version have been closed.
  • All resolved bugs should be tested. Bugs with a resolution code of "fixed" represent bugs where code has been updated, and probably represent more of a challenge than bugs with resoluton codes of duplicate, won't fix, and not a bug, and can't reproduce. Please ensure bugs have been closed with a proper resolution code. Unfortunately it's not easy to change a resolution code in Tracker once the bug has been resolved (the only way is to reopen, then re-resolve).
  • Don't be afraid to discuss your testing with the developer assigned to the bug. Simply adding a comment should get the attention of the developer as they are notified of all changes.

Detailed description of Tracker fields and groups

Tracker fields

NB A short explanation appears under each field in Tracker.

Project - Required field. Tracker is a collection of multiple projects. At present there are 3: 'moodle', ' sites' and 'Non-core contributed modules'. Specify 'moodle' for issues/bugs related to moodle software; specify ' sites' for issues/bugs related to,,,, or; specify 'Non-core contributed modules' for issues/bugs related to contributed modules.

Issue Type - Required field. Bugs are classified as 1 of the following:

Bug - A problem which impairs or prevents Moodle from functioning correctly.
Improvement - An enhancement to an existing Moodle feature.
New Feature - A new Moodle feature which has yet to be developed.
Task - A task that needs to be completed. Tasks usually refer to work that must be done outside the product.
Sub-Task - Issues are sometimes broken into multiple sub-tasks.

Summary - Required field. A brief, concise description of the problem.

Security Level - Optional field. Specify if this bug or change has security implications for Moodle. Bugs with serious security implications are restricted so that only members of the moodle-security group can see them.

Priority - Bugs are prioritised using one of the following:

Blocker - Blocks development and/or testing work, production could not run.
Critical - Crashes, loss of data, severe memory leak.
Major - Major loss of function.
Minor - Minor loss of function, or other problem where easy workaround is available.
Trivial - Cosmetic problem like misspelled words or misaligned text.

Component/s - Required field. Select the area in Moodle which is affected by this bug. Select 'Unknown' if you are unsure.

Affects Version/s - Required field. This is the Moodle version in which the bug has been found. It is entered by the person logging the bug, and typically only 1 version is specified. Enter your current version when logging an 'improvement', 'task', or 'new feature' as this will help assess the state of the product when the request was made.

Assigned To - This is the person who will fix (code) the issue. Tracker automatically assigns issues to Component Leads. Developers or QA Testers can reassign issues.

Reporter - The person who logs the bug. This field is automatically filled by Tracker.

Environment - Specify the operating system, software platform and/or hardware specifications if applicable to this bug.

Description - A full and complete yet concise description of the problem or improvement.

Database - Optional field. If applicable to the bug, identify the database type.

URL - Optional field. If possible, provide a URL address that demonstrates an example of this bug.

QA Assignee - Used to designate the person who will test this issue.

Fixed Version/s - This is the Moodle version the bug was or will be fixed in. Basically you should think Which release notes should this appear in? This field is normally completed by the developer when the bug has been resolved or by lead developers allocating bugs for a specific release. Normally only one version is specified in this field. It symbolises the first version of Moodle where the change will be seen.

Example: after Moodle 1.9 has been released, if you fix a bug on the MOODLE_19_STABLE and HEAD branches, mark it as fixed in 1.9.1. If you also backported to MOODLE_18_STABLE, then add the version of the next 1.8.x release too.
If you resolve the bug as anything but "Fixed" (Cannot Reproduce, Won't Fix, etc.) leave Fix Version/s blank.
If you resolve the bug as Duplicate, then create a link to the duplicate issue.
These Fix version/s are used to automatically build release notes (see the tabs on

Attachment - Optional. Attach a file that will help developers and testers better understand the bug. Maximum attachement size is 512Kb.

Comment - The comment field is a detailed register of all changes that relate to this bug.

Resolution - This field is only displayed when resolving or closing a bug. Specify a code that best describes how this bug was resolved.

Fixed - Bug has been fixed; a code change will be checked into CVS. Use this resolution code only when actual changes were made to Moodle code.
Won't Fix - The problem described is an issue which will never be fixed.
Not a bug - This issue is not a bug; was logged in error. Use this code if the bug was fixed by another bug report or in some earlier Moodle version.
Duplicate - The problem is a duplicate of an existing issue.
Incomplete - More information is needed to understand this bug.
Can't Reproduce - All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
Deferred - The resolution to this bug will be deferred to a later release.

Tracker groups and permissions

Standard Users [groupname=jira-user] - This is the default group. New user accounts are placed in this group at the time of creation, and users must be a member of this group in order to log into Tracker. Members of this group can browse bugs, create new bugs, comment on bugs, create attachments, create sub-tasks, create filters, watch bugs, and vote for bugs. Members of this group can also resolve bugs, which is primarily a way of closing bugs that are no longer relevant (eg duplicates, or logged in error). Standard Users can configure their Tracker workspace by using the "Configure your Issue Navigator" button. This feature allows users to view watch and voting lists and to manage preferences, profile, and password.

Developers [groupname=jira-developer] - Developers can do everything Standard Users can do. In addition they can clone bugs, close bugs, edit bugs, link bugs, and assign bugs. Members of this group can also use the Bulk Edit function which allows bulk updated to multiple bugs.

Testers [groupname=moodle-testers] - Testers can do everything a Developer can do.

Moodle Security groups [groupname=moodle-security] - Trusted developers and administrators who need to work on and learn about security issues.

"Nobody" is a Tracker user created to alert users to the fact that an issue hasn't been assigned to a developer. These issues are regularly reviewed by the team at Moodle HQ.

NB You can browse a project while not logged in to Tracker, however you will be unable change/edit/comment on bugs.

Link types

The following link types are available:

duplicates - duplicates are inevitable in a project the size of Moodle. They occur when a logger is unaware of an existing bug that describes the same problem. Use duplicates to link to the first or most comprehensively described instance of the problem. All duplicates should be linked together.
blockers - use this to identify bugs that block others from being fixed.
cloners - in some instances a duplicate bug is intentionally created in order to track the fix in another branch of the code - this almost never is used in the Moodle project.
dependency - often a fix is dependent on another bug being resolved first, on in a specific order.
relates - used to identify a bug that is somehow related to another bug.

Don't be afraid to link bugs. Links are bi-directional meaning that there's a concept of 'inward' and 'outward' - it affects how linked bugs are displayed. This is why you'll see "blocks/is blocked by" or "duplicates/is duplicated by" in the drop down list of the Link Issue dialog. Don't become too concerned about using the "correct" link type - all link types work similarly.

See also