> For the complete documentation index, see [llms.txt](https://docs.portainer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portainer.io/sts/faqs/contributing/how-do-you-decide-which-bugs-and-features-to-work-on-first.md). # 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](https://github.com/orgs/portainer/discussions/categories/ideas) and [bugs](https://github.com/portainer/portainer/issues) lists are long and at times seem never ending. 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.\ \ **Our process** When prioritizing which feature requests to work on, if we answer "yes" to any of the following questions, we will be more likely to 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 upvotes in GitHub? **Feature parity**\ We don't automatically maintain feature parity with Docker or Kubernetes. When a new 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 stable and 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 (using the upvote functionality of GitHub discussions). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.portainer.io/sts/faqs/contributing/how-do-you-decide-which-bugs-and-features-to-work-on-first.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.