From 9d1131a0019709726fa25dd10edde49b18d23911 Mon Sep 17 00:00:00 2001 From: Marcia Ramos Date: Thu, 18 Aug 2016 04:08:16 +0000 Subject: [PATCH] Update issue_and_merge_request_template.md - EE features --- .../issue_and_merge_request_template.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/doc/customization/issue_and_merge_request_template.md b/doc/customization/issue_and_merge_request_template.md index 5804f5193e5855..8cbd91bb282d6c 100644 --- a/doc/customization/issue_and_merge_request_template.md +++ b/doc/customization/issue_and_merge_request_template.md @@ -5,6 +5,22 @@ EE 6.9. Templates for issues were [introduced][ee-28] in GitLab EE 8.1._ --- +## Overview + +Templates provide standardized text for issues and merge requests (MRs). + +## Use-cases + +- Add a template to be used in every issue for a specific project, +giving instructions and guidelines, requiring for information specific to that subject. +For example, if you have a project for tracking new blog posts, you can require the +title, outlines, author name, author social media information, etc. +- Following the previous example, you can make a template for every MR submitted +with a new blog post, requiring information about the post date, frontmatter data, +images guidelines, link to the related issue, reviewer name, etc. + +## Description + We all know that a properly submitted issue is more likely to be addressed in a timely manner by the developers of a project. -- GitLab