We believe that the best way to build software is to do it in close collaboration with the people who use it.
We do our best to implement as many Ideas as we can. Our Product team will evaluate all submitted ideas in a timely manner and will disposition each into one of the following categories:
- Will integrate into the product roadmap
- Further research is needed
- Unlikely to implement
Raising a Public Feature Request
If you're able to raise a Public feature request please head on over to Chef-Ideas where you can sign up and submit your feature request in our public portal. This is preferable because it provides visibility and allows users with identical requirements to vote for your request and ensure it aggregates priority in the product roadmap.
If you have raised or observed a Feature request which already covers/complements your needs in Chef-Ideas you can reference this in the public feature request field in the feature request form. This is useful in the event your wish to signal that a request has value for your business but you cannot do so publically.
Raising a Private Feature Request
If you are raising feature requests as trackable tickets through Chef Support, then we ask that they are correctly identified by choosing the "Feature Request" form type from the issue drop down menu:
Submission Data
Subject - A summary of the feature request.
Description - A description of the feature request, including:
- The problem for which you are solving
- Benefits of implementing the idea
- Any additional context you think necessary
Public Feature Request: If an idea already captures/complements the feature request your are submitting please include this so we can aggregate your interest to it. This needs to the the URL of the idea as it is stated in our Chef Ideas portal
Product - the product you wish to see the feature request implemented against
Business Value - the associated value this has to your business needs
Attachments - If necessary, provide UI screenshots to describe the problem the feature request would address. Feel free to annotate these for the product team's benefit.
Comments
0 comments
Article is closed for comments.