Report a Bug
#BugReportDecidim Let's test Decidim and report bugs together
This bug report space no longer works, if you want to report a bug you must go to GitHub, before you have to read the instruccions:
Did you find a bug?
-
Do not open up a GitHub issue if the bug is a security vulnerability in Decidim, and instead send us an email to security [at] decidim.org. See full security policy.
-
Ensure the bug was not already reported by searching on GitHub under Issues
- If you’re unable to find an open issue addressing the problem, open a new one on GitHub. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
About this process
Welcome to the Bug Reporting Process. If you directly want to report a bug go to the "I found a bug!" section.
Every new release of Decidim software includes new features and improvements. This process helps us identify the bugs and report them quickly to be solved. Would you help us find new bugs? :)
We need you! We need all kind of users to report all kinds of bugs so we can make Decidim better. If you haven't found any bug yet but you are ready to contribute, we suggest you test the new functionalities to actively search for bugs. The best way to do so is to check out the latest release changelog. Here you can find a list of new features and you can start testing them. There are two spaces where you can do so: here at the meta.decidim community site (where you might not have admin privileges) or you can also do it on our Demo site, where you can freely explore admin panels and activate all kinds of functionalities.
Share: