update guides for feature proposals on the issue tracker
see also #4038 (closed)
cc @sytses
Merge request reports
Activity
mentioned in issue #4038 (closed)
41 41 42 42 To get support for your particular problem please use the [getting help channels](https://about.gitlab.com/getting-help/). 43 43 44 The [GitLab CE issue tracker on GitLab.com](https://gitlab.com/gitlab-org/gitlab-ce/issues) is only for obvious errors in the latest [stable or development release of GitLab](MAINTENANCE.md). If something is wrong but it is not a regression compared to older versions of GitLab please do not open an issue but a feature request. When submitting an issue please conform to the issue submission guidelines listed below. Not all issues will be addressed and your issue is more likely to be addressed if you submit a merge request which partially or fully addresses the issue. 44 The [GitLab CE issue tracker on GitLab.com](https://gitlab.com/gitlab-org/gitlab-ce/issues) is 45 for bugs in the latest GitLab release and feature proposals. 45 46 46 Do not use the issue tracker for feature requests. We have a specific [feature request forum](http://feedback.gitlab.com) for this purpose. Please keep feature requests as small and simple as possible, complex ones might be edited to make them small and simple. 47 When submitting an issue please conform to the issue submission guidelines listed below. 48 Not all issues will be addressed and your issue is more likely to be addressed 49 if you submit a merge request which partially or fully addresses the issue. 47 50 48 Please send a merge request with a tested solution or a merge request with a failing test instead of opening an issue if you can. If you're unsure where to post, post to the [mailing list](https://groups.google.com/forum/#!forum/gitlabhq) or [Stack Overflow](https://stackoverflow.com/questions/tagged/gitlab) first. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there. 51 Please send a merge request with a tested solution or a merge request with a failing test instead of opening an issue if you can. 52 If you're unsure where to post, post to the [mailing list](https://groups.google.com/forum/#!forum/gitlabhq) Can we move this paragraph up before
Please send a merge request with a tested solution or a merge request with a failing test instead of opening an issue if you can.
Right now it seems that
If you're unsure where to post...
relates to the sentence above about merge requests which makes no much sense.
Added 1 commit:
- 5fb1fd27 - move up text regarding where to post issue
mentioned in commit b95f7b18
I updated the list in #4038 (closed)
mentioned in commit 509e0505
mentioned in commit a1981116
mentioned in commit dfe3c9a5
mentioned in commit 050d92f8
mentioned in commit 476655ca
mentioned in commit ad309f5d
mentioned in commit 75b84469
mentioned in commit nolith/gitlab-ce@bd35f223
mentioned in commit nolith/gitlab-ce@23c7548f