Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
343534f4
Commit
343534f4
authored
Jan 17, 2019
by
Mike Lewis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Updates to Feature proposal.md
parent
b2c6058a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
14 additions
and
7 deletions
+14
-7
.gitlab/issue_templates/Feature proposal.md
.gitlab/issue_templates/Feature proposal.md
+14
-7
No files found.
.gitlab/issue_templates/Feature proposal.md
View file @
343534f4
### Problem to solve
### Problem to solve
<!--
-
What problem do we solve? -->
<!-- What problem do we solve? -->
### Target audience
### Target audience
...
@@ -9,21 +9,28 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst"
...
@@ -9,21 +9,28 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst"
### Further details
### Further details
<!--
-
Include use cases, benefits, and/or goals (contributes to our vision?) -->
<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### Proposal
### Proposal
<!--
-
How are we going to solve the problem? -->
<!-- How are we going to solve the problem? -->
### Documentation
### Documentation
<!-- What doc pages need to be created or updated across user, admin, and API docs?
<!--
What concepts, procedures, or info is needed on each?
*
What doc pages need to be created or updated across user, admin, and API docs?
PMs: Specify feature name, description, benefits, and use cases, if applicable. -->
*
What concepts, procedures, or information is needed in each area? Is there an 'old way' or workaround to deprecate?
Product managers:
*
By the kickoff, finalize the answers to the bullets above, and:
*
If applicable, specify new or updated feature name(s), description(s), benefits,
and use cases, which may all be used in the documentation or features.yml.
*
Specify which use cases or scenarios would benefit from a set of instructions
or a guide unique to that use case. -->
### What does success look like, and how can we measure that?
### What does success look like, and how can we measure that?
<!--
-
If no way to measure success, link to an issue that will implement a way to measure this -->
<!-- If no way to measure success, link to an issue that will implement a way to measure this -->
### Links / references
### Links / references
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment