A great request explains exactly what it is you're asking for, provides the context of the request, any use cases, and how you're currently overcoming the problem.
Below are some useful pointers for when it comes to submitting a request
Title: This should be clear and to the point. Avoid vague language and jargon as this needs to be instantly understandable.
Description: This is the meat of the request, and should contain all the information that the Product team needs to make a decision. You should include what the problem is that you're trying to solve, any context that is necessary for understanding, examples and use cases, and how you currently solve the problem.
Files: Files should be uploaded to add clarity or communicate something that is hard to put into the description. Screenshots should be clear and high resolution.
Modules: If the request is only relevant to a certain module, then make sure to assign it to the correct one.
Tags: Tags help organize the feedback, and so adding relevant tags is a massive aid for the Product team.
Effort: If you're in a position to accurately estimate the effort your request will require, then go ahead and add it in. If you're unsure, leave it for the Product team or Devs to decide.
Visibility: If you're making a private request, then be sure to change the visibility of your request before you submit it.
- Always try to focus on the problem and not the solution - that's the Product team's job.
- The more detail the better. Don't be scared of writing too much.
- But equally, don't waffle on. If something isn't relevant to the request, leave it out.