6aa8d060d5
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.
1.7 KiB
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Bug report | Create a report to help us fix issues. | Type: Bug |
Application version (The version of the application this issue occurs with.)
Platform (Information about the operating system the issue occurs on. Include at least the operating system and maybe GPU.)
Printer (Which printer was selected in Cura?)
Reproduction steps
- (Something you did.)
- (Something you did next.)
Screenshot(s) (Image showing the problem, perhaps before/after images.)
Actual results (What happens after the above steps have been followed.)
Expected results (What should happen after the above steps have been followed.)
Project file (For slicing bugs, provide a project which clearly shows the bug, by going to File->Save. For big files you may need to use WeTransfer or similar file sharing sites.)
Log file (See https://github.com/Ultimaker/Cura#logging-issues to find the log file to upload, or copy a relevant snippet from it.)
Additional information (Extra information relevant to the issue.)