Overview

trac allows us to keep "trac" of changes, defects, enhancements, etc. for the OpenMRS project. Work is described within a ticket. If you find a defect or would like an enhancement, you can create a new ticket.

Creating a ticket

Click on the New Ticket tab (you must be logged in to trac to see this tab). Describe the defect/enhancement and label it as such. Every ticket should be associated with a component and a milestone. Tickets are assigned to someone and can be followed by others by adding their username(s) to the CC field. The person creating the ticket and the person assigned will always get e-mail; others must be in the CC field to get e-mailed with any changes to the ticket.

Following your tickets

You can look under View Tickets and select My Tickets or -- better yet -- go there once to get the link for the RSS feed at the bottom and load that RSS link into an RSS reader, a Firefox Live Bookmark, or your Google personal homepage.

Don't forget to close your tickets when done and, if applicable -- please refer to the revision -- e.g., [123] -- containing the fix when closing a ticket.

Helpful formatting

There is a link to [WikiFormatting] when creating or editing a ticket for quick reference.

Always preview before submitting to make sure your formatting is okay.

• When insert code or SQL, put {{{ and }}} around the text -- e.g.,
  
  {{{
  SELECT * FROM MYTABLE
  }}}}
  
  becomes

SELECT * FROM MYTABLE

• CamelCase is interpreted as a trac wiki link -- e.g., CamelCase. This can be a problem with Java references. To keep text from becoming a link, prefix it with an exclamation mark (!) -- i.e., !CamelCase yields CamelCase

• [123] makes a link to a revision number -- e.g., [123]

• #23 makes a link to another ticket -- e.g., #23

• [http://www.google.com Google] makes an external link -- e.g., Google