In any software package you may encounter the occasional
flaw with a feature or the documentation. Please bring these
flaws, or bugs, to the attention of the Connexions team
with the Report a Bug link, which is located
on the Connexions Home page
and on other Connexions web pages in the Personal Toolbar.
To report a bug, use the following steps:
- Click on the Report a Bug link.
The Bug Report
Submission Form displays.
- Enter your name.
- Enter your e-mail address.
- Enter the module ID, if the error occurred while accessing
a module. This is a number, for example m99999. If you do not know
the module number, view the module and display its "About" or
"History" pages. The module's ID is listed on those pages.
- Specify the nature of the error. Click the down arrow in
the "Type" field and select the appropriate entry from the
drop-down menu.
- Specify the impact of the error. Click the down arrow in the
"Severity" field and select the appropriate entry from the drop-down
menu.
- Enter a one-line summary of the bug in the "Task Title"
field.
- Enter an explanation of the circumstances of the error in
the "Description" field. Include your actions and the system's
actions that led up to the error condition. If possible, include
step-by-step instructions for reproducing the bug.
- Click
Submit Bug to enter the bug into
the Connexions tracking system.
Reset clears your entries on the form.
Here are some tips for submitting error reports that will help
us fix the bugs quickly.
- First, do not close the error message display
until you have captured some information from it to include in your
bug report. The error message contains important information. If you
have left it to go to the
Bug Report Submission
Form or to a Help
page, use the Back function on your browser to redisplay the error
message.
- Include a copy of the error page. If the error displays an
actual error message, please copy the text of that message and paste
it into the bug report. It is even better to include the HTML source
of the error message -- some of our systems include important
information in HTML comments. While the error message is displaying,
right click your mouse and select the
View Source or
View Page Source option, depending on your browser, to
display the HTML for the page. Then you can copy the HTML information
and paste it into the bug report. - More information is always helpful. For a new system like
Connexions, full descriptions of errors are very useful. If your
error involved a specific module, include the name of the module.
If you were in the editing interface, include the workgroup and/or
module with which you were working. If you were using the Course
Composer, mention which course you were working with, and so forth.
Include the exact URL of the page on which the error occurred.
Always include a description of what you were doing, if you can.