[Feature]Automatic structure for Feature requests/bug repports

In category: Site Bug Reports & Feature Requests

Requested feature overview description.
Automatic structuring when suggesting a Feature request/bug repport in the style of alias/implication.

It would automatically add [bug] or [feature] in the title and add fields for, or auto-paste, relevant sub-titles.

Why would it be useful?
Simplifying bug repports/feature requests

What part(s) of the site page(s) are affected?
Site bug reports and feature requests


yeah please. people seem rarely understand what they are supposed to do with the current form so it would be easier to give for example simple literal form where user only has to fill the blanks and site spits out formatted forum post


By the way, the current templates could be improved.

Bug Report Template:

Bug overview description.
What part(s) of the site page(s) are affected?
What is the expected behavior?
What actual behavior is given instead?
Time of incident (if applicable).
Can you reproduce the bug every time?
What steps did you take to replicate this bug?
Errors or other messages returned (if any).

1. The usual order is "steps, expected, actual", "expected, actual, time, reproducible, steps" is used instead, which makes no sense.
2. The key parts of any bug report are "steps, expected, actual", so they should come first. Things like "time" (too specific?) and error messages (should be put in "actual", but can be used as a reminder) are less important.
3. Environment (OS, browser) is completely missing.
4. These are titles, so no periods should be put in the end.

Proposed template:

Bug report template:

Bug overview description
What steps did you take to replicate this bug?
What is the expected behavior?
What actual behavior is given instead?
Errors or other messages returned (if any)
What operating system and browser are you using?
What part(s) of the site page(s) are affected?
Time of incident (if applicable).
Can you reproduce the bug every time?