2,569
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: + + + + + + + + + + + + + + − + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 28:
Line 95: − Line 116:
Line 182: − − ==Chapter 8. Bug Tracker== − Find, report and fix bugs here http://bugs.contribs.org/ − − You don't have to be a programmer to help or use the bug tracker. − Bugs also include fixing things and making suggestions on documentation, translations and the SME Server web sites. − − General Instructions for using the bug Tracker are here [http://www.bugzilla.org/docs/tip/html/using.html Using Bugzilla] − − − ===Searching for bugs=== − To help find bugs, some prepared searches have been added in page headers, with more [[SME_Server:Documentation:HowTo:BugzillaReports | BugzillaReports]] here − − 1. Simple search <br /> − At the top of the search page choose 'Find a specific bug' <br /> − Select a Status and a Product category and enter your search term <br /> − − 2. Advanced search <br /> − At the top of the search page choose 'Advanced search' − − 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. − − typically you may restrict Product to use '7.x/Future/Documentation' <br /> − and enter a search term into either 'Summary' or 'A Comment' − − eg. Status = CLOSED, Resolution = WONTFIX, Summary = yum <br /> − will return about 7 bugs − − eg. Status = CLOSED, Resolution = WONTFIX, A Comment = yum <br /> − will return about 17 bugs − − *Modifying your search − − - Click on the hyperlinked headers to sort your list − − - Click 'Edit Search' near the page footer − * you can adjust your selection sets − * add a search tern in the summary or comments fields − * restrict the dates, eg between 365d and Now the last year, 60d and 7d from 2months ago but not the last week − * bugs you are working on or watching, add you email address to the left field in email and numbering and check cc:, commenter, etc − − - If you have a favourite search, − * when the bug list is displaying, add a name in the Remember field, these will show in your footer − * add the search to the [[:BugzillaReports | BugzillaReports]] page − − ===Reporting Bugs=== − Please help us to make our software as reliable as possible. Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Thanks. − − Everyone reporting bugs needs to read: "How to report bugs effectively": − − http://www.chiark.greenend.org.uk/~sgtatham/bugs.html − − [[http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug]] − If you have searched the Manual and Bug Tracker and not found an answer or someone else's report that matches yours, you should register on the Bug Tracker and enter a new bug. The debugging process of any issue requires active participation on the part of the reporter, providing further information and clarification of the problem. − − To enter a bug choose a category, component, fill in the details of the bug, and commit. − Please use a descriptive Summary, as most of the header searches just show the Summary − * 'panel errors' is not helpful, what panel, what errors ? − * 'Add option to limit mailman web access ' explains the topic very well − − Anyone reporting problems, ask yourself these important questions, so that you − know what to tell the developers in the bug report: − − # What version am I using and are there any contribs installed or other customisations? − # What did I do? − # What did I expect to happen? − # What happened? − # What do the logs say? −
no edit summary
==Chapter 8. Bug Tracker==
Find, report and fix bugs here http://bugs.contribs.org/
You don't have to be a programmer to help or use the bug tracker.
Bugs also include fixing things and making suggestions on documentation, translations and the SME Server web sites.
General Instructions for using the bug Tracker are here [http://www.bugzilla.org/docs/tip/html/using.html Using Bugzilla]
===Searching for bugs===
To help find bugs, some prepared searches have been added in page headers, with more [[SME_Server:Documentation:HowTo:BugzillaReports | BugzillaReports]] here
1. Simple search <br />
At the top of the search page choose 'Find a specific bug' <br />
Select a Status and a Product category and enter your search term <br />
===Bug and New Feature Verification===
2. Advanced search <br />
At the top of the search page choose 'Advanced search'
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.
typically you may restrict Product to use '7.x/Future/Documentation' <br />
and enter a search term into either 'Summary' or 'A Comment'
eg. Status = CLOSED, Resolution = WONTFIX, Summary = yum <br />
will return about 7 bugs
eg. Status = CLOSED, Resolution = WONTFIX, A Comment = yum <br />
will return about 17 bugs
*Modifying your search
- Click on the hyperlinked headers to sort your list
- Click 'Edit Search' near the page footer
* you can adjust your selection sets
* add a search tern in the summary or comments fields
* restrict the dates, eg between 365d and Now the last year, 60d and 7d from 2months ago but not the last week
* bugs you are working on or watching, add you email address to the left field in email and numbering and check cc:, commenter, etc
- If you have a favourite search,
* when the bug list is displaying, add a name in the Remember field, these will show in your footer
* add the search to the [[:BugzillaReports | BugzillaReports]] page
===Reporting Bugs===
Please help us to make our software as reliable as possible. Your role in that is to report possible bugs only via the bug tracker, and to encourage others to do the same. Thanks.
Everyone reporting bugs needs to read: "How to report bugs effectively":
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
[[http://www.bugzilla.org/docs/tip/html/bugreports.html#fillingbugs Reporting a New Bug]]
If you have searched the Manual and Bug Tracker and not found an answer or someone else's report that matches yours, you should register on the Bug Tracker and enter a new bug. The debugging process of any issue requires active participation on the part of the reporter, providing further information and clarification of the problem.
To enter a bug choose a category, component, fill in the details of the bug, and commit.
Please use a descriptive Summary, as most of the header searches just show the Summary
* 'panel errors' is not helpful, what panel, what errors ?
* 'Add option to limit mailman web access ' explains the topic very well
Anyone reporting problems, ask yourself these important questions, so that you
know what to tell the developers in the bug report:
# What version am I using and are there any contribs installed or other customisations?
# What did I do?
# What did I expect to happen?
# What happened?
# What do the logs say?
===Bug Verification===
If you find a bug you can work on, please do so.
If you find a bug you can work on, please do so.
As an example, the documentation section, only requires you to take the answer determined in the bug and copy the information onto the wiki.
As an example, the documentation section, only requires you to take the answer determined in the bug and copy the information onto the wiki.
* NEW
* NEW
Once bugs are confirmed, '''by anyone''' see note above, change status to new,
Once bugs are confirmed, '''by anyone''' see note above, change status to new,
----
----
* [-+?]
* [-+?]
Set the flag to ? to say someone needs to look at it
Set the flag to ? to say someone needs to look at it
===Bug Triage===
===Bug Triage===