Make sure your card is in the “Proposed Features” List
Feature idea guideline
The subject of the feature request should be as concise and crisp as possible.
This section has the names and email details of the proposer. We need your email details as we might have to come back to you with questions
This section consists of 3 parts. This is the most important part and helps us to understand the feature request and also help us to decide its priority. Most times a feature for an ongoing implementation takes priority over a feature that has no immediate usage
The feature description should be concise and expressive.
Describe the current behaviour if it is to be changed by the request.
Mention the reason why the change is relevant. Describe the associated use case.
2. Why is this feature important?
3. Target users of this feature: Who will use this feature
**Stakeholders and Analysis**
Specific implementations or clients who would be early adopters/testers of this feature:
We prioritise features that are likely to be used over those that we think would be great to have in the product. We do this primarily to make sure what we are working on is valuable and also the product benefits from the feedback from users.
Links to any technical analysis, business analysis or estimation of the feature (optional):
Here usually people link to the talk thread where our feature discussions take place. See the example below
Resources that you or your organization can provide to support the development of this feature (examples: software developers; business analysts; subject matter experts or end-users; funding). More support from you will increase our ability to develop this feature: