Feature Request Summary: 

By means of a pre-filled template, end users should be clearly encouraged to provide information in a structured form.

Description/Use Cases: 

We use Zendesk Gather to collect feature requests from our customers and partners.
Our implementation is almost identical to what Zendesk does itself and in one community topic we have pinned a post with a template for our customers and partners to use.

Unfortunately, we see in practice that only very, very few customers and partners use the template.
We would like to motivate them to use the template more often.

Our suggestion is that it is possible to deposit one (text) template per Gather community topic and the end users only need to add/update their content to the pre-filled template.

Business impact of limitation or missing feature:

Compared to competitor solutions (Aha! / UserVoice), we see that unfortunately with Zendesk Gather we get mostly very unstructured feature requests submitted.
As a result, product owners and product managers do not value Zendesk Gather compared to competitive solutions because it is more inefficient for them to extract the necessary information. Alternatively, they have to ask multiple times until they arrive at a similar level of information.
Of course, like other companies, we want to use our costly resource Product Owner and Product Manager as efficiently as possible - this should be supported by an enterprise tool like Zendesk Gather.

Other necessary information or resources:

Just take a look at the "workaround" used by Zendesk itself.