Before open a new bug ticket:

.. warning:: Under construction page

- Please, try to use English.

- If the bug has been found by exploratory testing, it's necessary to do some research in order to find the real problem, ruling out variables (See `Exploratory testing good practice `_).

- Once you know the real problem you should check if there is a bug already documented about it by searching in the bug tracker. (See `How to search in Osor trackers `_).

- If a similar ticket is already documented, please consider to add some useful information.

- In the other hand, if the bug isn't documented yet compile all the information needed to open a new bug ticket:

  * **gvSIG version number and package build number** [1]_ (see menu “About...” in gvSIG).

  * **Extension version number** [1]_ [2]_ (see menu “About...” in gvSIG).

  * **Operative system** [1]_

  * **Log file** [1]_ [3]_. (see `Where to find the gvSIG log file `_ ).

  * Data sets [3]_ .

  * Screen shots [3]_ .

.. [1] Mandatory information.
.. [2] Only if the error is related with a functionality that belongs to any installed extension.
.. [3] See point called `Attach files`_ inside the document `OSOR tracker help`_ to get more information about how to attach files in a ticket.

.. _`Attach files` : /web/production/proyectos/testing/docs/procedimientostesteo/Infromacionrelevantetesteo/ayuda-para-el-tracker-de-osor/#attach-files
.. _`OSOR tracker help` : /web/production/proyectos/testing/docs/procedimientostesteo/Infromacionrelevantetesteo/ayuda-para-el-tracker-de-osor/