Reporting issues

Owned by Former user (Deleted)
Last updated: May 31, 2011Version comment
2 min read

Bug reports

Please supply the most detailed information as possible. Shouting at as that:

Thing XXX does not work !!!

will not help us at all. It probably will work on our installation. We actually do test our software you know :)

First of all search the issue tracker is someone didn't already report a similar bug. Type a few words that others might of used to describe he bug in the search bar (upper right corner). If you find a bug with the same behavior please comment on it and add more information to it. Voting on it will also motivate developers to solve it faster.

But if you don't find something similar please create a new issue.

In most cases the bug is related to some specific data that you entered previously, your system configuration or to the specific version of the operating system and browser that you are using. The more we know about these things the sooner we can fix the bug.

An ideal bug report should have:

  • a nice title that summarizes the bug,
  • a detailed step-by-step description what did you do, what result did you expect and what happened instead,
  • browser name and version number, on what operating systems was the browser running and did the server qcadoo MES application run on a different one
  • a screenshot then the bug happened
  • the version your qcadoo MES application
  • information from systems logs - this will help the most !
    • if you have access to the server then zip the logs directory right after the error happened and just attach it to the issue
    • if you don't please see if there is something called "stack-trace" in the error message. If there is please click on it to expand it and copy its content to the issue report. This might look like random text but it is a blessing to developers

After all of this please stay tunned. The developers may ask you more questions to get the jobs done. Bug fixing is not an easy thing. Especially when a developer can't reproduce the bug on his machine.

In what order to issues get solved

In an open source project you can't really tell for sure :) Some developers may do your issue because they have a problem with it too. Other may feel that other issues are more important for them.

All we can say for sure is by which pattern developers hired by Qcadoo Limited work. We also encourage other developers to follow it.

  • The Fix version attribute is the best clue. It means that some developers have said that they will solve the issue before the declared release.
  • The Priority usually says in which order the tasks will be solved for the given Fix version. Issues with small Priority may sometimes not make it to the declared Fix version
  • User Votes are very important to us and determine the Fix version and Priority