From 73472484a9dc46d412e76f7dc397a9cec6eee8d0 Mon Sep 17 00:00:00 2001
From: Ryan Lue <hello@ryanlue.com>
Date: Thu, 25 Apr 2019 12:08:48 +0800
Subject: [PATCH] Rephrase GitLab MR template to encourage more complete
 reporting

---
 .gitlab/merge_request_templates/Default.md | 23 +++++++++++++++-------
 1 file changed, 16 insertions(+), 7 deletions(-)

diff --git a/.gitlab/merge_request_templates/Default.md b/.gitlab/merge_request_templates/Default.md
index d7d5580f77be..941bbfadcbf2 100644
--- a/.gitlab/merge_request_templates/Default.md
+++ b/.gitlab/merge_request_templates/Default.md
@@ -42,16 +42,25 @@
 
   <!-- If so, explain. -->
 
-### Other Considerations  <!-- Optional -->
+### Performance Impact  <!-- Optional -->
 
 <!--
-Does your MR need one of the following labels?
+Does your MR optimize (or degrade) performance?
+If so, apply the label and explain here.
 
-* Performance Impact
-  (Keep in mind that some instances process 2,000+ tickets per day.)
+Consider that some of OTRS’s customers had
+HUNDREDS of agents, overviews, and groups,
+over 2,000 tickets a day,
+and over 20,000,000 (!) tickets in all.
+How do your performance changes scale on a system of this size?
 
-* Follow-up Required
-  (e.g., Do we need to coordinate with the documentation/support teams?)
+(Remember, these are not edge cases we can ignore;
+they are really big customers, and we want to keep their business!)
+-->
+
+### Follow-up Required  <!-- Optional -->
 
-If so, apply it and explain here.
+<!--
+Does your MR require coordination with the documentation/support teams?
+If so, apply the label and explain here.
 -->