How to write tickets

The goal of creating a ticket is that it is being processed. One is tempted to write a ticket quickly saying little about the actual task or issue. But this is bad, because probably nobody will ever process it or even if it's processed it might not be clear if the job has actually been completed. No matter what issue tracking software one is using (Bugzilla, Trac, Pivotal, Jira or whatever), a ticket needs to be written by oneself. The following questions and hints will hopefully help to write tickets such that the actual tasks will be completed successfully.

General hints and questions

  • Do not add several tasks in one ticket, but rather make for each task one ticket.

Fixing stuff

  • Do not just describe what is currently broken ("The favicon is not displayed"), but also describe how it should work ("This particular favicon should be displayed").


Your comments are much appreciated

Is the content of this page unclear or you think it could be improved? Please add a comment and we will try to improve it accordingly.