►
From YouTube: GitLab 13.2 Kickoff - Plan:Project Management
Description
Planning Issue: https://gitlab.com/gitlab-org/plan/-/issues/104
A
Hey
everyone,
Gabe
Weaver
senior
product
manager
for
the
project
management
group
within
the
plant
stage.
You
get
lab
talking
to
you
all
about
13
in
what
we
hope
to
drop
in
the
upcoming
release.
So
nothing
huge
has
changed
since
our
major
focuses
in
13.1.
We
want
to
continue
iterating
on
iterations
pun
intended
and
where
we
got
mostly
in
13.1
was
the
ability
to
create
in
iteration
the
ability
to
associate
issue
to
it
and
a
very
rudimentary
issue
ListView
within
the
iteration
report
itself.
A
Our
long-term
goal
is
to
get
something
kind
of
more
closer
to
this,
where
the
top
is
actually
enough.
Some
stats
that
are
broken
down
about
completion
percentage,
you'll
be
able
to
toggle
your
charts
and
your
complete
percentage
by
wait,
count
or
time
as
teams
use
different
units
to
do
estimations
and
by
toggling
on
to
this
different,
yet
will
automatically
update
the
charts
and
then
the
other
thing
is
this
group
by
functionality.
A
So
we
will
be
able
to
group
by
label
group
by
assignee
also,
if
you're
in
a
in
the
parent
group,
you'll
build
a
group
by
projects
and
is
a
way
to
kind
of
dissect
that
and
different
from
how
milestones
work.
We're
actually
want
to
show
the
iteration
report
downstream.
So
if
I'm
in
a
sub
group
or
a
sub
project,
it
has
issues
associated
to
an
iteration
that
originated
in
the
in
the
topmost
group.
A
We
want
to
show
slices
of
that
report
view
within
each
of
those
contexts,
and
the
reason
for
this
is
like,
as
a
team,
you
might
have
permissions
and
access
to
projects
or
to
subgroup,
but
not
to
the
parent
group,
but
you
still
want
to
track
your
own
project.
Progress
against
your
contribution
to
that
iteration.
A
While
I
just
talked
about
other
things
in
terms
of
themes,
we
want
to
focus
in
some
quality
of
life.
Improvements,
ongoing
I,
think
this
is
where
issues
and
a
lot
of
the
artifacts
then
plan,
and
specifically
the
project
management
group
needs
some
love.
I
think
said
mentioned
in
this
AMA
that
we
are
doing
great
at
building
new
features
that
have
a
great
user
experience,
we're
not
doing
so
great
iterating
on
things
that
existed
before.
We
had
all
the
support
we
have
from
product
designers
and
UX
researchers.
A
So
one
of
the
things
that
we
want
to
do
is
make
it
so
that
you
can
remove
a
label
with
a
single
click
right
now,
it's
kind
of
clumsy
you
have
to
like
open
the
drop-down.
You
have
to
search
for
the
thing
you
want
to
remove
and
then
select
it
here.
We
just
want
to
make
it
so
that
you
can
remove
a
label
with
an
X
and
one
click.
This
should
make
it
easy
to
remove
things
and
then
pop
open.
A
The
Edit
view
whenever
you
want
to
add
links,
another
quality
of
life
improvement
that
were
working
towards
is
whenever
I'm
creating
a
an
epoch
within
another
epic.
You
can't
specify
what
subgroup
you
want
to
belong
to,
and
you
also
can't
move
epochs
right
now.
So,
as
a
first
iteration,
when
you
create
a
new
epoch
from
within
an
existing
epoch,
you
can
select
a
target
subgroup
that
you
want
to
more
less
assign
that
to
or
create
that
within.
A
So
that
way
will
automatically
roll
back
up
into
the
epoch
that
I'm
looking
at,
but
you
can
also
say,
if
there's
a
subgroup
that
doesn't
have
permissions
or
access
up
in
your
top
global
group,
they
can
still
see
that
sub
epoch
within
their
own
subgroup
without
having
to
have
access
to
the
parent
group.
So
good
flexibility
there,
especially
as
a
lot
of
folks,
are
starting
to
do
more
top-down
planning.
A
Another
thing
that
we
want
to
focus
on,
and
hopefully
we
can
get
to-
is
making
it
improving
the
label
management
across
groups
of
groups
and
projects.
So
the
basic
problem
right
now
is:
if
I
have
top-level
group
labels
and
I'm
in
a
project,
it's
deeply
nested
I
can't
see
any
of
those
labels
on
my
label
lists
and
I'm
duplicating
them.
I
can't
make
those
labels
prioritize
labels
within
my
projects.
I
can't
see
them.
So
that's.
A
The
first
thing
we
run
saw
here
is
show
all
inherited
labels
within
a
given
group,
so
group
project
label
lists,
but
really
the
gist
of
what
this
is
going
for
is
there
should
only
ever
be
one
label
with
the
same
name
within
any
hard
key
on
groups
of
bridge
projects.
So
that's
basically
the
goal
right.
A
This
also
kind
of
goes
hand
in
hand
with
something
that
I
wasn't
super
fond
of
initially,
but
I
kind
of
saw.
The
light
is,
there's
make
it
easier
to
get
start
with
issue
boards,
and
that's
done
by
just
make
use
of
the
you
have
default
lists
of
to
do
and
doing,
instead
of
prompting
them
with
the
decision
of,
should
I,
create
my
own
list
or
should
I
use
the
default
list.
A
We're
just
going
to
go
ahead
and
use
the
default
list,
and
the
reason
why,
if
you
want
to
read
and
catch
up
on
it,
actually
read
an
article
on
Hacker
News
a
couple
weeks
ago
that
just
talked
about
some
of
the
pain
points
with
project
management
as
a
whole
and
things
like
arguing
about.
If
it's
a
bug
like
what
did,
what
is
a
real
bug?
A
So
I
think
the
two
extra
clicks
to
remove
lists
you
don't
want
is
better
than
the
the
one-click
that
you
could
make
to
shoot
yourself
in
the
foot
and
make
a
more
complex
workflow
before
you
can
do.
So.
That's
that
and
then
the
last
thing
we'll
be
working
on
is
continued
progress
towards
the
swimlanes
MVC
epic
swim
lanes
that
we're
doing
with
portfolio
management
and
I
hope
we
get
to
launch
that
and
13.2
super
excited
about
it.