Contribute/Bugsquad/Quick Introduction to Bugzilla - Revision history

Moijes12: /* Modifying a bug report (permissions required) */

2011-12-04T02:40:00Z

‎Modifying a bug report (permissions required)

2009-12-26T01:30:12Z

‎Fields of a bug report

2009-12-22T02:37:50Z

‎Configure your account (Important)

2009-12-16T14:28:55Z

‎General Tips

2009-12-16T14:27:03Z

‎Modifying status of a bug report (permissions required)

2009-12-16T14:09:45Z

2009-12-16T14:08:46Z

‎Configure your account (Important)

2009-12-16T14:04:33Z

‎Configure your account (Important)

2009-12-16T14:00:15Z

‎Common Operations

2009-12-16T13:59:20Z

‎Adding comments

@@ Line 182: / Line 182: @@
 Finally you can modify the bug report status:
-* Mark ir as confirmed (NEW)
+* Mark it as confirmed (NEW)
 * Mark it as fixed or non-reproducible (RESOLVED as FIXED or RESOLVED as WORKSFORME)
 * Mark it as duplicate of another bug report (DUPLICATE of bug report XXXXXX)

@@ Line 44: / Line 44: @@
 '''Comments:''' The first comment is always the original description of the bug sent by the reporter. The other ones could be comments added by the same reporter or by any other user, a bug triager, or a developer.
-'''Keywords:''' Special words which are used to mark special reports, in order to find them easily.
+'''Keywords:''' Special words which are used to mark special reports, in order to find them easily. ''Several keywords can be used separated by commas.''
 '''CC List:''' List of mail addresses (from reporters or contributors) who are tracking the bug report and who are going to get a mail notification about every change on it.

@@ Line 60: / Line 60: @@
 [[File:Bugzilla_guide_preferences.png]]
-* There is an '''important setting which must be changed''' to avoid confusions on some situations: ''"After changing a bug same_bug" should be set to "Show the updated bug"''
+* There is an '''important setting which must be changed''' to avoid confusions on some situations: ''"After changing a bug" should be set to "Show the updated bug"''
 With the default behavior, after you modify a bug report (or after adding a comment) you will be redirected to another bug report (the next in your search list). Most of the users get confused with this behavior and write other comment in that bug report, thinking it is the same as before.

← Older revision		Revision as of 14:28, 16 December 2009
Line 190:		Line 190:
	==General Tips==		==General Tips==

−	~~Foo bar~~	+	* Take your time to discover bugzilla and its options.
		+	* Customize your settings until you feel confortable working with the bug tracker and tools
		+	* Bookmark the webpages of the common operations you use
		+	* Generate custom searches and save it to look at them later
		+	* Do not try to do too much things at the same time or you will end up with a headache :)

@@ Line 160: / Line 160: @@
 When you are ready, click the '''Commit''' button
-===Modifying status of a bug report (permissions required)===
+===Modifying a bug report (permissions required)===
-Modifying some of the fields of a bug report
-[Screenshot]
+If you have the enough bugzilla permissions, you can modify more fields of a bug reports. This is oftenly useful while organizing ("triaging") the reports.
 ==General Tips==
 Foo bar

← Older revision		Revision as of 14:04, 16 December 2009
Line 53:		Line 53:

	===Configure your account (Important)===		===Configure your account (Important)===
		+
		+	Prior to start using your bugzilla account, it is important to configure it.
		+
		+	You can access your control panel using the "Edit my Preferences" link or with this URL: [https://bugs.kde.org/userprefs.cgi User Preferences]
		+
		+	* There is an '''important setting which must be changed''' to avoid confusions on some situations:
		+	''"After changing a bug same_bug" should be set to "Show the updated bug"''
		+
		+	With the default behavior, after you modify a bug report (or after adding a comment) you will be redirected to another bug report (the next in your search list). Most of the users get confused with this behavior and write other comment in that bug report, thinking it is the same as before.

	===Get a description of the products and components===		===Get a description of the products and components===

← Older revision		Revision as of 14:00, 16 December 2009
Line 51:		Line 51:

	==Common Operations==		==Common Operations==
		+
		+	===Configure your account (Important)===

	===Get a description of the products and components===		===Get a description of the products and components===

@@ Line 137: / Line 137: @@
 ===Adding comments===
-[Screenshot]
+In every bug report page, you will find a textbox (below the comments) which allows you to add a comment to that report
 ===Modifying status of a bug report (permissions required)===