summaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE
diff options
context:
space:
mode:
Diffstat (limited to '.github/ISSUE_TEMPLATE')
-rw-r--r--.github/ISSUE_TEMPLATE/bug_report.md34
-rw-r--r--.github/ISSUE_TEMPLATE/feature_request.md16
-rw-r--r--.github/ISSUE_TEMPLATE/question.md26
3 files changed, 76 insertions, 0 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 000000000..d378d4512
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a bug report to help us improve
+labels: bug, needs triage
+---
+
+<!---
+When creating a bug report please:
+- Verify first that your issue is not already reported on GitHub
+- Test if the latest release and master branch are affected too.
+- Provide a clear and concise description of what the bug is in "Bug report
+ summary" section.
+- Try to provide as much information about your environment (OS distribution,
+ running in container, etc.) as possible to allow us reproduce this bug faster.
+- Write which component is affected. We group our components the same way our
+ code is structured so basically:
+ component name = dir in top level directory of repository
+- Describe how you found this bug and how we can reproduce it. Preferable with
+ a minimal test-case scenario. You can paste gist.github.com links for larger
+ files
+- Provide a clear and concise description of what you expected to happen.
+-->
+
+##### Bug report summary
+
+##### OS / Environment
+
+##### Netdata version (ouput of `netdata -V`)
+
+##### Component Name
+
+##### Steps To Reproduce
+
+##### Expected behavior
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 000000000..4d210259e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,16 @@
+---
+name: Feature request
+about: Suggest an idea for our project
+labels: feature request, needs triage
+---
+
+<!---
+When creating a feature request please:
+- Verify first that your issue is not already reported on GitHub
+- Explain new feature briefly in "Feature idea summary" section
+- Provide a clear and concise description of what you expect to happen.
+--->
+
+##### Feature idea summary
+
+##### Expected behavior
diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
new file mode 100644
index 000000000..c5cd71e66
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/question.md
@@ -0,0 +1,26 @@
+---
+name: Question
+about: You just want to ask a question? Go on.
+labels: question, no changelog
+---
+
+<!---
+When asking a new question please:
+- Verify first that your question wasn't asked before on GitHub.
+ HINT: Use label "question" when searching for such issues.
+- Briefly explain what is the problem you are having
+- Try to provide as much information about your environment (OS distribution,
+ running in container, etc.) as possible to allow us reproduce this bug faster.
+- Write which component is affected. We group our components the same way our
+ code is structured so basically:
+ component name = dir in top level directory of repository
+- Provide a clear and concise description of what you expected to happen.
+-->
+
+##### Question summary
+
+##### OS / Environment
+
+##### Component Name
+
+##### Expected results