Sometimes what you perceive as a bug in MAAS is actually by design. On other occasions, you might wish for a feature that’s yet to be added. In either case, the solution is a feature request.
If you’re certain about your request, go ahead and create a new Features post on Discourse^.
If you have an idea but aren’t sure how to present it, keep reading. This article is here to guide you.
We strive to deliver in-demand features, as evidenced by our last feature poll^. We actually implemented the top-voted feature in MAAS 3.1. However, we can’t promise to fulfil every request or do so immediately. The point is: your feedback matters.
For a feature to make it onto our roadmap, it usually shares some attributes:
- Addresses a common problem.
- Is grounded in well-articulated needs and real-world scenarios.
- Ideally comes with 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 higher the likelihood we’ll consider it for future releases. We might not guarantee every feature, but we’re definitely listening.