From 9dd1ef182bd0cf1a0af2073e6ede4e332995d127 Mon Sep 17 00:00:00 2001
From: Mark Fletcher <mark@gitlab.com>
Date: Wed, 31 May 2017 18:35:24 +0800
Subject: [PATCH] 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]
---
 .gitlab/issue_templates/Bug.md                              | 6 ++++++
 .../issue-template-reproduce-in-example-project.yml         | 4 ++++
 2 files changed, 10 insertions(+)
 create mode 100644 changelogs/unreleased/issue-template-reproduce-in-example-project.yml

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)
diff --git a/changelogs/unreleased/issue-template-reproduce-in-example-project.yml b/changelogs/unreleased/issue-template-reproduce-in-example-project.yml
new file mode 100644
index 00000000000..8116007b459
--- /dev/null
+++ b/changelogs/unreleased/issue-template-reproduce-in-example-project.yml
@@ -0,0 +1,4 @@
+---
+title: Ask for an example project for bug reports
+merge_request:
+author:
-- 
GitLab