Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/.github/ISSUE_TEMPLATE/2_bug_report.md

19 lines
619 B
Markdown
Raw Normal View History

github: Configure templates for filing issues. This PR creates templates for filing issues. The templates are intentionally quite light-weight. Note that I'm specifically not using forms for creating issues, as the UI for filling out such a form does not include GitHub's helpful formatting buttons and preview mode. Follow-up to #25998, pushed as a separate PR so that the original one can pass CI. This PR creates templates for filing issues. The templates are intentionally quite light-weight. Note that I'm specifically not using forms for creating issues, as the UI for filling out such a form does not include GitHub's helpful formatting buttons and preview mode. A major goal is to guide users towards starting a CZO conversation when that's more appropriate than filing a GitHub issue. Note that the config makes it possible to create a blank issue, which should be handy for: * Issues filed by maintainers * Issues for tracking follow-ups from merged PRs * Probably some other situations Because the blank issue option is easy to miss, it should probably be documented somewhere, but I'm not sure where. We can perhaps start with a note on CZO. Relevant CZO threads: https://chat.zulip.org/#narrow/stream/137-feedback/topic/issues.20link.20in.20description/near/1561110) https://chat.zulip.org/#narrow/stream/2-general/topic/bug.20report.20management/near/1589141 Also provide external documentation links for situations where filing an issue is not the best approach.
2023-06-13 00:32:53 +02:00
---
name: Bug report
about: A concrete bug report with steps to reproduce the behavior. (See also "Possible bug" below.)
labels: ["bug"]
---
<!-- Describe what you were expecting to see, what you saw instead, and steps to take in order to reproduce the buggy behavior. Screenshots can be helpful. -->
<!-- Check the box for the version of Zulip you are using (see https://zulip.com/help/view-zulip-version).-->
**Zulip Server and web app version:**
- [ ] Zulip Cloud (`*.zulipchat.com`)
github: Add Zulip Server 8.0+ to bug report checklist. And the release checklist so we don't forget next time.
2024-01-24 18:53:41 +01:00
- [ ] Zulip Server 8.0+
github: Configure templates for filing issues. This PR creates templates for filing issues. The templates are intentionally quite light-weight. Note that I'm specifically not using forms for creating issues, as the UI for filling out such a form does not include GitHub's helpful formatting buttons and preview mode. Follow-up to #25998, pushed as a separate PR so that the original one can pass CI. This PR creates templates for filing issues. The templates are intentionally quite light-weight. Note that I'm specifically not using forms for creating issues, as the UI for filling out such a form does not include GitHub's helpful formatting buttons and preview mode. A major goal is to guide users towards starting a CZO conversation when that's more appropriate than filing a GitHub issue. Note that the config makes it possible to create a blank issue, which should be handy for: * Issues filed by maintainers * Issues for tracking follow-ups from merged PRs * Probably some other situations Because the blank issue option is easy to miss, it should probably be documented somewhere, but I'm not sure where. We can perhaps start with a note on CZO. Relevant CZO threads: https://chat.zulip.org/#narrow/stream/137-feedback/topic/issues.20link.20in.20description/near/1561110) https://chat.zulip.org/#narrow/stream/2-general/topic/bug.20report.20management/near/1589141 Also provide external documentation links for situations where filing an issue is not the best approach.
2023-06-13 00:32:53 +02:00
- [ ] Zulip Server 7.0+
- [ ] Zulip Server 6.0+
- [ ] Zulip Server 5.0 or older
- [ ] Other or not sure