View source

What do we do to re-open an item that has been marked as resolved, but really is not? : see http://tracker.moodle.org/browse/MDL-6762. Would you just resubmit it?
[[User:D.I. von Briesen|D.I. von Briesen]] 00:35, 3 October 2006 (CDT)

Answer: If you do not have sufficient rights to 'reopen' a bug, simply add a comment to it.  The assignee & creator will receive email notification of your comments, and they can reopen the bug.

----
:Noticed Moodle.org homepage link says "Issue Tracking" which is a change from Bug Tracker or what ever it was between then and now.  Recent Buzz in social forum about where to log "good ideas" made this change jump out at me.   Issue is a little bit more encompassing, warm and fuzzy term than the old reliable [http://en.wikipedia.org/wiki/Image:H96566k.jpg bug]. Notice the Tracker page had not reflected this "new image" so revamped the introduction.  My edit job is still does not flow the way I want it, but I think it is an improvement. --[[User:chris collman|chris collman]] 06:46, 3 October 2006 (CDT)

==Page is getting cluttered==
I just created a section for information somebody just added, then remembered I had seen that information before on this page, maybe even wrote it :). It was there.   This indicates to me that this page needs to be re-organized. Some moving and looking at headings and sub heading.

My editing bias is that we want to encourage people to use Tracker AND to report things in a useful way that makes it efficient for the assignees. Thus that kind of information should come first.   After that we can get into the more technical field by field analysis and comments by developers etc for those who are more knowledgeable.  --[[User:chris collman|chris collman]] 07:27, 20 February 2008 (CST)

==Getting started with the tracker==

Documentation contributed on 22 September 2006 by [[User:N Hansen|N Hansen]]:


This is a good place to begin learning about Moodle Tracker. This is not intended to be an exhaustive Tracker tutorial, but an introduction to the most important features of interest to a novice user who wants to report a problem with Moodle or request a new feature. See [http://docs.moodle.org/en/Tracker#More_about_Tracker_functionality this page] for more in-depth Tracker instructions.  I will be adding more to this page in the coming days.

=== Browsing ===

Tracker is accessed from http://tracker.moodle.org.

To contribute to Tracker (that is create a new bug, comment, vote, or watch bugs), you must establish a Tracker user account.  You can browse Tracker without logging in so let's just browse for the moment.

Perhaps one of the easiest ways to become familiar with Tracker is to simply browse through previously submitted "bug" reports. On the left side of the [http://tracker.moodle.org/secure/Dashboard.jspa main tracker page] you will see two projects listed, Moodle and Moodle.org sites. The latter is for reporting problems at Moodle.org, but the former is for the Moodle software itself. Let's look at Moodle for now.

You will see there are a number of reports available. Start by clicking the "open issues" link.  This is a filter showing bugs which have not yet been resolved or fixed. On the [http://tracker.moodle.org/browse/MDL?report=com.atlassian.jira.plugin.system.project:openissues-panel open issues page] you will see a variety of categories of issues organized according to a variety of principles. New users will probably be interested in the components list. Here you will find the issues categorized according to the component of Moodle (e.g. choice, database, enrolments, blocks) to which they are related, very similar to the categories you find in the Using Moodle forums. Try clicking on a category that interests you.

You will now see a list of open issues for that component. Notice there are icons next to each issue indicating what kind of issue it is. Tracker is not only for reporting bugs (problems) with the Moodle software, it also can be used to file reports on other issues. The icons indicate what kind of issue it is:

*Red dot: Bug
*Green plus sign: Request for a new feature
*Blue arrow: An improvement or enhancement to an existing feature
*Yellow box with an x in it: A task that needs to be done
*Smaller yellow box with a dot in it: A subtask of another issue

== Duplicated tracker entries ==

there are many tracker entries that describe the same problem in different words. Maybe the original reporters thought about the problem in different ways and didn't notice the existing report. 
If you notice reports that look the same, it's good to link them.

However, which report should then become the more active one? The older report or the one with more details?
MDL-5887 illustrates my question: four identical bug reports were made. Some had more detail, some less. Which one should be considered the 'master'?--Minh-Tam Nguyen (10:15, 25 March 2009)

:All those bugs are already closed, so there is no need to change anything now.
:If you find an unresolved bug that is a duplicate of another bug, then the correct procedure is
:#Link the two bugs so that the newer (higher-numbered) bug is a duplicate of the older one.
:#Resolve the newer bug as Resolved/Duplicate.
:However, the normal rule that you resolve the higher numbered bug as a duplicate of the lower numbered bug should be reversed if the higher numbered bug is more active/complete/useful that the lower numbered one. You have to use your judgement about that.--[[User:Tim Hunt|Tim Hunt]] 04:36, 25 March 2009 (UTC)