bug_report.yaml 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990
  1. name: Bug Report
  2. description: Report a bug encountered while using Logseq
  3. body:
  4. - type: markdown
  5. attributes:
  6. value: |
  7. Thank you very much for opening a bug report with Logseq.
  8. If you have a feature idea or need help, please go to [our Forum](https://discuss.logseq.com/) or [our Discord](https://discord.com/invite/KpN4eHY).
  9. Please make sure to provide a descriptive, deterministic, and reproducible report. It saves time for both the developers and users who are looking for solutions. Providing as much information as possible, including screenshots and logs, is highly appreciated. This will help us to better understand the issue and respond more effectively.
  10. Please DO NOT use this template to ask questions. There are other appropriate channels to ask questions. This template is strictly for reporting bugs.
  11. - type: checkboxes
  12. id: confirm-search
  13. attributes:
  14. label: Search first
  15. description: Please search [existing issues](https://github.com/logseq/logseq/issues) and the [Logseq Forum](https://discuss.logseq.com/) before reporting.
  16. options:
  17. - label: I searched and no similar issues were found
  18. required: true
  19. - type: textarea
  20. id: problem
  21. attributes:
  22. label: What Happened?
  23. description: |
  24. Please provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner.
  25. validations:
  26. required: true
  27. - type: textarea
  28. id: reproduce
  29. attributes:
  30. label: Reproduce the Bug
  31. description: |
  32. Please tell us the steps to reproduce the bug.
  33. placeholder: |
  34. 1. Go to '...'
  35. 2. Click on '....'
  36. 3. Scroll down to '....'
  37. 4. See error
  38. validations:
  39. required: true
  40. - type: textarea
  41. id: expected
  42. attributes:
  43. label: Expected Behavior
  44. description: |
  45. Please tell us what's the behavior you expect.
  46. validations:
  47. required: false
  48. - type: textarea
  49. id: screenshots
  50. attributes:
  51. label: Screenshots
  52. description: |
  53. If applicable, add screenshots or screen recordings to help explain your problem.
  54. validations:
  55. required: false
  56. - type: textarea
  57. id: platform
  58. attributes:
  59. label: Desktop or Mobile Platform Information
  60. description: |
  61. Would you mind to tell us the system information about your desktop or mobile platform?
  62. placeholder: |
  63. OS version, Browser or App, Logseq App version
  64. example: macOS 12.2, Desktop App v0.5.9
  65. example: iPhone 12, iOS8.1, v0.5.9
  66. example: Pixel XL, Android 12, v0.5.9
  67. validations:
  68. required: false
  69. - type: textarea
  70. id: additional
  71. attributes:
  72. label: Additional Context
  73. description: |
  74. If applicable, add additional context to help explain your problem.
  75. validations:
  76. required: false
  77. - type: checkboxes
  78. id: ask-pr
  79. attributes:
  80. label: Are you willing to submit a PR? If you know how to fix the bug.
  81. description: |
  82. If you are not familiar with programming, you can skip this step.
  83. If you are a developer and know how to fix the bug, you can [submit a PR to fix it](https://github.com/logseq/logseq/blob/master/CONTRIBUTING.md#submit-pr).
  84. Your contributions are greatly appreciated and play a vital role in helping to improve the project!
  85. options:
  86. - label: I'm willing to submit a PR (Thank you!)