Tracker - Revision history

Jmouneyrac: /* How to write a good Tracker entry */

2008-10-21T02:20:43Z

How to write a good Tracker entry

← Older revision		Revision as of 02:20, 21 October 2008
Line 22:		Line 22:
	*Summary (describe the issue in 1 or 2 sentences)		*Summary (describe the issue in 1 or 2 sentences)
	*Description (a concise yet complete summary of the problem or improvement)		*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.		*'''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.		*'''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.		*'''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:		If possible, include additional information that may be helpful to the developer:

Jmouneyrac at 08:19, 22 September 2008

2008-09-22T08:19:20Z

← Older revision		Revision as of 08:19, 22 September 2008
Line 200:		Line 200:
	[[Category:Developer]]		[[Category:Developer]]
	[[Category:Developer tools]]		[[Category:Developer tools]]
			[[Category:Quality Assurance]]

	[[pt:Tracker]]		[[pt:Tracker]]
	[[es:Sistema de bugs]]		[[es:Sistema de bugs]]
	[[fr:Traqueur de bogues]]		[[fr:Traqueur de bogues]]

Davidkazuhiro: /* Logging new issues or improvements */ fixed section header

2008-07-21T01:11:34Z

Logging new issues or improvements: fixed section header

← Older revision		Revision as of 01:11, 21 July 2008
Line 74:		Line 74:
	Tracker's '''Quick Search''' function is explained [http://www.atlassian.com/software/jira/docs/v3.6.4/quicksearch.html here]		Tracker's '''Quick Search''' function is explained [http://www.atlassian.com/software/jira/docs/v3.6.4/quicksearch.html here]

	===Resolving issues=== (this section should be reviewed)		===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".		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".

Rubenback26 at 11:24, 22 May 2008

2008-05-22T11:24:12Z

← Older revision		Revision as of 11:24, 22 May 2008
Line 200:		Line 200:
	[[Category:Developer tools]]		[[Category:Developer tools]]

			[[pt:Tracker]]
	[[es:Sistema de bugs]]		[[es:Sistema de bugs]]
	[[fr:Traqueur de bogues]]		[[fr:Traqueur de bogues]]

Mblake: /* Tracker fields */

2008-04-24T07:10:27Z

Tracker fields

← Older revision		Revision as of 07:10, 24 April 2008
Line 108:		Line 108:
	NB A short explanation appears under each field in Tracker.		NB A short explanation appears under each field in Tracker.

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

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

Mblake: /* Tracker fields */

2008-04-24T07:09:34Z

Tracker fields

← Older revision		Revision as of 07:09, 24 April 2008
Line 132:		Line 132:
	'''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.		'''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 ~~problem~~. Tracker automatically assigns ~~bugs~~ to Component Leads. Developers or QA Testers can reassign issues.		'''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.		'''Reporter''' - The person who logs the bug. This field is automatically filled by Tracker.

Mblake: /* Tracker groups and permissions */

2008-04-23T08:38:55Z

Tracker groups and permissions

← Older revision		Revision as of 08:38, 23 April 2008
Line 174:		Line 174:

	'''Moodle Security groups''' [groupname=moodle-security] - Trusted developers and administrators who need to work on and learn about security issues.		'''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.		NB You can browse a project while not logged in to Tracker, however you will be unable change/edit/comment on bugs.

Mblake: /* Tracker fields */

2008-04-23T08:32:33Z

Tracker fields

← Older revision		Revision as of 08:32, 23 April 2008
Line 132:		Line 132:
	'''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.		'''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 problem. ~~This field is completed by developers or~~ Component Leads.		'''Assigned To''' - This is the person who will fix (code) the problem. Tracker automatically assigns bugs to Component Leads. Developers or QA Testers can reassign issues.

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

Tsala: /* See also */ link added

2008-04-01T13:04:29Z

Dougiamas: /* Tracker fields */

2008-03-27T09:05:58Z

Tracker fields

← Older revision		Revision as of 09:05, 27 March 2008
Line 146:		Line 146:
	'''QA Assignee''' - Used to designate the person who will test this issue.		'''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. 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.		'''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.		: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.

← Older revision		Revision as of 13:04, 1 April 2008
Line 188:		Line 188:
	==See also==		==See also==

			*[[Development:Weekly Code Review]]
	*[http://www.atlassian.com/software/jira/ Jira] Tracker is a slightly customised version of Atlassian's product		*[http://www.atlassian.com/software/jira/ Jira] Tracker is a slightly customised version of Atlassian's product
	*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