►
From YouTube: GitLab 13.1 Kickoff - Plan:Project Management
Description
13.1 Release Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/100#project-management-gabe-kickoff-video
A
Hey
this
is
Cape
Weaver
senior
product
manager
at
the
project
management
group.
In
the
plan
stage,
we're
gonna
be
talking
about
our
13
that
long
kick
off
lots
of
balls
in
the
air.
A
lot
of
things
you're
trying
to
wrap
up
that
are
pretty
close
to
finish
line
at
high
level.
We're
gonna
continue
working
on
iterations
and
improving
our
time
box
reports.
A
So
the
basic
gist
of
this
is:
we
have
the
basic
ability
to
create
an
iteration
and
associate
an
issue
to
it,
but
we
don't
have
a
ton
in
terms
of
what
you
see
within
the
iteration
report
itself,
so
in
13.1
we're
gonna
work
on
an
MVC
for
the
iteration
report
view
and
as
soon
as
we
have
this
MVC
done,
we'll
make
this
generally
available.
It's
going
to
follow
a
similar
pattern
to
milestones,
but
in
this
case
we're
building.
A
A
But
you
can
actually
check
out
a
video
of
this
working
in
a
local
environment
on
master,
which
is
pretty
cool,
I'm
not
going
to
show
it
here,
but
you
can
update
in
assigning
an
one
client
and
see
it
automatically
update
another.
So
that's
getting
exciting
we're
getting
pretty
close
to
having
this
first
field
of
in
real
time
via
WebSockets.
A
Next
up,
Jeremy
er
we're
going
to
continue
making
progress
here
in
39.
We
ran
in
a
couple
roadblocks
in
terms
of
how
to
approach
user
mapping
and
how
to
approach
parsing,
jura,
syntax,
and
comparing
that
to
get
that
flavor
markdown.
We
ran
a
couple
research
spikes
in
both
directions
and
kind
of
hit
a
few
brick
walls
and
had
to
backtrack
a
little
bit.
A
But
I
think
we
settled
on
a
way
that
we're
going
to
do
mapping
issues
or
mapping
users
from
jarred
ticket
lab
and
that's
basically
consists
of
showing
display
name
for
all
the
terior
users
and
allowing
gitlab
within
the
UI
to
select
from
a
drop-down
members
of
the
existing
project
that
they
want
to
map
to.
We
opted
for
this
over
the
CSV
just
because
you
don't
have
to
leave.
A
Get
lab
to
get
it
working
and
you
don't
have
to
go
export
a
list
and
then
cross-reference
that
with
a
project
members
list
on
the
project,
but
in
the
future
we
might
support
uploading,
a
CSV
or
a
JSON
file.
If
that's
desirable
back
to
next
thing,
we
also
are
working
on
a
number
of
quality
of
life
improvements,
and
this
is
in
conjunction
with
the
UX
and
engineering.
Ok,
art
for
love
ability
and
UX
improvements,
as
well
as
performance.
Some
there's
a
large
list
of
target
areas
we
may
focus
on.
A
If
you
want
to
click
through
that
issue,
you
can
look
it
up
for
this
particular
release.
We're
gonna
make
it
so
easier
to
remove
labels
from
issues.
Epics,
merge,
requests
and
hopefully
doing
that
with
a
single
click.
We're
still
settling
on
the
best
implementation
approach
will
either
do
it
with
an
X
or
we're
going
to
show
all
the
applied
labels
and
the
top
of
the
label
picker.
A
Whenever
you
open
it,
we're
still
exploring
which
one
would
be
more
performant,
there's
trade-offs
of
both,
so
we
haven't
settled
there,
but
we'll
hopefully
get
some
feedback
from
some
of
the
research
we're
doing
within
a
couple
days
to
solidify
the
right
path.
There
we're
also
going
to
work
on
sticky
issue,
titles
and
issues,
and
hopefully
epics
and
maybe
in
Mars.
If
that
works
there,
but
the
basic
idea
is
we
want
to
keep
the
the
tile
sticky.
So
if
you
get
deep
linked
into
an
issue,
you
understand
what
the
context
is
right
away.
A
Eventually,
so,
there's
lots
of
exciting
things
here,
we're
doing
to
try
to
improve
issues
and
the
main
problem
we
want
to
solve
is
making
it
so
that
people
won't
have
to
scroll
up
and
down
to
interact
with
the
issue.
So,
if
you're,
deep
in
the
comments,
we
want
you
to
be
able
to
edit
the
issue
title
and
the
description
and
then
return
right
back
to
where
you
were
reading,
so
you
don't
have
to
scroll.
That's
the
long-term
goal
with
that.
We
also
are
working
on
the
ability
to
assign
an
epoch
to
a
subgroup
from
creation.
A
So,
right
now,
when
you
are
creating
an
epoch
at
a
top-level
group,
you
can't
create
that
they
can
assign
it
to
a
subgroup.
So
this
is
kind
of
what
it
looks
like
now
and
what
will
look
like
after
is
you
can
select
the
subgroup
that
you
want
to
sign
this
to
and
so
we'll
the
benefit
of
this
is
you'll,
be
able
to
do
kind
of
top-down
planning.
A
If
you
have
a
subgroup
that
you
know
is
part
of
your
portfolio
in
value
stream,
you
can
create
the
Epicurus
I
it
there
automatically
have
it
show
up
within
your
your
epoch
that
you're
planning,
as
well
as
in
that
subgroup
level.
So
it's
pretty
would
be
a
nice
thing
for
the
creation
of
epochs
with
epics.
We
also
want
to
fix
the
select
and
search
inputs
across
the
product.
This
is
a
big
headache
when
you
try
to
move
an
issue,
there's
a
lot
of
different
problem
areas.
A
What
if
you
don't
try
to
create
an
issue
from
a
group
level
project
issue
list?
You
can
only
see
a
couple
of
the
items,
usually
not
the
project
that
you
want
to
target.
So
we're
going
to
look
across
the
board.
Do
an
audit
of
where
all
the
places
we
need
fixes
and
try
to
do
it
in
a
more
global
manner,
so
that
there's
better
experience
across
board
using
that
component
and
then
the
last
one
for
quality
of
life,
we're
going
to
work
on
properly
showing
inherited
labels
within
projects.
A
So
that's
one
of
the
things
we
want
to
focus
on
fixing
and
then
we're
also
going
to
be
clubbing
with
the
portfolio
group
to
work
on
epic
swim
lanes
on
issue
boards.
It's
a
really
important
thing.
We
want
to
contribute
to
and
we're
gonna
put
all
the
resources
we
can
to
move
that
forward
with
portfolio
management.
That's
it
for
13.1
again.
If
you
want
to
look
at
this,
you
can
issue
100
and
the
planned
project
and
get
a
better
work
thanks.