---
title: How to request features
description: Canonical makes open source secure, reliable and easy to use, providing
  support for Ubuntu and a portfolio of enterprise-grade technologies. Founded in
  2004, Canonical operates globally with team members in over 80 countries.
url: https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md
---

*Submit*

# How to request features

User feedback drives MAAS development. Feature requests help us understand what real-world problems you need solved. While we cannot guarantee every request will be implemented, clear, well-structured requests increase the chance of adoption.

## [Step 1 – Choose your path](https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md#p-7636-step-1-choose-your-path)

* Have a clear request? Post directly in [Discourse: Features](https://discourse.maas.io/c/features/15).
* Exploring an idea? Use the checklist below to shape it before posting.

## [Step 2 – Shape your feature request](https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md#p-7636-step-2-shape-your-feature-request)

A strong feature request:

* Addresses a common problem – not just a one-off scenario.
* Describes needs in real-world terms – what you’re trying to achieve.
* Includes user stories and use cases – concrete examples.
* Explains the “what” and the “how” – what you need, and how you expect it to work.
* Provides contact details – so we can follow up.

## [Step 3 – Post your request](https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md#p-7636-step-3-post-your-request)

1. Go to [MAAS Discourse: Features](https://discourse.maas.io/c/features/15).
2. Click New Topic.
3. Add a clear title and summary.
4. Paste your prepared details.
5. Submit.

## [Safety nets](https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md#p-7636-safety-nets)

* Not sure if it’s already requested? Search the Features category first.
* Concerned about sharing details? Remove any sensitive information before posting.
* Need help drafting? Start a discussion in the [Users category](https://discourse.maas.io/c/users) to refine your idea.

## [Next steps](https://canonical-com-2934.demos.haus/maas/docs/how-to-request-features?format=md#p-7636-next-steps)

* [Report a bug](https://canonical.com/maas/docs/how-to-report-and-review-bugs)
* [Troubleshooting MAAS](https://canonical.com/maas/docs/maas-troubleshooting-guide)

If you’re certain about your request, go ahead and create a new Features post on [Discourse](https://discourse.maas.io/c/features/15). If you have an idea but are not sure how to present it, make sure that your feature idea:

* Addresses a common problem.
* Clearly describes well-articulated needs and real-world scenarios.
* Includes detailed user stories and use cases.
* Is clearly described, allowing us to understand both the ‘what’ and the ‘how’.
* Includes contact details for follow-up questions.

The more compelling your case, the greater the chances it will appear in a future release.

---

[Previous

Security](https://canonical-com-2934.demos.haus/maas/docs/about-maas-security)

Last updated 1 year, 1 month ago. [Help improve this document in the forum](https://discourse.maas.io/t/how-to-request-features/4447).
