Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #44188
Closed (moved) (moved)
Open
Created Mar 13, 2018 by Carlos Soriano Sánchez@csorianoContributor

Issue templates are not discoverable enough

We were discussing at GNOME the usage of issue templates, but found they are not of much use given that they are not discoverable enough and reporters don't know they exist or how to use them and they keep skipping them.

In gitlab.com this is solved by using a default template in issues pointing out to use a template, however that is an EE feature.

Most probably this makes more sense to have in CE nowadays given that the default template feature predates the multiple issues templates feature that was made into CE from the start. However, I wanted to take this issue from the UX perspective without jumping into solutions that can interfere between CE and EE.

One solution to this UX problem could be to force the use of templates for every issue and provide an "Empty" template as part of the default set. This may make more sense if templates are the preferred way to report issues and it could potentially remove the need for default templates in GitLab.

Edited Mar 13, 2018 by Carlos Soriano Sánchez
Assignee
Assign to
Time tracking