Filing bugs and issues - Revision history

Unworthyslave: /* Access the Joomla! development bug tracker. */

2013-04-10T13:37:00Z

‎Access the Joomla! development bug tracker.

Unworthyslave at 20:50, 8 September 2012

2012-09-08T20:50:49Z

Unworthyslave: /* Reporting bugs */

2012-09-06T19:56:20Z

‎Reporting bugs

Chris Davenport: Reverted edits by SammyWilson (talk) to last revision by Sueter

2011-08-08T07:21:05Z

Reverted edits by SammyWilson (talk) to last revision by Sueter

SammyWilson: /* Check to see if the bug you want to report is already reported. */

2011-08-08T02:59:51Z

‎Check to see if the bug you want to report is already reported.

Sueter: /* Access the Joomla! development bug tracker. */

2011-07-20T18:45:08Z

‎Access the Joomla! development bug tracker.

Batch1211 at 20:41, 29 September 2010

2010-09-29T20:41:17Z

Dextercowley: add category bug squad

2010-08-13T03:02:08Z

add category bug squad

Rudy at 10:38, 21 July 2010

2010-07-21T10:38:30Z

Masterchief: /* Access the Joomla! development bug tracker. */

2010-05-18T04:06:42Z

‎Access the Joomla! development bug tracker.

@@ Line 9: / Line 9: @@
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] - Active
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Joomla! 2.5 Bug Tracker] - Active - this is for issues that *only* affect 2.5.  For issues that affect 2.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Old Joomla! 2.5 Bug Tracker] - Inactive - Please use the main CMS Issue Tracker (above) to report Joomla 3 and Joomla 2.5 bugs.
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active - this is for issues that *only* affect 1.5. For issues that affect 1.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Inactive
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=5782 Joomla! 1.0 Bug Tracker] - Closed

@@ Line 10: / Line 10: @@
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] - Active
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=11410 Joomla! 2.5 Bug Tracker] - Active - this is for issues that *only* affect 2.5.  For issues that affect 2.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
-*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active
+*[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active - this is for issues that *only* affect 1.5. For issues that affect 1.5 and 3.0, please put them in the Joomla! CMS Issue Tracker (see above).
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=5782 Joomla! 1.0 Bug Tracker] - Closed

@@ Line 1: / Line 1: @@
 == Reporting bugs ==
-To report a bug in the Joomla! bug trackers, you need to create an "artefact" (''Editor's note: joomlacode.org uses the American spelling "artifact", but our policy is to use British/Australian spellings throughout the documentation.''). Once the artefact is created, the developers will check the validity of it and act accordingly.
+To report a bug in the Joomla! bug trackers, you need to create a tracker item. Once the tracker item is created, the developers will check the validity of it and act accordingly.
 === Register an Account at joomlacode.org ===
@@ Line 9: / Line 9: @@
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8103 Joomla! CMS Issue Tracker] - Active
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32 Joomla! 1.5 Bug Tracker] - Active
 *[http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=5782 Joomla! 1.0 Bug Tracker] - Closed
@@ Line 14: / Line 15: @@
 === Check to see if the bug you want to report is already reported. ===
-A series of filters display the artefacts. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the artefacts to check their contents. If the issue you are experiencing is not already reported, click on the bottom-right Button "Add new Tracker Item".
+A series of filters display the tracker items. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the tracker items to check their contents. If the issue you are experiencing is not already reported, click on the bottom-right Button "Add new Tracker Item".
 A new screen will display and there, the more information you give, the easier it is for the developers.
@@ Line 34: / Line 35: @@
 === Provide a summary ===
-Describe in a few words the issues you are having. It is generally a good idea to use existing artefacts as examples if this is your first time reporting a bug.
+Describe in a few words the issues you are having. It is generally a good idea to use existing tracker items as examples if this is your first time reporting a bug.
 Examples:
@@ Line 81: / Line 82: @@
 === Add an attachment to your report ===
