My Marlin configs for Fabrikator Mini and CTC i3 Pro B
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

bug_report.yml 5.4KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168
  1. name: 🪲 Report a bug
  2. description: Create a bug report to help improve Marlin Firmware
  3. title: "[BUG] (bug summary)"
  4. body:
  5. - type: markdown
  6. attributes:
  7. value: >
  8. Do you want to ask a question? Are you looking for support? Please use one of the [support links](https://github.com/MarlinFirmware/Marlin/issues/new/choose).
  9. - type: markdown
  10. attributes:
  11. value: |
  12. **Thank you for reporting a bug in Marlin Firmware!**
  13. ## Before Reporting a Bug
  14. - Read and understand Marlin's [Code of Conduct](https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/.github/code_of_conduct.md). You are expected to comply with it, including treating everyone with respect.
  15. - Test with the [`bugfix-2.0.x` branch](https://github.com/MarlinFirmware/Marlin/archive/bugfix-2.0.x.zip) to see whether the issue still exists.
  16. ## Instructions
  17. Please follow the instructions below. Failure to do so may result in your issue being closed. See [Contributing to Marlin](https://github.com/MarlinFirmware/Marlin/blob/bugfix-2.0.x/.github/contributing.md) for additional guidelines.
  18. 1. Provide a good title starting with [BUG].
  19. 2. Fill out all sections of this bug report form.
  20. 3. Always attach configuration files so we can build and test your setup.
  21. - type: dropdown
  22. attributes:
  23. label: Did you test the latest `bugfix-2.0.x` code?
  24. description: >-
  25. Always try the latest code to make sure the issue you are reporting is not already fixed. To download
  26. the latest code just [click this link](https://github.com/MarlinFirmware/Marlin/archive/bugfix-2.0.x.zip).
  27. options:
  28. - Yes, and the problem still exists.
  29. - No, but I will test it now!
  30. validations:
  31. required: true
  32. - type: markdown
  33. attributes:
  34. value: |
  35. # Bug Details
  36. - type: textarea
  37. attributes:
  38. label: Bug Description
  39. description: >-
  40. Describe the bug in this section. Tell us what you were trying to do and what
  41. happened that you did not expect. Provide a clear and concise description of the
  42. problem and include as many details as possible.
  43. When pasting formatted text don't forget to put ` ``` ` (on its own line) before and after to make it readable.
  44. placeholder: |
  45. Marlin doesn't work.
  46. validations:
  47. required: true
  48. - type: input
  49. attributes:
  50. label: Bug Timeline
  51. description: Is this a new bug or an old issue? When did it first start?
  52. - type: textarea
  53. attributes:
  54. label: Expected behavior
  55. description: >-
  56. What did you expect to happen?
  57. placeholder: I expected it to move left.
  58. - type: textarea
  59. attributes:
  60. label: Actual behavior
  61. description: What actually happened instead?
  62. placeholder: It moved right instead of left.
  63. - type: textarea
  64. attributes:
  65. label: Steps to Reproduce
  66. description: >-
  67. Please describe the steps needed to reproduce the issue.
  68. placeholder: |
  69. 1. [First Step] ...
  70. 2. [Second Step] ...
  71. 3. [and so on] ...
  72. - type: markdown
  73. attributes:
  74. value: |
  75. # Your Setup
  76. - type: input
  77. attributes:
  78. label: Version of Marlin Firmware
  79. description: "See the About Menu on the LCD or the output of `M115`. NOTE: For older releases we only patch critical bugs."
  80. validations:
  81. required: true
  82. - type: input
  83. attributes:
  84. label: Printer model
  85. description: Creality Ender 3, Prusa mini, or Kossel Delta?
  86. - type: input
  87. attributes:
  88. label: Electronics
  89. description: Stock electronics, upgrade board, or something else?
  90. - type: input
  91. attributes:
  92. label: Add-ons
  93. description: Please list any hardware add-ons that could be involved.
  94. - type: dropdown
  95. attributes:
  96. label: Bed Leveling
  97. description: What kind of bed leveling compensation are you using?
  98. options:
  99. - UBL Bilinear mesh
  100. - ABL Bilinear mesh
  101. - ABL Linear grid
  102. - ABL 3-point
  103. - MBL Manual Bed Leveling
  104. - No Bed Leveling
  105. - type: dropdown
  106. attributes:
  107. label: Your Slicer
  108. description: Do you use Slic3r, Prusa Slicer, Simplify3D, IdeaMaker...?
  109. options:
  110. - Slic3r
  111. - Simplify3D
  112. - Prusa Slicer
  113. - IdeaMaker
  114. - Cura
  115. - Other (explain below)
  116. - type: dropdown
  117. attributes:
  118. label: Host Software
  119. description: Do you use OctoPrint, Repetier Host, Pronterface...?
  120. options:
  121. - SD Card (headless)
  122. - Repetier Host
  123. - OctoPrint
  124. - Pronterface
  125. - Cura
  126. - Same as my slicer
  127. - Other (explain below)
  128. - type: checkboxes
  129. attributes:
  130. label: Other things to include
  131. options:
  132. - label: A ZIP file containing your `Configuration.h` and `Configuration_adv.h`.
  133. required: true
  134. - label: Log output from the host. (`M111 S247` for maximum logging.)
  135. - label: Images or videos demonstrating the problem, if it helps to make it clear.
  136. - label: A G-Code file that exposes the problem, if not affecting _all_ G-code.
  137. - type: textarea
  138. attributes:
  139. label: Additional information & file uploads
  140. description: >-
  141. If you've made any other modifications to the firmware, please describe them in detail.
  142. When pasting formatted text don't forget to put ` ``` ` (on its own line) before and after to make it readable.