I think I've found a bug in Plone. Where should I report it?

Security-Related Bugs


Security-related bugs should be reported only via email to security@plone.org. Security issues in Plone or its add-ons can be reported this way, and the Security Team will contact the relevant maintainer if necessary.

Bugs That Are Not Security-Related

All other Plone bugs should be reported via a ticket (issue) in an appropriate on-line tracker. For best results, you will need to do some research to figure out which such tracker is most appropriate for your situation. This is because development of core Plone components, third-party products (add-ons / plugins), other third-party packages, and Plone documentation are all handled by different teams around the world, each with their own work schedules and development infrastructure. You should anticipate needing to remain engaged with the issue after reporting -- to include working on the problem yourself and offering a patch if possible -- in order to improve the likelihood of a prompt resolution.

Bugs in Plone Core

If you think your bug involves a core component of Plone, check to see if that component has its own repository at https://github.com/plone. If it does, use the component's issue tracker to submit your bug report. If the component does not have its own repository there, submit your bug report in the catch-all CMFPlone tracker on GitHub.

Note: after figuring out where to post your report, but before doing so, please search the issue tracker to ensure this issue hasn't already been reported and that it hasn't already been fixed in a later version of the component.

Bugs in Plone Add-ons 

Bugs in Plone add-ons should be reported in their repository's issue tracker, which is usually listed on the add-on's PyPi page or in the add-on's listing in the Plone.org add-ons. In some cases, you may need to use a web search engine or ask for guidance in the Plone IRC channel or in one of the Plone discussion forums.

Bugs in Plone Documentation

If the problem is in the Plone documentation, report it in the documentation tracker.

If the problem is in the Plone training manuals, report it in the training issue tracker.



The following legacy recommendations need to be checked and updated. Right now they point people into the legacy tracker, which may no longer be correct:

If the issue is related to plone.org (this website), please file the ticket under the component "Website".

Internationalization bugs (i18n) should be filed in the Plone issue tracker under the Internationalization component.