-To better describe the issue or/and propose a fix, you can add attachments to the artefact you are creating by using the "Browse" buttons at the bottom of the screen.
+To better describe the issue or/and propose a fix, you can add attachments to the tracker item you are creating by using the "Browse" buttons at the bottom of the screen.
 A screen capture of the page(s) concerned helps a lot. If you can, try to optimise the size of the image through an image editor.
 If you know what part(s) of the code base to change, a patch [patches] or a full file where your changes are WELL shown will help the developers to solve the problem quicker.
@@ Line 87: / Line 88: @@
 === Finish and send in the report ===
-You will receive an e-mail confirming that you posted the artefact. When someone comments or asks for supplementary details or solves the issue, you will receive a notification e-mail and may reply if needed.
+You will receive an e-mail confirming that you posted the tracker item. When someone comments or asks for supplementary details or solves the issue, you will receive a notification e-mail and may reply if needed.
 === Extra tips and tricks ===
@@ Line 100: / Line 101: @@
 * Don't use the trackers to make large-scale feature requests. We like to discuss any big changes to Joomla!'s core on the [http://forum.joomla.org/index.php#6 developers forums] before actually working on them.
 * Don't reopen issues that have been marked "not a bug". This mark means that the decision has been made that we can't or won't fix this particular issue. If you're not sure why, please ask on developer forums.
-* Don't use the tracker for lengthy discussions, because they're likely to get lost. If a particular artefact is controversial, please move discussion to [http://forum.joomla.org/index.php#6 developer forums].
+* Don't use the tracker for lengthy discussions, because they're likely to get lost. If a particular tracker item is controversial, please move discussion to [http://forum.joomla.org/index.php#6 developer forums].
 == Reporting security issues ==

@@ Line 14: / Line 14: @@
 === Check to see if the bug you want to report is already reported. ===
-A series of filters display the artefacts. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the artefacts to check their contents. If the issue you are experiencing <span class="plainlinks">[http://www.diamondlinks.net/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] is not already reported, click on the bottom-right Button "Add new Tracker Item".
+A series of filters display the artefacts. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the artefacts to check their contents. If the issue you are experiencing is not already reported, click on the bottom-right Button "Add new Tracker Item".
 A new screen will display and there, the more information you give, the easier it is for the developers.
@@ Line 31: / Line 31: @@
 * Customer : Use "User" if the issue is in front-end, "Developer" if the issue concerns an extension you are developing, "Administrator" in other cases.
 * Web Server : The version/server type is also available in "Help" -> "System Info".
-−
 === Provide a summary ===

@@ Line 14: / Line 14: @@
 === Check to see if the bug you want to report is already reported. ===
-A series of filters display the artefacts. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the artefacts to check their contents. If the issue you are experiencing is not already reported, click on the bottom-right Button "Add new Tracker Item".
+A series of filters display the artefacts. Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing. Mouse over the title of the artefacts to check their contents. If the issue you are experiencing <span class="plainlinks">[http://www.diamondlinks.net/<span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">link building</span>] is not already reported, click on the bottom-right Button "Add new Tracker Item".
 A new screen will display and there, the more information you give, the easier it is for the developers.
@@ Line 31: / Line 31: @@
 * Customer : Use "User" if the issue is in front-end, "Developer" if the issue concerns an extension you are developing, "Administrator" in other cases.
 * Web Server : The version/server type is also available in "Help" -> "System Info".
-−
 === Provide a summary ===

← Older revision		Revision as of 20:41, 29 September 2010
Line 113:		Line 113:
	* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.		* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.

−	[[Category:Development]] [[Category:Bug_Squad]]	+	[[Category:Development]] [[Category:Bug_Squad]][[Category:Working Groups]]

← Older revision		Revision as of 03:02, 13 August 2010
Line 113:		Line 113:
	* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.		* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.

−	[[Category:Development]]	+	[[Category:Development]] [[Category:Bug_Squad]]

← Older revision		Revision as of 10:38, 21 July 2010
Line 113:		Line 113:
	* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.		* Publicly announce the vulnerability and the fix on the pre-determined go-public date. This will probably mean a new release of Joomla! but in some cases it may simply be patches against current releases.

−	~~[[Category:Bug Squad]]~~
	[[Category:Development]]		[[Category:Development]]