How-To Report a Bug on the Bug Tracker
To report a bug in the Joomla! bug trackers, one has to create an "artefact".
Once this artefact is created, the developers will check the validity of it and act accordingly.
1. Register an Account at joomlacode.orghttp://joomlacode.org/gf/account/?action=UserAdd
2. Access the joomla! development bug tracker.Joomla! 1.5 Bug Tracker
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=32
Joomla! 1.0 Bug Tracker http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=5782 3. Check to see if the bug you want to report is already reported.
A series of filters display the artifacts.
Make sure Priority is set to "Any", Assignee to "Any" and Status to "Any", other filters to nothing.
Mouse over the title of the artefacts to check their contents.
If the issue you are experiencing is not already reported, click on the bottom-right Button "Add new Tracker Item".
4. A new screen will display and there, the more information you give, the easier it is for the developers.Fill as many fields as you can.
| Priority | Use the default "Medium" except if you know the code enough to make another choice. |
|---|
| PHP | Choose the version you are testing on. You can find this information by
clicking the Menu "Help"->"System Info" in the Administrator back-end of Joomla!
|
|---|
Estimated Time
| Leave this blank. |
|---|
| Build | Type here the #SVN number if you know it, or Nightly Build date, or Version used if using a Released version. |
|---|
| Browser | Self-explanatory. |
|---|
| Database | The version of MySQL is also available in "Help" -> "System Info". |
|---|
| Status | Leave this to "Open". |
|---|
Percent Complete
| Leave this blank. |
|---|
| Category | This one is more tricky. Use "Administration" if you do not know better. |
|---|
| Customer | Use "User" if the issue is in front-end, "Developer" if the issue
concerns an extension you are developing, "Administrator" in other
cases. |
|---|
Web Server
| The version/server type is also available in "Help" -> "System Info".
|
|---|
5. SummaryDescribe in a few words the issues you are having. It is generally a good idea to use existing artefacts as examples if this is your first time reporting a bug.
Examples:
Front-end: Warning such and such.
or
Back-end: Unable to save article when "nameofplugin" is published.
Note: Take care to be descriptive in your summary as this is the first thing the developers will see when they are perusing the tracker for something to fix. 6. DetailsThis is the most important part of reporting the bug.
Describe here step by step how you got the error you are noticing.
The more details, the better.
Examples:
A. When I enabled "nameofplugin", no article can be saved. These are the plugins enabled at the same time. SEF is on (or Off). My site is in a sub-folder. I also remark that... etc. Files such and such are the issues IMHO (if you know what you are talking about).
B. Back-end. Clicking on "menu_name" Menu. Page opened is blank. Any other menu works OK. etc.
C. Back-end. Content -> Article Manager (The -> means you click on a submenu). Editing a non-categorized Article. Section dropdown does not display the sections available (or Editor is going over the right column for parameters, or Can't save article after changing a parameter [describe parameter], etc.
D. I have such an such issue when doing this and that. By changing this code [code proposed] in file [name and hierarchy of file], line(s) #, the issue looks solved on my settings.
7. To better describe the issue or/and propose a fix, you can add attachments to the artefact you are creating by using the "Browse" buttons at the bottom of the screen.A screen capture of the page(s) concerned helps a lot. If you can, try to optimise the size of the image through an image editor.
If you know what part(s) of the code base to change, a patch [patches] or a full file where your changes are WELL shown will help the developers to solve the problem quicker.
8. Click the "Add" button at bottom-left of screen. You will receive an e-mail confirming that you posted the artefact. When someone comments or asks for supplementary details or solves the issue, you will receive a notification e-mail and may reply if needed.
|
