►
From YouTube: GitLab 13.5 Kickoff - Plan:Project Management
Description
13.5 Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/159#project-management-gabe-kickoff-video
A
I've
laid
out
this
planning
issue
based
on
our
prioritization
table.
This
is
probably
the
only
time
or
the
last
time
that
I'll
be
presenting
the
planning
issue.
This
way
stay
tuned
for
a
new
way,
new
approach
to
doing
this,
the
next
release
vmr
that
I'm
going
to
open
up,
but
we
have
kind
of
a
mix
of
things
this
release,
which
is
interesting.
A
But
what
we
were
able
to
figure
out
this
last
week
is
that
we
can
use
the
redis
counter
to
do
this
in
a
performant
way,
and
so
we're
going
to
experiment
with
that
in
13.5
to
see
if
we
can
instrument
all
these
events
with
res
counters
and
then
do
that
distinct
aggregation.
So
we
can
get
a
more
accurate
amount
number
and
that's
kind
of
going
to
be
pretty
exciting
there
as
well
one
of
the
things
that
we
want
to
do
in
terms
of
usability.
This
came
out
of
our
category
of
maturity
scorecard
work.
A
Thank
you,
holly
for
doing
an
amazing
job.
There
is
we
want
to
make
promoting
issues
to
epic
more
discoverable
right
now.
It's
just
stuck
in
a
quick
action.
You
do
slash
promote
and
then
it
will
turn
the
issue
into
an
epic,
but
that's
not
exactly
intuitive,
and
no
one
in
our
test
knew
that.
So
what
we're
going
to
do
is
refactor
kind
of
the
header
of
the
issue
to
support
this
new
little
drop
down
thing
and
we're
going
to
start
moving
some
of
the
global
issue.
A
Actions
into
this
drop
down
things
that
are
also
upcoming,
which
I'll
talk
about
cloning,
an
issue
moving
issue
promoting
an
issue
into
an
epic,
creating
a
new
issue,
reporting
abuse.
These
are
all
sort
of
like
global
actions,
and
we
want
to
consolidate
them
within
this
one
menu
item
and
make
it
available
both
in
the
in
the
primary
header
as
well.
A
This
is
the
sticky
sticky
header
on
the
issue,
as
you
scroll
down
this
kind
of
falls
in
line
with
what
people
currently
do
already,
when
you
scroll
down
an
issue-
and
you
can
kind
of
see
within
the
comments
here-
you
can
kind
of
open
this
menu
and
a
lot
of
our
users
that
we
talked
to
and
and
kind
of
did
some
test
scenarios
on
would
always
scroll
up
and
sort
of
expect
that
same
thing
up
here
in
the
header,
and
it
makes
sense.
So
that's
what
we're
going
to
work
towards
excited
about
that.
A
Another
usability
improvement
that
we
want
to
make
right
now
is.
If
I
have
a
top
level
group,
I
cannot
see
those
labels
within
my
deeply
nested
project,
which
means
I
also
cannot
use
priority
labels.
If
my
labels
have
been
inherited
from
a
top
level
group,
so
what
we're
going
to
do
is
they're
already.
You
can
already
assign
issues
to
these
top
level.
A
Group
labels
we're
just
going
to
make
them
show
up
within
the
issue
list,
so
you
can
also
use
priority
labels
within
the
projects
that
you're
at
the
other
thing
we
want
to
do
is
fix
the
ux
for
applying
drop-down
selections.
So
one
of
the
things
that
was
confusing,
particularly
with
assignees.
When
you
look
at
this
and
you
want
to
go
change
an
assignee
I
can.
I
can
kind
of
change
that,
but
it
doesn't
really
indicate
that
it's
saved.
A
A
We
have
an
edit
button
instead
of
button,
we'll
close,
that
this
drop
down
arrow
will
also
close
and
save,
and
this
x
will
not
really
do
anything
but
there's
next
there,
and
then
you
also
have
to
search
for
users,
and
this
is
like
the
same
problem
across
a
lot
of
our
dropdowns
and
it's
super
confusing.
Why
would
duplicate?
This
is
a
due
date?
This
is
a
due
date.
A
We're
going
to
change
the
edit
button
to
actually
read
apply,
so
you
can
click
out
to
save
or
you
can.
Click
apply
to
save,
which
will
close
the
drop
down
and
turn
the
button
back
into
edit.
It's
a
small
thing,
but
it
will
make
using
these
drop
downs
within
the
sidebar
and
across
the
product
a
lot
more
usable,
and
this
will
be
a
core
change
to
pajamas.
Hopefully,
so,
if
we
make
the
change
in
one
place,
it
should
propagate
to
everywhere.
That
is
using
the
pajamas
components
which
goes
back
to
that
efficiency.
A
You
change
it
one
place.
It
changes
everywhere.
Great
everybody
wins.
This
is
a
stretch
goal,
but
we
would
also
like
to
get
to
be
on
the
clone,
an
issue
with
the
quick
action
and
also
with
the
ui,
as
I
showed
you
before
right
now,
if
I'm
working
on,
let's
say
an
epic-
and
I
know
that
I
have
bullet
points
for
the
five
issues.
I
need
to
create.
A
The
title
all
that
stuff,
so
really
all
you
have
to
do
is
tweak
the
few
things
you
want
to
tweak
within
that
specific
issue:
save
and
you're
off
to
the
races
in
line
with
moving
and
improving
on
iterations.
One
of
the
things
that
is
not
working
super
well
is
that
iteration
state
within
the
report
view
is
mutable
like.
So,
if
I
were
to
finish
an
iteration
and
then
I
move
all
the
issues
out.
My
completed
percentage
is
an
incomplete
and
unstarted
all
that
that
number
changes
as
well.
A
So,
there's
not
really
a
historical
record
of
what
I
really
did
complete
or
what
my
team
did
complete
in
a
given
iteration.
We
already
have
the
the
data
in
the
back
end,
to
be
able
to
do
this
as
part
of
working
on
burn
up
charts.
So
what
we
want
to
do
is
make
sure
that
these
numbers
don't
change
when
iteration
ends.
Basically
so
anytime,
I
can
go
back
in
the
future
and
go
back
to
previous
iteration
and
see
historically
accurate
immutable
stats
on
how
my
team
did
during
that
iteration.
A
It's
a
small
change,
but
it
is
one
of
those
things
that
if
people
want
to
trust
the
iteration
reports,
the
iteration
report
shouldn't
change
once
the
iteration
is
over.
And
lastly,
one
of
the
things
that
I'm
getting
really
excited
about
is
we're
getting
close
to
being
done
with
the
first
two
phases
of
our
real-time
working
group.
The
only
thing
we
have
left
to
do
with
in
phase
one
is
add
the
usage
ping.
So
that
will
be
part
of
that
work
that
I
kind
of
highlighted
earlier
about
which
instances
have
enabled
action.
A
That
will
then
enable
us
to
add
real-time
functionality
to
all
the
other
fields
in
the
sidebar
and
then
eventually,
real-time
boards,
so
super
stoked
about
this-
and
I
I'm
thankful
for
john
hope
and
heinrich
and
all
the
other
folks
that
have
been
contributing
to
this.
It's
been
a
pleasure
to
work
with
them,
so
that's
it
for
highlighting
13.5
for
the
project
management
group.
I'm
excited
about
it.
I
hope
you
are
too
until
next
time.