~2 min read|
We use templates to help write descriptive tickets or MRs on various projects at work. 1 Then I started working on a new project and when I reached for them, I found the templates hadn’t been set up.
I didn’t realize just how much I liked them until I found myself in a position where they weren’t available. I took their absence as an opportunity. I set out to set up some basic ones and get the process started for the team.
To do that, however, I needed to learn a few things. It turns out that there are multiple types of templates (issues and merge requests) and that they can have some levels of automation built into them (through quick actions 1 on Gitlab).
The actual creation of the process is very straightforward:
.gitlab/merge_request_templatesdepending on the template type you’re interested in.
.md) file with the template. Name it how you’d like the template to appear in the UI.
repoand merge them into Master.
Once that’s done, you should have templates available.
Secondly, I loved the motivation for the feature. According to Gitlab:
We all know that a properly submitted issue is more likely to be addressed in a timely manner by the developers of a project. Description templates allow you to define context-specific templates for issue and merge request description fields for your project, as well as help filter out a lot of unnecessary noise from issues.
So true. Now, go forth and create better tickets powered by templates.
Hi there and thanks for reading! My name's Stephen. I live in Chicago with my wife, Kate, and dog, Finn. Want more? See about and get in touch!