@@ -129,7 +129,7 @@ request that potentially fixes it.
...
@@ -129,7 +129,7 @@ request that potentially fixes it.
### Feature proposals
### Feature proposals
To create a feature proposal for CE and CI, open an issue on the
To create a feature proposal for CE, open an issue on the
[issue tracker of CE][ce-tracker].
[issue tracker of CE][ce-tracker].
For feature proposals for EE, open an issue on the
For feature proposals for EE, open an issue on the
...
@@ -144,16 +144,7 @@ code snippet right after your description in a new line: `~"feature proposal"`.
...
@@ -144,16 +144,7 @@ code snippet right after your description in a new line: `~"feature proposal"`.
Please keep feature proposals as small and simple as possible, complex ones
Please keep feature proposals as small and simple as possible, complex ones
might be edited to make them small and simple.
might be edited to make them small and simple.
You are encouraged to use the template below for feature proposals.
Please submit Feature Proposals using the ['Feature Proposal' issue template](.gitlab/issue_templates/Feature Proposal.md) provided on the issue tracker.
```
## Description
Include problem, use cases, benefits, and/or goals
## Proposal
## Links / references
```
For changes in the interface, it can be helpful to create a mockup first.
For changes in the interface, it can be helpful to create a mockup first.
If you want to create something yourself, consider opening an issue first to
If you want to create something yourself, consider opening an issue first to
...
@@ -166,55 +157,11 @@ submitting your own, there's a good chance somebody else had the same issue or
...
@@ -166,55 +157,11 @@ submitting your own, there's a good chance somebody else had the same issue or
feature proposal. Show your support with an award emoji and/or join the
feature proposal. Show your support with an award emoji and/or join the
discussion.
discussion.
Please submit bugs using the following template in the issue description area.
Please submit bugs using the ['Bug' issue template](.gitlab/issue_templates/Bug.md) provided on the issue tracker.
The text in the parenthesis is there to help you with what to include. Omit it
The text in the parenthesis is there to help you with what to include. Omit it
when submitting the actual issue. You can copy-paste it and then edit as you
when submitting the actual issue. You can copy-paste it and then edit as you
see fit.
see fit.
```
## Summary
(Summarize your issue in one sentence - what goes wrong, what did you expect to happen)
## Steps to reproduce
(How one can reproduce the issue - this is very important)
## Expected behavior
(What you should see instead)
## Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
## Output of checks
### Results of GitLab Application Check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
=link_tonamespace_project_tag_path(@project.namespace,@project,@tag.name),class: 'btn btn-remove remove-row grouped has-tooltip',title: "Delete tag",method: :delete,data: {confirm: "Deleting the '#{@tag.name}' tag cannot be undone. Are you sure?"}do
=link_tonamespace_project_tag_path(@project.namespace,@project,@tag.name),class: 'btn btn-remove remove-row grouped has-tooltip',title: "Delete tag",method: :delete,data: {confirm: "Deleting the '#{@tag.name}' tag cannot be undone. Are you sure?"}do
=link_to'Delete',polymorphic_path([@project.namespace.becomes(Namespace),@project,issuable]),data: {confirm: "#{issuable.class.name.titleize} will be removed! Are you sure?"},
=link_to'Delete',polymorphic_path([@project.namespace.becomes(Namespace),@project,issuable]),data: {confirm: "#{issuable.class.name.titleize} will be removed! Are you sure?"},