95
edits
Changes
Jump to navigation
Jump to search
Line 44:
Line 44: − + Line 57:
Line 57: − + − + Line 69:
Line 69: − + − + − + − + + + + +
→Reporting Bugs
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 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.
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.
'''Component:''' As accurately as possible, you may choose which category your issue fits into. If Unknown then choose UNKNOWN.
'''Component:''' As accurately as possible, you may choose which category your issue fits into. If Unknown then choose UNKNOWN.
'''Description:''' Present the details of your problem in this section. You may use the following as a template:
'''Description:''' Present the details of your problem in this section. You may use the following as a template:
'''ENVIRONMENT''': '''''Give a brief server history'''''
'''ENVIRONMENT''': '''''Give a brief server history'''''
eg. SME Server 7.1, Updated to 7.3 with yum
eg. SME Server 7.1, Updated to 7.3 with yum
'''MODIFICATIONS''': '''''List any contribs or modifications you have on the server'''''
'''MODIFICATIONS''': '''''List any contribs or modifications you have on the server'''''
eg. If the following produce any output, attach the results (don't post inline)
eg. If the following produce any output, attach the results (don't post inline)
'''''or say''''', no custom-templates or contribs.
'''''or say''''', no custom-templates or contribs.
'''ORIGINAL PROBLEM''': '''''State what you were trying to do.'''''
'''ORIGINAL PROBLEM''': '''''State what you were trying to do.'''''
'''STEPS TO REPRODUCE''': '''''As accurately and exactly as possible state what you did to get your problem.'''''
'''STEPS TO REPRODUCE''': '''''As accurately and exactly as possible state what you did to get your problem.'''''
'''ACTUAL RESULTS''': '''''List what you got as a result.'''''
'''ACTUAL RESULTS''': '''''List what you got as a result.'''''
'''EXPECTED RESULTS''': '''''List what you expected to happen.'''''
'''EXPECTED RESULTS''': '''''List what you expected to happen.'''''
'''Attachment:''' This is used to attach (not post in line) any logs or results of command line queries such as the examples listed in "Modifications" above.
Finally, when satisfied with your entries, submit your bug report by pressing the '''COMMIT''' button.
===Verifying Bugs===
===Verifying Bugs===