Changes

From SME Server
Jump to navigationJump to search

Bugzilla Help (view source)

Revision as of 23:42, 3 February 2013

68 bytes added ,  23:42, 3 February 2013
no edit summary
Line 1: Line 1:  
<noinclude>{{Languages}}</noinclude>
 
<noinclude>{{Languages}}</noinclude>
 
==Bug Tracker==
 
==Bug Tracker==
 +
 
Please help us to make our software as reliable as possible. Please report possible bugs only via the bug tracker and encourage others to do the same.  
 
Please help us to make our software as reliable as possible. Please report possible bugs only via the bug tracker and encourage others to do the same.  
   Line 9: Line 10:  
===Bugzilla is easy===
 
===Bugzilla is easy===
   −
A frequent complaint is Bugzilla is too hard or convoluted, but it is hard to justify.
+
A frequent complaint is Bugzilla is too hard or convoluted, but it is hard to justify the complaint.
    
*You open an account
 
*You open an account
Line 17: Line 18:     
===Searching Bugs===
 
===Searching Bugs===
 +
 
Have you searched bugzilla, and read the SME Server Manual and FAQ ?
 
Have you searched bugzilla, and read the SME Server Manual and FAQ ?
   Line 26: Line 28:  
* Advanced
 
* Advanced
 
You can restrict searches by using a selection or multiple selections of a category  <br />
 
You can restrict searches by using a selection or multiple selections of a category  <br />
−
Use Control Click to select/deselect from selection sets, if none are selected all are.
+
Use Control Click to select/deselect from selection sets, if none are selected the defailt is all.
    
* Reports
 
* Reports
Line 38: Line 40:     
===Reporting Bugs===
 
===Reporting Bugs===
 +
 
Please take the time to read
 
Please take the time to read
 
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
 
[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
 
(available in multiple languages)
 
(available in multiple languages)
   −
For bugs in SME Server Release, SME Server Future & SME Server Translations the following format is suggested. It's not always appropriate eg. New Feature Requests  
+
For bugs in SME Server Release, SME Server Future & SME Server Translations the following format is suggested. It's not always appropriate so use some discretion, see eg. New Feature Requests  
    
When reporting a new bug, and after choosing the platform, the next screen asks for more details on your problem.  There are 4 main fields that need to be completed. These are '''Component,''' '''Found-In-Version,''' '''Summary,''' and '''Description.'''  Fields such as '''Flags''' and '''Requestee''' should be left blank initially by most reporters. The '''CC''' field is for other people you would like notices on this issue to be sent to.  YOU will always be automatically included by default, so you don't need to 'cc' yourself.  The '''Attachment''' button at the bottom of the page is used to attach additional file information such as log files that may be helpful.
 
When reporting a new bug, and after choosing the platform, the next screen asks for more details on your problem.  There are 4 main fields that need to be completed. These are '''Component,''' '''Found-In-Version,''' '''Summary,''' and '''Description.'''  Fields such as '''Flags''' and '''Requestee''' should be left blank initially by most reporters. The '''CC''' field is for other people you would like notices on this issue to be sent to.  YOU will always be automatically included by default, so you don't need to 'cc' yourself.  The '''Attachment''' button at the bottom of the page is used to attach additional file information such as log files that may be helpful.
Line 82: Line 85:     
===Verifying Bugs===
 
===Verifying Bugs===
 +
 
Bugs in the SME Server Release, SME Server Future & SME Server Translations products  
 
Bugs in the SME Server Release, SME Server Future & SME Server Translations products  
 
need to be verified if fixed. (otherwise they can be closed)  
 
need to be verified if fixed. (otherwise they can be closed)  
Line 127: Line 131:  
===General===
 
===General===
 
====Bug Categories====
 
====Bug Categories====
 +
 
Bugs are sorted by '''Product''', they should be mostly self explanatory. Future/7.x/8.x/9.x may need  clarifying.  
 
Bugs are sorted by '''Product''', they should be mostly self explanatory. Future/7.x/8.x/9.x may need  clarifying.  
   Line 154: Line 159:     
====Bug Triage====
 
====Bug Triage====
 +
 
If you can help, the developers can concentrate on fixing the bugs. <br >
 
If you can help, the developers can concentrate on fixing the bugs. <br >
−
The steps in this list take approx 90% of the time of resolving most bugs.  
+
The steps in this list take approx 90% of the time in the resolving of most bugs.  
    
Reread [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
 
Reread [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to report bugs effectively]
Line 171: Line 177:     
====Bug Status====
 
====Bug Status====
 +
 
[http://www.bugzilla.org/docs/tip/html/lifecycle.html Lifecycle of a Bug]
 
[http://www.bugzilla.org/docs/tip/html/lifecycle.html Lifecycle of a Bug]
   Line 241: Line 248:     
====Bugzilla flags====
 
====Bugzilla flags====
 +
 
These will be obvious to the people they are intended to serve.  If you feel  
 
These will be obvious to the people they are intended to serve.  If you feel  
 
comfortable setting them based on information contained in the bug or needs  
 
comfortable setting them based on information contained in the bug or needs  
Retrieved from "https://wiki.koozali.org/Special:MobileDiff/17880"

Navigation menu