Add support for "New issue" templates

On GoogleCode it was possible to provide a template for new issues - which helps not experienced users to create proper reports.

After submission these lines are displayed in bold:

GitHub allows to set up some rules for contributing which are then displayed as a link above the test area:

/cc @DouweM

Note that we've already got the link to the contribution guide, even if it's not as obvious as on GitHub:

Take the CONTRIBUTING.md of GitLab, nobody reads such a long text :-(

mentioned in issue #1429 (closed)

mentioned in issue #1420 (closed)

I'm open to creating a single issue and merge request template in the project settings. @dzaporozhets how do you feel about that?

@sytses merge request templates is EE feature now. I am not sure if having one template for both issues and merge requests will work because in issue you describe the problem but in merge request you describe a solution.

From https://news.ycombinator.com/item?id=9873282:

GitHub makes some things harder -- the issue tracker doesn't have issue templates, so you have to overcommunicate the need to fill out proper templates, and people also throw code at projects prior to asking what the code should be. I love GitHub for the OSS explosion it has enabled, but it is a chaotic way of managing a project as that project gets big.

Implementing the ability to create different types of issue templates (e.g., "Feature Request", "Bug Report", "Meta Suggestions", etc.) would allow for a much more streamlined contribution process. Having a CONTRIBUTING.md is important, but expecting users to read it fully before contributing is like expecting users to fully read the Terms and Conditions before signing up for a website. Templates would help filter out a lot of unnecessary noise from issues.

@dzaporozhets Please let me correct myself. I mean one issue template and one merge request template. I think it should be an EE feature since you need it when having a lot of people. Project on GitLab.com will be able to use it.

@nonostante Thanks for the comment, makes sense.

I mean one issue template and one merge request template. I think it should be an EE feature since you need it when having a lot of people. Project on GitLab.com will be able to use it.

@sytses absolutely right

Milestone changed to 7.14

Added promised label

@JobV I added the new promised label to this because I promised it to Turtoise.

Fair enough.

This didn't get picked up.

@dzaporozhets can you work on this for 8.0?

Milestone changed to 8.0

@JobV I am not sure. But I will ask @vsizov in case I will be overloaded.

Thanks @dzaporozhets

mentioned in issue tortoisegit/tortoisegit#2579 (closed)

Added ~107431 label

@dzaporozhets @vsizov this didn't get implemented for the second time after promising it, which is a shame.

There is no space in 8.1. I'll have a look in 8.1 if I can move things. Otherwise this will move up.

cc @sytses

Milestone changed to 8.1

This should be very easy to implement, because we already have the necessary code for merge requests.
It's pretty much copy & pasting the results of this search:
https://gitlab.com/search?utf8=%E2%9C%93&project_id=278964&group_id=&snippets=&scope=&search=merge_requests_template
You just need to modify it very little.
I'll take a look at it if I have some time later.

@haynes that would be really great. If you want me to ping you, let me know.

@JobV If I haven't send an MR within one week, please ping me. :)

I've implemented this in the MR mentioned above my comment ;)

@haynes

gitlab-org/gitlab-ee!28 was merged!

@mrtux This will be available in GitLab EE 8.1 and GitLab.com on October 22nd :)

Status changed to closed

mentioned in commit 3e71e568

Why this issue is closed? It's still not available in GitLab CE

Is there a way to have "issue templates" in CE?

@quanlong @chraibi we decided to make this a GitLab EE feature because we think it is much more relevant for organizations that have more than 100 developers

@sytses you mean EE?

@connorshea correct, thanks, I edited my comment

Mentioned in commit pfjason/gitlab-ce@3e71e568

mentioned in merge request !14785