[[TracNav]]

= Reporting bugs =

Please report bugs using our bug tracking system called [http://www.trex.informatik.uni-goettingen.de/jira/secure/Dashboard.jspa JIRA]. Do not use the mailing list for this purpose.

Before filing a new bug, please check whether a similar bug has been filed before.
This can be easily achieved using the ''QUICK SEARCH'' feature on the upper right hand side of the [http://www.trex.informatik.uni-goettingen.de/jira/browse/TTC JIRA window].
A more detailed search can be performed using ''[http://www.trex.informatik.uni-goettingen.de/jira/secure/IssueNavigator.jspa FIND ISSUES]''.

While you may browse the issue data base anonymously, you need to signup for an account on the log in page of the [http://www.trex.informatik.uni-goettingen.de/jira/browse/TTC JIRA system] to be able to create a new issue report.

Once you are sure that you have found a new bug, use ''CREATE NEW ISSUE'' and follow the instructions.
 * In addition to the ''Bug'' issue type, you may also suggest an ''Improvement'' or ''New Feature'' as issue type. [[BR]] (All other types are probably only relevant for developers: e.g. the type ''task'' shall only be used for internal changes, e.g. to the Web site, because fixed ''task''s do not appear in the release notes.)
 * Use a descriptive ''Summary''.
 * Provide in the ''Description'' section a more detailed description of the bug including instructions how to reproduce the bug. 
 * The ''Priority'' can be left at it's default.
 * Concerning the ''Component/s'' to which your report relates, you can make a guess, e.g. ''Core'' if editing capabilities are concerned, ''Refactoring'' if refactoring are concerned, and ''Automated Code Review'' if marker generation and metrics are concerned. In case of doubt, leave it empty.
 * In the ''Affects Version/s'' you should select the version number displayed in the TRex ''Help''->''About''->''Feature Details'' dialog. [[BR]] (If you are reporting a bug for a nightly build, this means that you will use the version number of the upcoming version.)
 * The fields ''Fix Version/s'', ''Original Estimate'' are usually only for developers and should be left empty. 

If you like later-on to add further information you can use the ''Comment'' field at any time.

As any mature bug report system, JIRA might look overwhelming when using the first time. For documentation on using JIRA, please click on one of the yellow help bubbles inside JIRA or refer to the [http://www.atlassian.com/software/jira/docs/latest/ JIRA documentation].