Place issue default description template in an Issues section

This an actionable insight from the Code Review FY21-Q2 Category Maturity Scorecard research (insight).

What

Right now the project settings pages and sections don’t have a 1:1 mapping to features. Some features, like Repository, have a dedicated page. Others, like Merge requests, have their settings in the General settings page, in two sections: Merge requests and Merge request approvals. Others, like Issues, have a single section in the General settings, called Default issue template.

Why

This organization causes confusion on where to look for settings.

In research, we identified a specific instance of this problem, related to description templates. Participants were tasked with adding a default description template for merge requests. However, some of them were faster in finding the default description template setting for issues.

We think this is due to the MRs template existing inside the Merge requests section, and the issues template having its dedicated section, with the label clearly visible.

How

By placing the issue template in a new “Issues” section inside the General settings, this puts the issues feature at the same level as merge requests, avoiding confusion.