How do I...File bug reports about Deki Wiki?

Before you file issues

If you've found an issue that many people are having on the forums, chances are somebody's already filed it on Mantis. Do a quick scan of the unassigned bugs on Mantis to see if your issue is already there. You can leave a comment in there saying you have the same issue (that'll give us an idea of the widespread severity). If not, click "Report Issue" to file a bug report.

Filing the issue

As a general rule of thumb: poorly written bug reports will be prioritized below well-written bug reports. If it looks like you spent 5 seconds writing a bug report ("editing is broken"), we will probably spend 5 seconds looking at the bug report :)

Here is a checklist of items you should include in your bug report: (or you can use the template below!)

• Your Deki Wiki version and installation information (VM or source? If source, what OS?)
• Any and all error outputs (does the UI output an error? Do you see any errors in the API or Apache logs?)
• Screenshots are a huge plus!
• If the bug is UI-related, does it appear in a different browser? Which browser are you using?
• Repro steps - be very specific; your bug may be affected by where you're working in the wiki (user namespace? main namespace?), whose user account you're using (is it an admin? what are its permission flags?)
• Expected behavior - what did you expect to happen? How did Deki Wiki behave differently?

Here's an example of a real bug report from our internal QA team. The bug report, although not lengthy, had enough information to allow the developer to identify the problem and apply a fix in a timely manner.

The bug process

Every day, bugs are triaged to developers. If a bug remains unassigned, check to see if a MT developer left a comment asking for more information. If the bug becomes assigned, then it's been accepted and will be fixed (hopefully for an upcoming release). You can use Mantis' "watch" feature to track the progress of a bug. After a bug's been assigned to a developer, the developer will fix and change the status to resolved. After the bug has been fixed, it will be assigned to a QA tester for verification. Once the QA tester have validated the fix, the bug report status will be changed to closed and will be in the next release.

Bug report template

Use this template to facilitate the creation of new bug reports. Sections in parenthesis should be filled out in the bug report.

Incident:
(What happened?)

Expected:
(What should have happened?)

DekiWiki Version:
(View Tools > About in your wiki)

VM/Source Install:
(Are you running the VM or Source with what OS?)

How To Repro:
(- Login to Control Panel)
(- Do something else...)