bug-report.yml 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116
  1. #
  2. # Licensed to the Apache Software Foundation (ASF) under one or more
  3. # contributor license agreements. See the NOTICE file distributed with
  4. # this work for additional information regarding copyright ownership.
  5. # The ASF licenses this file to You under the Apache License, Version 2.0
  6. # (the "License"); you may not use this file except in compliance with
  7. # the License. You may obtain a copy of the License at
  8. #
  9. # http://www.apache.org/licenses/LICENSE-2.0
  10. #
  11. # Unless required by applicable law or agreed to in writing, software
  12. # distributed under the License is distributed on an "AS IS" BASIS,
  13. # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
  14. # See the License for the specific language governing permissions and
  15. # limitations under the License.
  16. #
  17. name: Bug report
  18. title: "[Bug] [Module Name] Bug title "
  19. description: Problems and issues with code of Apache Dolphinscheduler
  20. labels: [ "bug", "Waiting for reply" ]
  21. body:
  22. - type: markdown
  23. attributes:
  24. value: |
  25. Please make sure what you are reporting is indeed a bug with reproducible steps, if you want to ask questions
  26. or share ideas, please [subscribe to our mailing list](mailto:dev-subscribe@dolphinscheduler.apache.org) and sent
  27. emails to [our mailing list](mailto:dev@dolphinscheduler.apache.org), you can also head to our
  28. [Discussion](https://github.com/apache/dolphinscheduler/discussions) tab.
  29. For better global communication, Please write in English.
  30. If you feel the description in English is not clear, then you can append description in Chinese, thanks!
  31. - type: checkboxes
  32. attributes:
  33. label: Search before asking
  34. description: >
  35. Please make sure to search in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue)
  36. first to see whether the same issue was reported already.
  37. options:
  38. - label: >
  39. I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found
  40. no similar issues.
  41. required: true
  42. - type: textarea
  43. attributes:
  44. label: What happened
  45. description: Describe what happened.
  46. placeholder: >
  47. Please provide the context in which the problem occurred and explain what happened
  48. validations:
  49. required: true
  50. - type: textarea
  51. attributes:
  52. label: What you expected to happen
  53. description: What do you think went wrong?
  54. placeholder: >
  55. Please explain why you think the behaviour is erroneous. It is extremely helpful if you copy and paste
  56. the fragment of logs showing the exact error messages or wrong behaviour and screenshots for
  57. UI problems. You can include files by dragging and dropping them here.
  58. **NOTE**: please copy and paste texts instead of taking screenshots of them for easy future search.
  59. validations:
  60. required: true
  61. - type: textarea
  62. attributes:
  63. label: How to reproduce
  64. description: >
  65. What should we do to reproduce the problem? If you are not able to provide a reproducible case,
  66. please open a [Discussion](https://github.com/apache/dolphinscheduler/discussions) instead.
  67. placeholder: >
  68. Please make sure you provide a reproducible step-by-step case of how to reproduce the problem
  69. as minimally and precisely as possible. Keep in mind we do not have access to your deployment.
  70. Remember that non-reproducible issues will be closed! Opening a discussion is recommended as a
  71. first step.
  72. validations:
  73. required: true
  74. - type: textarea
  75. attributes:
  76. label: Anything else
  77. description: Anything else we need to know?
  78. placeholder: >
  79. How often does this problem occur? (Once? Every time? Only when certain conditions are met?)
  80. Any relevant logs to include? Put them here inside fenced
  81. ``` ``` blocks or inside a collapsable details tag if it's too long:
  82. <details><summary>x.log</summary> lots of stuff </details>
  83. - type: checkboxes
  84. attributes:
  85. label: Are you willing to submit PR?
  86. description: >
  87. This is absolutely not required, but we are happy to guide you in the contribution process
  88. especially if you already have a good understanding of how to implement the fix.
  89. Dolphinscheduler is a totally community-driven project and we love to bring new contributors in.
  90. options:
  91. - label: Yes I am willing to submit a PR!
  92. - type: checkboxes
  93. attributes:
  94. label: Code of Conduct
  95. description: |
  96. The Code of Conduct helps create a safe space for everyone. We require that everyone agrees to it.
  97. options:
  98. - label: >
  99. I agree to follow this project's
  100. [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
  101. required: true
  102. - type: markdown
  103. attributes:
  104. value: "Thanks for completing our form!"