►
From YouTube: Plan - Scoped Labels Speed Run
Description
A quick demo of Scoped Labels and how they can be used as a mutually exclusive key:value stores on GitLab Issues, Merge Requests, and Epics.
A
Everyone's
Gabe
Weaver
senior
product
manager
of
the
project
management
group
within
the
plain
state
you
get
lab
today,
we're
going
to
be
doing
a
speedrun
on
scoped
labels,
so
we're
inside
of
a
project
right
now
we're
going
to
go
ahead
and
create
a
new
label
which
is
going
to
be
a
scope
labeled.
As
you
can
see,
the
instructions
here
use
the
double
colon
to
create
a
scope
label
set.
So
what
exactly
is
a
scope
label
set?
It
is
a
mutually
exclusive
key
value
store.
A
A
So
an
issue
1,
we
don't
have
any
labels,
we're
going
to
go
ahead
and
apply
our
new
scope,
labels
here
and
we're
going
to
find
key
value.
1,
you
can
see
that
label
is
applied,
so
what
traditionally
happens
is
if
you
want
to
remove
this
label,
you
have
to
go
search
for
it,
remove
it
and
then
add
the
new
label
you
want
to.
A
You
want
to
replace
it
with
with
scoped
label,
since
they're
mutually
exclusive,
you
can
simply
select
key
value,
2
and
save
that,
and,
as
you
can
see
once
we
save
it,
it
automatically
replaces
key
values
1
with
key
value
2.
So
what
this
lets
you
do
is
make
sure
that
if
you
want
to
have
a
pseudo
proxy
custom
field
which
represents
the
key,
is
the
field
name
and
then
a
set
of
different
values.
You
use
it
for
issue
types.
You
can
use
it
for
workflow
steps.
You
can
use
it
for
all
sorts
of
different
things.
A
Just
make
sure
that
you
can
only
have
one
of
each
available.
This
also
transitions
over
into
issue
boards
nicely,
as
you
can
set
up
your
list
for
your
key
and
your
values.
If
I
were
to
add
1
&
2
here,
you
can
see
that
I
mike
lee
pulls
in
the
key
value
2,
since
this
is
on
issue.
1
I
can
swap
it
into
the
key
value
1,
which
will
automatically
also
remove
that
key
value,
2
and
add
the
key
value
1
label.