Reporting a Bug

Important!

Before submitting anything, be sure it is really a bug :

• Are you running the latest version? The Downloads page has both the latest and nightly builds of OpenMRS.
• Has it been fixed or is it being worked on now?
  • Search for the a similar bug ticket.
  • Search the forum.
  • Search the implementers archive and the Search the developers archive

If and only if you are unable to find any other similar reports, you may create a new ticket for the bug. Read all about creating tickets on our tickets page.

In your bug ticket...

Include as much pertinent information as possible:

1. A full stack trace if applicable.
2. Your OpenMRS code version and database version
3. Whether or not you are using custom templates/stylesheets/messages
4. A clear description of how to recreate the error

Assigning the ticket:

• If you have been discussing the bug with a developer, choose their username
• If your ticket belongs in a specific component (other than the generic "OpenMRS Code Base"), it is probably safe to leave Assign To blank.
• If your ticket is using the generic OpenMRS Code Base component, you should choose a developer. That developer can reassign the ticket if need be.