Bug report: Added checkbox for project files and log file. Added extra information in additional information and file uploads.
Changed the textarea to markdown so files can be uploaded.
Updated the placeholder to 4.9 in application version.
Feature request:
Changed textarea to markdown.
Removed issue-body in bugreport.yaml and featurerequest.yaml
Added config file: can't create a blank issue and added contact link to ultimaker community.
I think the 'why' of things is not always relevant and makes people prevent reading all of it. Keep it brief! And with all of this information that people tend to just leave there it's hard to find the actual changes that people made to the template. That's also why the brackets are important, so that it's easy to see that people didn't erase the original template text.
We used to have HTML comment codes there but then people put the actual bug report inside the comments as well and nothing showed up, so this is somewhat of a middle ground that everyone understands, programmers and non-programmers.
I fear people might simply ignore the header, which is surrounded by
comment tags. Having headings for all important pieces of information
might make them stand out more.
Two major changes here:
1. No longer include the instructions in comments. Quite often the filled in template was also in comments then because people don't know the HTML formatting. Also if the template is not completely filled in now, public shaming ensues.
2. The reproduce steps for bugs now suggest a numbered list of steps. Hopefully this will improve the bug reports we get with better reproduction steps.
We don't usually need to know what specific Qt version or graphics driver the user has, and it's a great hassle for the user to figure this out, especially when they aren't technical and just installed an official release.
I hope that this leads more bug reporters to actually fill in the template.
