| Version 1 (modified by , 6 years ago) ( diff ) |
|---|
Languages:
- Ελληνικά
- English
- Esperanto
- français
- norsk bokmål
- Nederlands
Table of Contents
Ticket system guidelines
The aim of the JOSM ticket system is to report bugs, suggest enhancements/improvements or submit patches regarding JOSM and its plugins.
- Everyone (even anonymous) is allowed to create tickets, comment on tickets and add attachments.
- Bug reports must be created by using the JOSM internal feature Help -> Report Bug.
- Don't set the milestone, this is permitted to JOSM core developpers only.
- Don't reopen resolved tickets of previous milestones. Create a new ticket instead and reference related previous tickets.
The meaning of some fields of a ticket
- Version:
- tested - the bug is present already in the current tested version of JOSM
- latest - the bug is present only in the current latest version of JOSM but not in the current tested version (i.e. it is a regression of the current release cycle)
- if not sure, just leave it empty
- Priority:
- blocker - JOSM doesn't work at all for a majority of users
- critical - a large number of users is affected (we're getting a lot of duplicate reports), usually results in a hotfix and manual latest compilation
- major - more important issue affecting a group of users
- normal - default priority, used for most tickets
- minor - changes with very little benefit, also little typos (except in osm keys or values)
- trivial - ?
See also
Back to Developers Guide
Note:
See TracWiki
for help on using the wiki.


