►
From YouTube: Issue Templates
Description
How and why you may want to create and use issue templates and a high-level overview of using issue boards and labels for basic workflow management and automation.
Find other videos like this one at https://about.gitlab.com/handbook/practical-handbook-edits/.
A
I
was
recently
asked
by
a
team
member
just
how
to
create
issue
templates,
so
I
thought
I'd
record
this
in
case
it
can
help
the
rest
of
the
team
alright.
So
this
is
an
example
of
our
command
of
the
message.
Page
recently
worked
with
John,
Jeremiah
and
Eric
Brown
to
create
this.
This
improved
process
that
automates
some
of
the
collecting
of
feedback.
A
So
any
any
kind
of
program
that
you
have,
if
you
want
to
create
you
may
want
to
do,
you
may
want
to
create
an
issue
template
just
to
standardize
on
the
way
in
which
that
information
comes
in,
so
that
you
then
can
then
triage
and
figure
out
what
to
do
with
the
issue.
And
then
you
can
automatically
apply
labels
to
facilitate
issue
boards
to
help
you
manage
multiple
issues
and
kind
of
track
and
manage
that.
A
So
in
this
instance,
for
example,
click
on
issue
template,
and
so
so
that
you
know
what
I'm
talking
about
an
issue.
Template
is
pre-populated,
so
somebody
can
come
in
and
instead
of
having
a
blank
slate
here,
it
prompts
them
for
specifically
the
information
that
you
want
them
to
include.
So,
in
this
instance,
we
vasto
me
explain
what
it
is.
A
We
say,
alright
check
which
what's
the
type
of
feedback
and
what's
the
specific
asset
or
part
of
the
framework
framework
that
you're
giving
feedback
on
or
making
a
suggestion,
and
then
they
described
the
change
here
and
what's
what's
the
value?
What's
the
benefit
of
what
you're
suggesting
and
then
at
the
bottom,
it
lists
out
labels,
so
you
can
automatically
apply
labels
so
that
it
appears
in
issue
boards.
A
You
can
assign
it
to
any
of
these
quick
actions.
It
supports
in
these
issue
templates
again
helps
to
automate
some
of
the
workflow
of
how
you're
managing
the
work
so
in
terms
of
authority.
So
you
want
to
create
your
own
I'd
say:
first,
you
know
find
an
issue
that
you
of
where
you
want
to
create
the
template.
So
here's
one
I
was
recently-
and
this
is
so.
This
is
within
field.
Ops,
enablement,
so
yeah
I
want
to
see
where
to
I
want
to
create
an
issue
template
in
this
group
area.
A
So
you
go
to
in
this
view
of
with
an
issue
go
to
repository
files,
and
then
you
can
see
if
I
click
there.
This
lists
out
the
different
issue
templates
that
are
available
so
just
simply
click
web
IDE
and
on
the
rights
on
the
left
side.
If
I
want
to
create
a
new
one,
just
literally
hit
new
file
and
on
this
example-
and
you
can
look
at
how
some
of
these
others
are
formatted.
A
So
here,
if
I
went
to
new
it'll,
ask
me
to
pick
a
template,
so
I
can
choose
any
one
of
these
apply
template
and
then
it
pre-populates
hope
this
is
helpful.
So
and
I'll
extend
just
a
little
bit
more.
So
then,
in
that
example,
I
shared
command
with
command
of
the
message.
We
have
a
issue
template
that
people
can
use
to
provide
feedback,
so
the
workflow
then
based
on
the
labels
that
we've
applied
or
that
we
have
applied
in
the
issue.
It
automatically
gets
applied
this
vff
new.
A
So
we
can
periodically
look
at
this
to
see
what
feedback
has
come
in
and
then,
whether
that's
you
want
to
look
at
it
daily.
You
know
weekly,
whatever
your
the
process
as
the
cadence
of
how
frequently
your
you're
reviewing
this
and
then
from
there
you,
you
can
use
labels
to
essentially
kind
of
come
up
with
a
disposition
or
what
action
you're
taking
so
here
you
can
choose
to
either
accept
decline
or
defer,
and
all
this
by
the
way
is
documented
in
that
same
handbook,
page
that
we
looked
at
before.
A
So
it's
we're
very
transparent
about
what
the
process
is.
So
we
either
accept
decline
or
defer,
and
then
we've
also
introduced
labels
that
we
have
a
calendar
of.
Is
this
improvement
or
this
this
feedback?
Is
it
going
to
be
show
up
in
version
1.1
or
version
1.2
and
then
so?
Each
piece
of
feedback
then
can
be
tracked
and
managed
separately.
The
person
that
submitted
the
feedback
will
get
updates,
etc.
I
hope
this
was
helpful.