bugreport.yaml 3.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. name: 🪲 Bug Report
  2. description: Create a report to help us fix issues.
  3. labels: ["Type: Bug", "Status: Triage"]
  4. body:
  5. - type: markdown
  6. attributes:
  7. value: |
  8. **Thank you for using Cura and wanting to report a bug. 🙏**
  9. Before filing, [please check if the issue already exists](https://github.com/Ultimaker/Cura/issues?q=is%3Aissue) by using the search bar on the issues page.
  10. If it does, comment there. Even if it's closed, we can reopen it based on your comment.
  11. Please include the cura version in the title of the issue. For example, *"[5.4.0] Support Brim is missing in this model"*.
  12. - type: input
  13. attributes:
  14. label: Cura Version
  15. description: The version of Cura this issue occurs with.
  16. placeholder: 5.4.0
  17. validations:
  18. required: true
  19. - type: input
  20. attributes:
  21. label: Operating System
  22. description: Information about the operating system the issue occurs on. Include at least the operating system and maybe GPU.
  23. placeholder: Windows 11 / MacOS Catalina / MX Linux
  24. validations:
  25. required: true
  26. - type: input
  27. attributes:
  28. label: Printer
  29. description: Which printer was selected in Cura? It also helps to mention if you made any firmware modifications to your printer.
  30. placeholder: Ultimaker S7 / Creality CR-10 with Klipper
  31. validations:
  32. required: true
  33. - type: textarea
  34. attributes:
  35. label: Reproduction steps
  36. description: Share what you did, so we can reproduce it
  37. placeholder: |
  38. 1. Something you did
  39. 2. Something you did next
  40. validations:
  41. required: true
  42. - type: textarea
  43. attributes:
  44. label: Actual results
  45. description: What happens after the above steps have been followed?
  46. validations:
  47. required: true
  48. - type: textarea
  49. attributes:
  50. label: Expected results
  51. description: What should happen after the above steps have been followed?
  52. validations:
  53. required: true
  54. - type: markdown
  55. attributes:
  56. value: |
  57. ### Please add the following files when they are related to...
  58. * 🔵 **The quality of your print**
  59. Please add **a Project File**. It contains the printer and settings we need for troubleshooting.
  60. To save a project file go to File -> Save project.
  61. Please make sure to .zip your project file. For big files, you may need to use [WeTransfer](https://wetransfer.com/) or similar file-sharing sites.
  62. G-code files are not project files! Before you share, please think to yourself. Is this a model that can be shared?
  63. ![Alt Text](https://user-images.githubusercontent.com/40423138/240616958-5a9751f2-bd34-4808-9752-6fde2e27516e.gif)
  64. * 🔵 **Using and interacting with Cura**
  65. Please add **screenshots** showing the issue.
  66. Before and after, and arrows can help here.
  67. * 🔵 **Unexpected crashes and behavior**
  68. Please add **a log file** with information on what your Cura is doing.
  69. You can find your log file here:
  70. Windows: `%APPDATA%\cura\<Cura version>\cura.log`
  71. MacOS: `$USER/Library/Application Support/cura/<Cura version>/cura.log`
  72. Ubuntu/Linux: `$USER/.local/share/cura/<Cura version>/cura.log`
  73. If the Cura user interface still starts, you can also reach this directory from the application menu in Help -> Show settings folder
  74. - type: textarea
  75. attributes:
  76. label: Add your .zip and screenshots here ⬇️
  77. description: You can add the zip file and additional information that is relevant to the issue in the comments below.
  78. validations:
  79. required: true