Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Tracker guide: Difference between revisions

From MoodleDocs
(→‎Tracker groups and permissions: users and developers update)
(32 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{draft}}
The [http://tracker.moodle.org/ Moodle Tracker] is our database for recording and managing all Moodle development issues - bugs, improvements and feature requests.
The [http://tracker.moodle.org/ Moodle Tracker] is our database for recording and managing all Moodle development issues - bugs, improvements and feature requests.


''For an intro guide to the tracker, see [[:en:Tracker|Tracker]] in the user docs.''
''For an intro guide to the tracker, see [[Tracker introduction]].''


To do anything more than browsing and searching in the tracker, you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create an account] and then login.
To do anything more than browsing and searching in the tracker, you'll need to [http://tracker.moodle.org/secure/Signup%21default.jspa create an account] and then login.
Line 16: Line 15:
===When creating an issue===
===When creating an issue===


'''Project''' - Required field.  Tracker is a collection of multiple projects.  At present these are: 'moodle', 'moodle.org sites' and 'Non-core contributed modules'.
{| class="nicetable"
:''moodle'' for issues/bugs related to moodle software.
! Field
:''moodle.org sites'' for issues/bugs related to tracker.moodle.org, docs.moodle.org, demo.moodle.org, download.moodle.org, moodle.org, etc..
! Values
:''Non-core contributed modules'' for issues/bugs related to contributed plugins.
! Notes
 
|-
'''Issue Type''' - Required field.  Bugs are classified as one of the following:
| valign=top | '''Project'''
:''Bug'' - A problem which impairs or prevents Moodle from functioning correctly.
| valign=top |
:''Improvement'' - An enhancement to an existing Moodle feature.
; Moodle
:''New Feature'' - A new Moodle feature which has yet to be developed.
: For an issue relating to the Moodle codebase
:''Task'' - A task that needs to be completed. Tasks usually refer to work that must be done outside the product.
; Moodle Community Sites
:''Sub-Task'' - Issues are sometimes broken into multiple sub-tasks.
: For an issue on tracker.moodle.org, docs.moodle.org, demo.moodle.org, download.moodle.org, moodle.org, etc..
 
; Non-core contributed modules
'''Summary''' - Required field.  A brief, concise description of the problem.
: For an issue with a contributed plugin
 
(There are a few more projects, but these are the main ones.)
'''Description''' - A full and complete yet concise description of the problem or improvement. Please provide as much detail as possible. The description of bugs should include the steps needed to replicate the bug, including the expected and actual outcomes.
| valign=top |
 
* Tracker is used for multiple projects.
'''Testing instructions''' - The steps that a tester should follow to achieve the expected behaviour after the issue has been resolved.
|-
 
| valign=top | '''Issue Type'''  
'''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 one 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.
| valign=top |
 
; Bug
'''Component/s''' - Required field.  Select the area in Moodle which is affected by this bug. Select 'Unknown' if you are unsure.
: A problem which impairs or prevents Moodle from functioning correctly.
 
; Improvement''
'''Database''' - Optional field.  If applicable to the bug, identify the database type.
: An enhancement to an existing Moodle feature.
 
; New Feature''
'''Environment''' - Specify the operating system, software platform and/or hardware specifications if applicable to this bug.
: A new Moodle feature which has yet to be developed.
 
; Task
'''Security Level''' - The higher the security level, the fewer people who can view the issue.
: A task that needs to be completed, usually apart from coding.
:''None'' - Viewable by everyone, including non-logged-in users
; Sub-Task
:''Could be a security issue'' - Viewable by all logged-in users
: Part of a greater task
:''Minor security issue'' - Viewable by developers and testers only
|-
:''Serious security issue'' - Viewable by members of the security team only
| valign=top | '''Summary'''
 
| valign=top | A brief, concise description of the problem.
'''URL''' - Optional.  If possible, provide a URL address that demonstrates an example of this bug.
| valign=top |
 
* When the issue is about applying an existing solution to another, usually older, branch (namely "backport"), please use the summary of the existing solution plus its issue number (i.e. "Fix forum alignment (backport of MDL-99999)").
'''Attachment''' - Optional.  Attach a file that will help developers and testers better understand the bug. Maximum attachment size is 512Kb. It is very helpful to attach screenshots of bugs. This really helps developers. Attaching a patch containing a solution is also very helpful.
|-
 
| valign=top | '''Description'''
'''Workaround''' - Optional. If there is a way to achieve the desired functionality by other means, please describe it here. This will be very useful to other Moodle users who have the same problem, until the issue is resolved. If the issue can be resolved by a simple code change, say one line, then you can give that as a workaround.
| valign=top |
 
A full and complete description of the issue including:
'''Labels''' - see [[Tracker issue labels]]
* replication steps,
* the expected result,
* the actual result,
* any error messages shown with [[:en:Debugging|Debugging]] turned on, and
* any other relevant information.
| valign=top |
* Please provide as much detail as possible.
* More detail means an issue will be easier to resolve.
|-
| valign=top | '''Affects Version/s'''
|
* For bugs: the latest ''released'' version in which the bug is found
* For improvements: the latest ''released'' version
* For new features: Use 'Future dev'
|
|-
| valign=top | '''Component/s'''
| valign=top | The area(s) in Moodle which is affected by the issue.
| valign=top |
* Select 'Unknown' if you are unsure.
|-
| valign=top | '''Security Level'''
| valign=top |
; None
: Viewable by everyone, including non-logged-in users
; Could be a security issue
: Viewable by members of the jira-developers group
; Minor security issue
: Viewable by members of the security team only
; Serious security issue
: Viewable by members of the security team only
| valign=top |
* The reporter can view the issue they reported, regardless of the security level set.
* The higher the security level, the fewer people who can view the issue.
* The 'Could be a security issue' should only be used temporarily when the issue is reported. A decision should be made as soon as possible to set another level.
|}


===When editing an issue===
===When editing an issue===
Line 60: Line 94:
Once an issue has been created, the following additional fields are able to be changed/set by editing the issue. Not all users can edit all fields.
Once an issue has been created, the following additional fields are able to be changed/set by editing the issue. Not all users can edit all fields.


'''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.
{| class="nicetable"
: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.
! Field
 
! Values
:If you resolve the bug as anything but "Fixed" (Cannot Reproduce, Won't Fix, etc.) leave Fix Version/s blank.
! Notes
: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 http://tracker.moodle.org/browse/MDL).
| valign=top | '''Fixed Version/s'''
 
| valign=top |
'''Priority''' - Issues are prioritised using one of the following.
* Prior to integration, this will be set to a backlog (a queue of development work), for example STABLE Backlog, Dev Sprint 2.
:''Blocker'' - Blocks development and/or testing work, production could not run (Blocker should not be applied to Improvements or New features)
* After integration, this will be set to the Moodle version the bug was fixed in, for example 2.4.1.
:''Critical'' - Leads to wrong results, loss of data, severe memory leak
|
:''Major'' - Major loss of function
* This is usually set during triage, or later by a developer or integrator.
:''Minor'' - Minor loss of function, or other problem where easy workaround is available
* If you resolve the bug as anything but "Fixed" (Cannot Reproduce, Won't Fix, etc.) leave Fix Version/s blank.
:''Trivial'' - Cosmetic problem like misspelled words or misaligned text
* Fix version/s are used to automatically build release notes (see the tabs on http://tracker.moodle.org/browse/MDL).
 
|-
The priority of issues may be promoted by HQ developers and component leads as the issue escalates. Others wishing to influence the priority of issues should do so by voting for the issue.
| valign=top | '''Priority'''
 
| valign=top |
'''Reporter''' - The person who logs the bug.  This field is automatically filled by Tracker.
; Blocker
 
: Blocks development and/or testing, prevents Moodle from running
'''Assignee''' - This is the person who will fix (code) the issue. Tracker automatically assigns issues to Component Leads. Developers or QA Testers can reassign issues. Please note that even though a person may be assigned to an issue, this does not mean they are working on the issue, although they are likely to in future.
: Applicable to bugs only
 
; Critical
'''Peer reviewer''' - This is another person who will test a fix at the code level.
: Crashes server, loss of data, severe memory leak
 
; Major
'''Integrator''' - This is another person who will integrate the code into the Moodle codebase.
: Major loss of function, incorrect output
 
; Minor
'''Tester''' - This is the person who will test the solution at a functional level, according to the test instructions provided.
: Minor loss of function where workaround is possible
 
; Trivial
'''Pull...''' fields - These fields are used by developers to link to a code solution in a Git repository. There may be multiple solutions if the problem affects multiple Moodle versions.
: Cosmetic problem like misspelt words or misaligned text
 
| valign=top |
'''Integration date''' - This indicates when the solution was integrated into the Moodle codebase.
* When it is reported, the priority level represents the severity of an bug.
 
* After being reported, the priority may be promoted by HQ developers and component leads as an issue escalates.
'''Comment''' - The comment field is a detailed register of all changes that relate to this bug.
* Other users wishing to influence the priority of issues should do so by voting for the issue.
* The priority of new features and improvements should generally remain at the default (Minor) level.
|-
| valign=top | '''Reporter'''  
| valign=top | The person who logs the bug.  This field is automatically filled by Tracker.
|
|-
| valign=top | '''Assignee'''
| valign=top | The person who will fix the issue. Prior to May 2013, developers were [[Changes to issue assignment|automatically assigned]]. Currently, the assignee should be set when there is a definite intention to complete the issue.
|
* Developers or QA Testers can reassign issues.
* Please note that even though a person may be assigned to an issue, this does not mean they are currently working on the issue, although they are likely to in future.
|-
| valign=top | '''Peer reviewer'''
| valign=top | The person who will check the fix at the code level.
|
|-
| valign=top | '''Integrator'''
| valign=top | The person who will integrate the code into the Moodle codebase.
|
|-
| valign=top | '''Tester'''
| valign=top | The person who will test the solution at a functional level, according to the test instructions provided.
|
|-
| valign=top | '''Environment'''
| valign=top | The operating system, server and/or browser specifications if applicable to this bug.
|
* Note that the database is specified separately in the database field below.
|-
| valign=top | '''Database'''
| valign=top | If applicable to the bug, identify the database type.
|
|-
| valign=top | '''Testing instructions'''
| valign=top | The steps that a tester should follow to achieve the expected behaviour after the issue has been resolved.
| valign=top |
* This may be different to the replication steps reported in the description.
* These instructions are written by the developer working on the issue.
|-
| valign=top | '''Workaround'''
| valign=top | A way to achieve the desired functionality by other means.
| valign=top |
* This will be very useful to other Moodle users who have the same problem, until the issue is resolved.
* If the issue can be resolved by a simple code change, say one line, then you can give that as a workaround, although patches and Git branches are preferred.
|-
| '''Attachment'''
| valign=top | Patch files, Screenshots, example backups or other related files
| valign=top |
* Attaching a file will help developers and testers better understand the bug.
* Maximum attachment size is 512Kb.
|-
| valign=top | '''URL'''
| valign=top | If possible, provide a URL address that demonstrates an example of this bug.
|
|-
| valign=top | '''Epic Name'''
| valign=top | A short name given to an issue of type Epic so that linked issues can be grouped by this name. It should only be a few words at most.
| valign=top | Only applies to issues of type Epic.
|-
| valign=top | '''Epic Link'''
| valign=top | A link to an Epic issue. This can be added by providing the issue ID or Epic name. It is a way of organising related issues as part of a project.
| valign=top | Only applies to issues that need to be collected together for a project.
|-
| valign=top | '''Labels'''
| valign=top | See [[Tracker issue labels]]
|
* Labels should be specific values used in filters and searches.
* This is not a field for including generic keywords.
|-
| valign=top | '''Pull...'''
| valign=top | Links to a code solution in a Git repository.
|
* These fields are used by developers.
* There may be multiple solutions if the problem affects multiple Moodle versions.
|-
| valign=top | '''Documentation link'''
| valign=top | URL of related documentation.
| valign=top |
* When changes require documentation to be updated, this field should be filled.
|-
| valign=top | '''Comment'''
| valign=top |
* Notes made by all interested parties.
* A detailed register of all changes that relate to this bug.
|
|}


===When closing an issue===
===When closing an issue===


When closing an issue, the following resolution states can be applied.
{| class="nicetable"
 
! Field
'''Resolution''' - This field is only displayed when resolving or closing a bug.  Specify a code that best describes how this bug was resolved.
! Values
:''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.
! Notes
:''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.
| valign=top | '''Resolution'''
:''Duplicate'' - The problem is a duplicate of an existing issue.
| valign=top |
:''Incomplete'' - More information is needed to understand this bug.
; Fixed
:''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.
: Bug has been fixed; a code change has been integrated into Moodle code.
:''Deferred'' - The resolution to this bug will be deferred to a later release.
; Won't Fix
: The problem described is an issue which will never be fixed. Specific reasons should be given.
; Not a bug
: This issue is not a bug. The issue may have been 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 was needed to understand this bug, but it was not provided.
; Can't Reproduce
: Attempts at reproduce the issue failed. If more information appears later, please open a new issue.
; Deferred
: The resolution to this bug will be deferred to a later release or to a fix in a third-party plugin used in Moodle.
| valign=top |
* This field is only displayed when resolving or closing a bug.
|}


== Tracker groups and permissions ==
== Tracker groups and permissions ==


'''Users''' [groupname=jira-users] - Anyone who creates a tracker account and logs in is a member of the users group. Users can create new issues, comment on issues, watch and vote for issues, link issues, attach files, create sub-tasks, watch bugs, and vote for bugs.
There are a number of groups used to define the potential of users in Tracker. Here are some important ones.
'''Developers''' [groupname=jira-developers] - Developers can edit issues and assign issues to themselves.
 
If you'd like to be added to the developers group in the tracker, please send an email to [mailto:michaeld@moodle.com michaeld@moodle.com] with your tracker username and a link to an issue where you have contributed a patch.


'''Testers''' [groupname=moodle-testers] - Testers can do everything a Developer can do.
{| class="nicetable"
! Name
! Jira group
! Potential
! How to become one
|-
| valign=top | '''Users'''
| valign=top | jira-users
| valign=top | Users can create new issues, comment on issues, vote for issues, link issues, attach files, create sub-tasks and watch issues.
| valign=top | Anyone who creates a tracker account becomes a member of the Users group.
|-
| valign=top | '''Testers'''
| valign=top | moodle-testers
| valign=top | Testers are able to work on (pass and fail) QA tests prior to a major Moodle release.
| valign=top | People wishing join the Testers group and help with [[QA testing]] should email [mailto:helen@moodle.org helen@moodle.org].
|-
| valign=top | '''Moodle Security'''
| valign=top | moodle-security
| valign=top | Trusted developers and administrators who need to work on security issues that are hidden from normal users. (See [[Moodle security procedures]].)
| valign=top | This is generally limited to developers at Moodle HQ and Partner organisations. People wishing join the Moodle Security group should email [mailto:security@moodle.org  security@moodle.org] with the reasons for your request.
|-
| valign=top | '''Developers'''
| valign=top | jira-developers
| valign=top | Developers can edit issues and assign issues to themselves. They are also able to request peer reviews from HQ staff and component leads. They cannot submit code directly for integration review, but an HQ staff member or component lead can do this after a satisfactory peer review. (See [[Process]].)
| valign=top | People wishing to join the Developers group should be able to demonstrate a history of contributing patches to issues.


'''Moodle Security groups''' [groupname=moodle-security] - Trusted developers and administrators who need to work on and learn about security issues.
When a developer's first patch is integrated, tested and the issue is closed, they are added to the group and set as issue assignee.


"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.
If that doesn't happen automatically, please send an email to [mailto:integration@moodle.com integration@moodle.com] with your tracker username and links to issues where you have contributed patches.
|-
| valign=top | '''Integration requesters'''
| valign=top | pull-requesters
| valign=top | Developers can send issues for integration review. (See [[Process]].)
| valign=top | This role is reserved for Moodle HQ developers and component leads.
|}


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


==See also==
==See also==


*[[Tracker introduction]] - less scary version of this page for new users.
*[[Process]]
*[[Process]]
*[[Bug triage]]
*[[Bug triage]]
*[[Testing]]
*[[Tracker issue labels]]
*[[Testing of integrated issues]]
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43952 How to manipulate Moodle developers] forum discussion
*Using Moodle [http://moodle.org/mod/forum/discuss.php?d=43952 How to manipulate Moodle developers] forum discussion
*Wikipedia [http://en.wikipedia.org/wiki/Software_bug Definition of a bug]
*Wikipedia [http://en.wikipedia.org/wiki/Software_bug Definition of a bug]


[[Category:Developer tools]]
[[Category:Tracker]]
[[Category:Quality Assurance]]
[[Category:Quality Assurance]]

Revision as of 10:21, 14 October 2020

The Moodle Tracker is our database for recording and managing all Moodle development issues - bugs, improvements and feature requests.

For an intro guide to the tracker, see Tracker introduction.

To do anything more than browsing and searching in the tracker, you'll need to create an account and then login.

Integration workflow

The following diagram illustrates the integration workflow in the tracker and lists the different statuses of an issue.

Workflow.jpg

Tracker fields

When creating an issue

Field Values Notes
Project
Moodle
For an issue relating to the Moodle codebase
Moodle Community Sites
For an issue on tracker.moodle.org, docs.moodle.org, demo.moodle.org, download.moodle.org, moodle.org, etc..
Non-core contributed modules
For an issue with a contributed plugin

(There are a few more projects, but these are the main ones.)

  • Tracker is used for multiple projects.
Issue Type
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, usually apart from coding.
Sub-Task
Part of a greater task
Summary A brief, concise description of the problem.
  • When the issue is about applying an existing solution to another, usually older, branch (namely "backport"), please use the summary of the existing solution plus its issue number (i.e. "Fix forum alignment (backport of MDL-99999)").
Description

A full and complete description of the issue including:

  • replication steps,
  • the expected result,
  • the actual result,
  • any error messages shown with Debugging turned on, and
  • any other relevant information.
  • Please provide as much detail as possible.
  • More detail means an issue will be easier to resolve.
Affects Version/s
  • For bugs: the latest released version in which the bug is found
  • For improvements: the latest released version
  • For new features: Use 'Future dev'
Component/s The area(s) in Moodle which is affected by the issue.
  • Select 'Unknown' if you are unsure.
Security Level
None
Viewable by everyone, including non-logged-in users
Could be a security issue
Viewable by members of the jira-developers group
Minor security issue
Viewable by members of the security team only
Serious security issue
Viewable by members of the security team only
  • The reporter can view the issue they reported, regardless of the security level set.
  • The higher the security level, the fewer people who can view the issue.
  • The 'Could be a security issue' should only be used temporarily when the issue is reported. A decision should be made as soon as possible to set another level.

When editing an issue

Once an issue has been created, the following additional fields are able to be changed/set by editing the issue. Not all users can edit all fields.

Field Values Notes
Fixed Version/s
  • Prior to integration, this will be set to a backlog (a queue of development work), for example STABLE Backlog, Dev Sprint 2.
  • After integration, this will be set to the Moodle version the bug was fixed in, for example 2.4.1.
  • This is usually set during triage, or later by a developer or integrator.
  • If you resolve the bug as anything but "Fixed" (Cannot Reproduce, Won't Fix, etc.) leave Fix Version/s blank.
  • Fix version/s are used to automatically build release notes (see the tabs on http://tracker.moodle.org/browse/MDL).
Priority
Blocker
Blocks development and/or testing, prevents Moodle from running
Applicable to bugs only
Critical
Crashes server, loss of data, severe memory leak
Major
Major loss of function, incorrect output
Minor
Minor loss of function where workaround is possible
Trivial
Cosmetic problem like misspelt words or misaligned text
  • When it is reported, the priority level represents the severity of an bug.
  • After being reported, the priority may be promoted by HQ developers and component leads as an issue escalates.
  • Other users wishing to influence the priority of issues should do so by voting for the issue.
  • The priority of new features and improvements should generally remain at the default (Minor) level.
Reporter The person who logs the bug. This field is automatically filled by Tracker.
Assignee The person who will fix the issue. Prior to May 2013, developers were automatically assigned. Currently, the assignee should be set when there is a definite intention to complete the issue.
  • Developers or QA Testers can reassign issues.
  • Please note that even though a person may be assigned to an issue, this does not mean they are currently working on the issue, although they are likely to in future.
Peer reviewer The person who will check the fix at the code level.
Integrator The person who will integrate the code into the Moodle codebase.
Tester The person who will test the solution at a functional level, according to the test instructions provided.
Environment The operating system, server and/or browser specifications if applicable to this bug.
  • Note that the database is specified separately in the database field below.
Database If applicable to the bug, identify the database type.
Testing instructions The steps that a tester should follow to achieve the expected behaviour after the issue has been resolved.
  • This may be different to the replication steps reported in the description.
  • These instructions are written by the developer working on the issue.
Workaround A way to achieve the desired functionality by other means.
  • This will be very useful to other Moodle users who have the same problem, until the issue is resolved.
  • If the issue can be resolved by a simple code change, say one line, then you can give that as a workaround, although patches and Git branches are preferred.
Attachment Patch files, Screenshots, example backups or other related files
  • Attaching a file will help developers and testers better understand the bug.
  • Maximum attachment size is 512Kb.
URL If possible, provide a URL address that demonstrates an example of this bug.
Epic Name A short name given to an issue of type Epic so that linked issues can be grouped by this name. It should only be a few words at most. Only applies to issues of type Epic.
Epic Link A link to an Epic issue. This can be added by providing the issue ID or Epic name. It is a way of organising related issues as part of a project. Only applies to issues that need to be collected together for a project.
Labels See Tracker issue labels
  • Labels should be specific values used in filters and searches.
  • This is not a field for including generic keywords.
Pull... Links to a code solution in a Git repository.
  • These fields are used by developers.
  • There may be multiple solutions if the problem affects multiple Moodle versions.
Documentation link URL of related documentation.
  • When changes require documentation to be updated, this field should be filled.
Comment
  • Notes made by all interested parties.
  • A detailed register of all changes that relate to this bug.

When closing an issue

Field Values Notes
Resolution
Fixed
Bug has been fixed; a code change has been integrated into Moodle code.
Won't Fix
The problem described is an issue which will never be fixed. Specific reasons should be given.
Not a bug
This issue is not a bug. The issue may have been 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 was needed to understand this bug, but it was not provided.
Can't Reproduce
Attempts at reproduce the issue failed. If more information appears later, please open a new issue.
Deferred
The resolution to this bug will be deferred to a later release or to a fix in a third-party plugin used in Moodle.
  • This field is only displayed when resolving or closing a bug.

Tracker groups and permissions

There are a number of groups used to define the potential of users in Tracker. Here are some important ones.

Name Jira group Potential How to become one
Users jira-users Users can create new issues, comment on issues, vote for issues, link issues, attach files, create sub-tasks and watch issues. Anyone who creates a tracker account becomes a member of the Users group.
Testers moodle-testers Testers are able to work on (pass and fail) QA tests prior to a major Moodle release. People wishing join the Testers group and help with QA testing should email helen@moodle.org.
Moodle Security moodle-security Trusted developers and administrators who need to work on security issues that are hidden from normal users. (See Moodle security procedures.) This is generally limited to developers at Moodle HQ and Partner organisations. People wishing join the Moodle Security group should email security@moodle.org with the reasons for your request.
Developers jira-developers Developers can edit issues and assign issues to themselves. They are also able to request peer reviews from HQ staff and component leads. They cannot submit code directly for integration review, but an HQ staff member or component lead can do this after a satisfactory peer review. (See Process.) People wishing to join the Developers group should be able to demonstrate a history of contributing patches to issues.

When a developer's first patch is integrated, tested and the issue is closed, they are added to the group and set as issue assignee.

If that doesn't happen automatically, please send an email to integration@moodle.com with your tracker username and links to issues where you have contributed patches.

Integration requesters pull-requesters Developers can send issues for integration review. (See Process.) This role is reserved for Moodle HQ developers and component leads.

Note that you can browse a project without being logged in to Tracker, however you will be unable edit or comment on bugs.

See also