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

Tracker issue labels

From MoodleDocs

This content of this page has been updated and migrated to the new Moodle Developer Resources. The information contained on the page should no longer be seen up-to-date.

Why not view this page on the new site and help us to migrate more content to the new site!

The Moodle Tracker allows issues to be "labelled" with tags. This page lists common labels that we use to flag aspects about our MDL issues (bugs and feature requests about Moodle itself).

Note: Labels can only be added by a user with permission to edit an issue i.e. the issue reporter, members of the developers group, or members of certain other groups.


This is set after a bug has been triaged by component lead or HQ developer. It indicates that the issue has been confirmed, with basic fields like "Priority" checked, and is now ready for a developer to look at.
Used to flag issues that are being triaged (sometimes an ongoing process for days or weeks). When the issue has been triaged the triaging_in_progress label should be removed and a triaged label should be added or when the issue is closed.
Used to flag that an issue is a direct result of a Moodle QA test, conducted just before major releases. The bug should also be LINKED to the original MDLQA test, so that developers/integrators can reset the original MDLQA test (for re-testing) when the MDL issue is fixed. Once all the related MDLQA tests are passing the label can be deleted.
Used to flag MDL issues that are converting MDLQA issues to behat features. The bug should also be LINKED to the MDLQA test being converted. Useful to know what's going and exclude some issues from manual QA. Once the MDL issue has been closed and the MDLQA has been moved to MDLQA-5249 the label can be deleted.
Used to flag issues that should have their own unit tests.
Used to flag issues that should be regularly tested using the behat framework ( Before a major release these issues will be reviewed and new feature files will be added.
Used to flag issues that cannot be covered by automated tests. When adding the label, please also add a comment advising exactly what needs covering in the QA test e.g. steps 6-10 in testing instructions.
Used to flag issues identified in QA testing which we were not able to fix before the release. Hopefully such issues can be worked on shortly after release, removing the label once the issue is fixed.
Used to flag issues that have created a need for documentation work, such as new pages, changes, or even being added to upcoming release notes. Docs people will look for these issues periodically when working on documentation, removing the label once documentation has been written. For new features in the upcoming version of Moodle, please add documentation to the dev docs (adding a link to it from the tracker issue) or in a comment in the issue, then when the new version wiki is set up (3 weeks prior to release), the info can be transferred.
cl_docs_required (all | yours)
Used to flag issues that contain features which need to be documented in the Component Library. The responsibility of creating/updating Component Library documentation falls to the developer assigned to each relevant issue. Normally the relevant documentation should be included in the issue, but in some cases this will not be the case.:When the issue is resolved and component library documentation was not included, a new issue should be created for the Component Library changes, linking using the "Documents" and "is documented by" issue links, and the cl_docs_required label should be removed from the issue.
dev_docs_required (all | yours)
Used to flag issues that need to be noted in the dev docs. The responsibility of creating/updating Dev docs falls to the developer assigned to each relevant issue. When the issue is resolved, documentation should be created/updated, an appropriate URL should be added to the Documentation link field of the issue and the dev_docs_required label should be removed from the issue.
Used to flag issues already sent to integration that, for any cause, have been postponed to next cycles. Used only by integrators when there is some dependency or time-period causing one issue not being immediately integrable. Must be cleaned when the held is over.
Used to ask for an issue (having the integration_held label) to become unblocked, this flag must be coupled with a reasoned comment. Anybody can use it as far as repeated requests are avoided. Development managers will decide ASAP about giving the issue an integration opportunity or keeping it held. See Integration_Review#During_continuous_integration.2FFreeze.2FQA_period.
Used to flag security issues that have been reviewed by integrators already but held from integration repository. These issues must be cleared during point releases.
Used to flag issues which help to improve the security of Moodle, but are not directly exploitable security bugs (and therefore do not have a security level assigned). For example, MDL-66775 and MDL-65443.
Moodle Partners apply this label to flag issues that are important to their clients. The Moodle HQ dev team takes this label into consideration when setting roadmap and bug fixing priorities.
This label indicates that a solution (patch) has been attached to the issue. However, if you can, it may be better to submit the issue for peer review, rather than using this label. This is useful to component leads and Moodle HQ when deciding what to work on next.
A developer can add the label 'cime' to an issue to request that CiBot perform an Automated code review.
Used to flag any issues that developers think may affect Moodle's performance in some way (positively or negatively)
Used to identify issues that affect the interface presented to users. This label will usually be added together with the docs_required label, but the ui_change will remain permanently with the issue, while the docs_required label is removed after docs are created. This label is searched for during the preparation of release notes.
Used to identify issues that require review by Moodle HQ UX designers. This label will usually be added to issues that involve more than a trivial UI or workflow change, to ensure UX best practice is applied, with a consistent and human centered design approach. Adding this label will ensure the issue is placed on the UX backlog for review and input.
Used to identify API changes. This label will usually be added together with the dev_docs_required label, but the api_change will remain permanently with the issue, while the dev_docs_required label is removed after docs are created. This label is searched for during the preparation of release notes.
Used to identify all issues to be listed in the release notes (minor or major).
Issues that need to be mentioned in the user documentation Upgrading under 'Possible issues that may affect you in Moodle 3.x' (major versions).
Used to identify issues describing functionality which was available in an earlier version but which is no longer available in the latest version.
Used to identify QA tests which can't be tested on the QA testing site such as upgrade testing.
Used to identify QA tests which require the tester to enter credentials such as a client ID and secret for configuring OAuth 2.
Used to identify new tests in the current QA cycle for volunteers from the community to use as a basis for exploratory testing.
Used to identify suggestions for improvements/new features as possible candidates for add-on development. New and willing developers can be directed to these issues for projects.
Used to identify MDL issues that may affect the mobile app. It should be used when adding new features to functionalities supported by the app or when doing changes in existing ones. Examples are: MDL-372 and MDL-38158
Used to identify MDL issues that may affect Moodlecloud
Used to identify MDL issues that may affect Moodle Workplace
Used to identify issues that require further clarification of the requirements through adding user stories.
Used to identify issues that already have been peer-reviewed but the user lacks permissions (pull-requester) to send the issue to integration. Any pull-requester can, on peer-reviewer's behalf, proceed with the transition. The label is removed once the issue has been transitioned.

See also