summaryrefslogtreecommitdiff
path: root/.gitlab
diff options
context:
space:
mode:
authorMark Fletcher <mark@gitlab.com>2017-05-31 18:35:24 +0800
committerMark Fletcher <mark@gitlab.com>2017-05-31 18:39:37 +0800
commit9dd1ef182bd0cf1a0af2073e6ede4e332995d127 (patch)
tree1e7a5adedf5c68c45db9d86fcc3ed6a5679eeab8 /.gitlab
parente5226177ac667c8ad4cc07270bbdef24031eb8a2 (diff)
downloadgitlab-ce-9dd1ef182bd0cf1a0af2073e6ede4e332995d127.tar.gz
Ask for an example project for bug reports
* Bugs reported in the GitLab Issue trackers should be reproducible * Asking reporters to reproduce on GitLab.com is reasonable * It lets us know whether the issue still exists in latest * It ensures that the steps to reproduce are solid * It gives Developers a live example to work from * Reporter can verify the fix in the example project once shipped [skip ci]
Diffstat (limited to '.gitlab')
-rw-r--r--.gitlab/issue_templates/Bug.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/.gitlab/issue_templates/Bug.md b/.gitlab/issue_templates/Bug.md
index 58af062e75e..9d53a48409a 100644
--- a/.gitlab/issue_templates/Bug.md
+++ b/.gitlab/issue_templates/Bug.md
@@ -20,6 +20,12 @@ Please remove this notice if you're confident your issue isn't a duplicate.
(How one can reproduce the issue - this is very important)
+### Example Project
+
+(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
+
+(If you are using an older version of GitLab, this will also determine whether the bug has been fixed in a more recent version)
+
### What is the current *bug* behavior?
(What actually happens)