From a9326cfa279edf1ae6ffa7708cdd38ee78e48b76 Mon Sep 17 00:00:00 2001
From: Mike Lewis <mlewis@gitlab.com>
Date: Fri, 8 Feb 2019 18:18:47 +0000
Subject: [PATCH] Update Documentation section to include link to new
 Documentation Requirements section in docs

---
 .gitlab/issue_templates/Feature proposal.md | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/.gitlab/issue_templates/Feature proposal.md b/.gitlab/issue_templates/Feature proposal.md
index 3cd800907a3..abfbef4b2b0 100644
--- a/.gitlab/issue_templates/Feature proposal.md	
+++ b/.gitlab/issue_templates/Feature proposal.md	
@@ -39,11 +39,8 @@ Existing personas are: (copy relevant personas out of this comment, and delete a
 
 ### Documentation
 
-<!-- See the Documentation Workflows https://docs.gitlab.com/ee/development/documentation/workflow.html and specify the following:
-What doc pages need to be created or updated across user, admin, and API docs?
-What concepts, procedures, or information is needed in each area? Is there an 'old way' that should be deprecated in the docs?
-If applicable, specify a new or updated feature name, description, benefits, and use cases, which may all be used in the documentation or features.yml.
-Which use cases or scenarios would benefit from a set of instructions or a guide, whether unique to each use case or flexible enough to cover multiple use cases. -->
+<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html
+Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements -->
 
 ### What does success look like, and how can we measure that?
 
-- 
GitLab