If you find a bug, please tell us so we can triage it. All bugs are managed in this GitHub repo. When you click through, our template makes it easy to record all of the details. Before you report a bug, please check our list of open bugs in case someone else has already reported it.
You can request new features in this GitHub repo. When you click through, our template makes it easy to record all of the details. We also publish a list of open feature requests in GitHub. Check to see if someone has already requested the feature you want, and give it a thumbs up.
How do you decide which bugs and features to work on first?
Here at Portainer, we encourage feedback from our customers, and we truly value our user community. That being said, our features and bugs lists are long and at times seem neverending. Our decision-making process aims to balance user needs with the reality of Portainer's limited time and resources. Despite our best intentions, we know that at times we will disappoint some of you.
When prioritizing which feature requests to work on, if we answer "yes" to any of the following questions, we will add that feature:
Will it address a security vulnerability or potential exploitation?
Will it have a wide appeal?
Will it benefit professional Portainer users?
Does the request have at least 20 thumbs-ups or hearts in GitHub?
We don't automatically maintain feature parity with Docker. When a new Docker CE feature comes out, we ask the same four questions before deciding whether or not to add it to Portainer. And we only add support for features that we feel are in high demand.
The importance of voting
We receive many feature requests for issues that exist only because of a specific use case. These stay pending until we identify an opportunity, or our community indicates its demand by voting (thumbs-up).
How do I log a support ticket?
Fast facts about Portainer support
Only Portainer Business (BE) customers can log tickets directly with Portainer.