►
Description
How a GitLab Product Manager uses GitLab - Reviewing issue progress in the current milestone.
A
A
We
have
monthly
Milestones,
they
run
the
18th
of
the
month
to
the
17th
of
the
subsequent
month,
and
so
right
around
this
time,
when
we're
in
the
middle
I
have
a
pretty
specific
set
of
tasks
that
I'm
doing
to
make
sure
things
are
on
track
and
prepare
myself
for
the
next
Milestone,
so
I'll
share
my
screen
and
I'm
typically
completing
this
set
of
tasks
here
in
the
issue
board.
This
is
my
favorite
view
where
I
have
the
current
Milestone
as
a
list
and
the
next
couple
of
Milestones
as
lists
as
well.
A
This
allows
me
to
very
easily
move
things
in
and
out
of
the
Milestone,
depending
upon
feedback.
I
get
change
in
priorities.
I
will
typically
never
disrupt
a
current
Milestone
unless
it's
a
P1
a
kind
of
severity
issue,
but
I
might
find
that,
like
during
this
time
as
I'm
scanning,
how
things
are
going
I
might
find
like
a
newly
blocked
issue
and
as
I
read,
more
information
identify
that
hey
that
thing's,
just
not
going
to
ship
in
this
Milestone
there's
no
possibility
and
it
was
unforeseen
when
I
was
planning
and
so
I'll
move
that
out
here.
A
So
let
me
just
walk
you
through
the
steps
that
I'm
taking
so
the
first
thing
I'm
doing
is
because
this
is
mid-month
and
I
still
have
half
of
a
milestone,
left
I'm
looking
for
things
that
are
maybe
carryovers
from
the
prior
Milestone
and
sitting
in,
like
a
verification
or
in
review
and
I'm,
just
checking
out
those
issues
to
see
what
the
progress
is
and
see.
If
there's
any
blockers
that
I
can
help
with
in
this
case,
I
think
that
this
was
actually
closed
out,
but
I
am
double
checking
with
the
developer.
A
Before
we
close
the
issue,
I
think
there
was
just
a
step
Miss,
so
the
other
thing
I'm
looking
for
as
I
mentioned,
is
work
that
might
be
newly
blocked.
This
particular
issue
was
blocked
when
it
entered
the
Milestone,
but
we
have
hopes
that
it's
going
to
unblock
here
soon,
so
I'll
leave
that
alone
and
the
other
thing
I'm
looking
for
is
issues
that
haven't
been
picked
up
yet
so
something
that
might
be
ready
for
development,
or
in
this
case
this
one
is
still
in
planning
breakdown.
A
Has
it
been
broken
down
yet
I'm
going
to
go
into
those
issues
and
see
what's
up
so
this
is
one
that
I
actually
just
I
added
pretty
late
to
the
Milestone
and
that's
why
it
hasn't
been
broken
down
yet
and
so
I
have
tagged
the
engineering
manager
and
asked
for
a
weight
to
be
added,
typically
I'm
doing
that
before
the
Milestone
starts.
But
in
this
case
it
we
had
extra
capacity
because
folks
grabbed
everything
my
planned
and
we
brought
in
a
few
extra
things.
A
So
I'm
just
looking
for
anything
that
might
be
sticking
out
to
me.
That's
a
spike.
Let's
see
what
else
ready
for
Dev
this
one,
it's
a
one,
so
that
makes
sense
why
it
hasn't
been
picked
up.
Yet
this
one
needs
a
weight,
so
I'm
gonna
tag
somebody
on
this
to
get
a
weight
on
it,
so
I
can
move
it
to
ready
for
Dev,
and
you
can
automate
a
lot
of
these
tasks.
If
you
can
Define
them,
you
can
automate
them
with
like
Bots.
A
A
A
That
doesn't
happen
all
the
time,
but
it
happens
sometimes,
and
so
in
that
case,
I
would
move
some
additional
pieces
of
work
in
to
the
bottom,
because
I
have
my
list
in
priority
order
and
I
would
tag
my
em
to
let
him
know
that
new
stuff
has
come
in.
At
the
same
time,
I
might
be
looking
for
things
that
maybe
aren't
blocked,
but
just
don't
make
sense
anymore
to
be
done
in
this
current
Milestone.
A
If
priorities
have
changed
so
I
might
pull
a
couple
things
out
and
put
it
in
a
future
Milestone
but
again
I
try
not
to
disrupt
the
monster
once
it
started
too
much,
and
this
will
be
the
time
where
I'm
going
to
start
looking
at
the
next
Milestone
and
adding
things
here
from
the
future
and
then
also
reordering,
so
that
it's
in
priority
order.
So
this
is
how
I
use
a
board
to
see
how
things
are
going
in
my
current
Milestone
to
communicate
with
my
team
members
and
to
look
ahead
hope.
It
was
helpful
thanks.