Got a GRASS GIS software problem or enhancement wish?Bug reports and wishes can be submitted in the GRASS GIS bugtracking system (GRASS-trac).
This requires you to setup a personal account (Userid) at OSGeo.
All trackers' new submissions will be automatically forwarded to the GRASS GIS development mailing list. Submissions and all followup traffic will be stored in the tracker and forwarded only to parties discussing the ticket. However, any project member can "monitor" a ticket, or a whole tracker, in order to receive all the related traffic (see Trac manual).
The following trackers are available:
- 'defects' for bugs, and "bad features";
- 'enhancement' for wishes;
- 'task' for different tasks.
Some considerationsPlease consider the following when submitting bugs or feature requests:
- Check if the bug is still present in at least the current stable release version before reporting. If you use an older version, please consider upgrading.
- Make sure that the developers have all the information needed to recreate the bug (e.g. explain how to reproduce the bug using the Spearfish or North Carolina example dataset).
- Report only a single bug with each request.
- Before reporting a bug, please check that it is yet unknown: GRASS-trac bug tracking system search page
- Read How to Report Bugs Effectively (several languages) by Simon Tatham.
Legacy bugtrackersYou can still access our old GForge system hosted by Intevation GmbH, Germany or the old RT bugtracking system, to examine both previously resolved issues, and those that were still in progress as the new system was released. Note that many bugs mentioned there have been fixed since then.
- Old GForge bug tracker search page
- All information in the old, outdated bug and wish tracking system can still be queried here (many bugs will have been fixed since then):
[ GRASS 6 bugs only | GRASS 6 wishes only | All open requests | All resolved requests| Search the Bug Report System: ]
Development >> Bug tracking | Last change: 22-Aug-2016