►
Description
How a GitLab Product Manager uses GitLab in product planning tasks - In this video, I walk through converting an idea which has been discussed in an issue to a feature via epic promotion. Then I decompose that epic into individual issues which I can schedule in upcoming milestones.
A
Hello,
everybody
I'm,
Amanda,
reeda
I,
am
a
product
manager
with
the
product,
Planning
Group
in
gitlab
and
I
thought
I
would
share
my
screen
and
walk
you
through
one
of
the
things
that
I
do
very
often
in
my
role
as
a
product
manager
here
and
that
is
I'm
taking
an
issue
which
is
either
an
idea
or
an
opportunity
for
us
to
pursue.
In
this
case,
it's
already
been
vetted.
We
know
we
want
to
do
this
I'm
going
to
promote
this
to
an
epic
and
basically
kind
of
decompose.
A
What
needs
to
happen
and
create
all
of
the
kind
of
issues
that
I
want
to
assign
to
the
various
kind
of
steps
in
the
the
dev
flow
that
we
have
here
at
gitlab.
So
I
thought
it'd
be
a
good
chance
to
record
this
and
put
it
on
the
dog
fooding
playlist,
for
you
to
see
how
I
do
this,
so
this
is
something
that
we
had
intended
to
do.
It's
with
our
work
items
initiative.
A
It's
the
problem
is
well
known.
We
just
have
to
create
parity
of
these
features
of
being
able
to
copy
the
reference
and
the
email
I
have
designs
approved
by
our
ux
designer,
so
I
am
ready
to
kind
of
create
a
I
like
to
think
of
it
as
a
package.
So
I'm
going
to
promote
this
to
an
epic
is
my
first
step
because
it's
currently
under
my
kind
of
ultimate
parent
of
the
initiative
of
work
items
and
I
want
to
create
a
sub
epic
of
that
ultimate
parent.
A
So
now
I'm
in
my
epic,
my
sub
epic,
as
it
were,
and
what
I'm
going
to
do
first
is
since
I
already
have
the
ux
approved
I'm,
just
going
to
add
that
information,
so
that
I
have
an
ssot
of
the
design.
Let's
see,
okay
I
found
the
comments
where
our
designer
said
that
we
can
follow
the
changes
and
gave
information
about
where
it
can
be
located.
So
I'm
going
to
go
ahead
and
save
this
so
yep,
okay,
cool.
So
now,
I
have
my
container
for
this
kind
of
feature.
A
So
to
do
this,
I
will
because
I'd
like
to
have
a
ssot
of
the
information
and
not
have
different
information
in
every
issue,
because
it
might
get
out
of
sync.
I
will
just
have
a
generic
summary.
This
is
back
end
issue
for
and
I'll
just
drop
the
epic
and
then
I'll
indicate
where
they
can
find
the
designs.
A
A
It
adds
all
of
my
labels,
feature
I'm,
going
to
add
my
Milestone,
so
I
think
this
one
I
believe
I
have
room
in
16
and
so
now
I'm
in
a
stagger
I'm
going
to
wait.
16
is
our
not
the
Milestone
starting
in
a
few
days,
but
after
that
one
so
I'm
going
to
save
these
changes
apply,
do
a
quick
refresh
and
we
should
see
the
blocking
work.
We
should
see
my
labels.
A
A
So
here
we
go
I'll
add
a
couple
more
labels
to
this
one,
because
when
this
lands
I
want
documentation
for
this
I'm
going
to
want
to
mention
this
in
the
release,
post,
I
think
that
that's
all
set.
So
now,
if
I
go
back
to
my
sub
Epic
and
I,
take
a
look
at
my
children.
I
can
see
that
the
back
end
is
scheduled
for
16.
I
have
all
my
labels
and
then
my
front
end
is
scheduled
for
61..
A
So
there
you
have
it.
That's
how
I
take
a
single
issue
promoted
to
an
epic
and
why
I
do
it
so
that
it's
this
kind
of
single
feature
release
within
the
larger
initiative,
rather
than
being
a
bunch
of
issues
underneath
that
larger
ethic
and
then
I
break
it
into
individual
parts
so
that
I
can
have
individual
assignees
individual
weight,
individual
Milestone
assignments
and
then
I
can
stagger
my
work.