Issue tracker

The issue tracker is not a support forum

If you have questions, or are having a problem please ask on the Discourse user group first, also make sure you read the guidelines before posting.
It's best to open a bug report only when the issue has been confirmed by some third party, we often have to close down tickets that are created just out of a misunderstanding or a misconfiguration.

Asking for new improvements and new features

If you are looking for a new feature, or an improvement on existing functionality, we encourage you to open a ticket only after securing the necessary development resources. Please to read this guide to learn how to best deal with this type of requests.

Reporting a security vulnerability

If you encounter a security vulnerability in GeoServer please take care to report in a responsible fashion:

1. Keep exploit details out of public forums, mailing lists, and issue tracker.
2. There are two options to report a security vulnerability:
   • Please send an email directly to the volunteers on the private geoserver-security@lists.osgeo.org mailing list. Provide information about the security vulnerability you might have found in your email.
     This is a moderated list: send directly to the address; your email will be moderated; and eventually shared with volunteers.
   • To report via GitHub:
     Navigate to security page, use link for Private vulnerability reporting.
     For more information see GitHub documentation.
3. There is no expected response time. Be prepared to work with geoserver-security email list volunteers on a solution.
4. Keep in mind participants are volunteering their time, an extensive fix may require fundraising/resources.

Refer to the GeoServer Security policy.

Access to the issue tracker

First off, make sure what you're reporting is a bug. If you have a question, a improvement/feature request, or you're unsure if you're dealing with a bug, ask on the Discourse user group instead (see above).
Also, make sure the issue is not already known by searching the bug tracker, if you find an existing ticket for the issue you can comment on it directly, instead of opening a new one.

• Issue Tracker home page
• Quick search unresolved GeoServer issues:
  
  In the example v:2.26.0 is used search stable version, c:wms is used to search only the WMS component.

To comment on a issue, or create a new one, you must be logged in. If you do not have a login you can sign up here.
Once you are logged in there should be a link at the top of the page to 'CREATE'. You will also be able to comment on and watch individual issues.