Version 3 (modified by Luke, 9 years ago) (diff)

import basic guidelines from first page and clean up a bit

Find our bugtracker at

Important bug reporting guidelines

  1. State the version of the buggy application.
  2. Fill all the "user" fields in the bug reporting page (for example: do set component, don't set milestone)
  3. Choose a descriptive short summary (topic) of the bug. Don't make it too short, it should be informative.
  4. Don't make private jokes in bug reports summaries (i.e, if you want openMooCow to be added to feed, don't write "The moko needs a cow" it's both not funny, and hard for us to understand, choosing "Adding openmoocow to feed" is more appropriate.
  5. Being polite is good and important, though not in the bug summary (topic) as it's just hard to read.
  6. Please add as much info as you can to the description of the bug.

Check for duplicate

Check if the bug is already reported. If no, add a ticket, be as much precise as you can in the title and the description (in what circumstances it's append, ...)

Include contextual information

Please attach the corresponding logs to the ticket, e.g.:

Also attach screenshots if they are usefull.

Please don't upload logs on pastebin or link screenshots from scap, as they will expire after some time!