GRASS: Bugs and feature requests

GRASS Trackers - Tracking bugs and feature requests

The bugtracking system to support the ongoing community development of GRASS GIS has been moved to the new GRASS-trac bug/issue tracking system hosted by the OSGeo Foundation. You 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.

The new GRASS-trac is available for public view, but in order to be able to post and use all their features, you need to setup an account at OSGeo.

All trackers' new submissions will be automatically forwarded to the GRASS 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.

For questions about using the GRASS bug trackers please contact
Maciej Sieczka [tutey <at> o2 <dot> pl].

Please consider the following when submitting bugs or feature requests:

• Please only report bugs if using at least the current stable release version. 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 example dataset).
• Report only a single bug with each request.
• Before reporting a bug, please check that it is currently unknown:
  • New GRASS-trac bug tracking system search page
  • Old GForge bug tracker search page
  • All information in the old bug and wish tracking system can still be queried here:
    [ GRASS 6 bugs only | GRASS 6 wishes only | All open requests | All resolved requests | Search the Bug Report System: ]
    (search may be incomplete)

PROCEED to the NEW bug and feature tracker...