►
From YouTube: GitLab 13.4 Kickoff - Plan:Project Management
Description
Plan 13.4 Release Planning Issue - https://gitlab.com/gitlab-org/plan/-/issues/147
A
Hey
y'all
gabe,
weaver
senior
product
manager
of
the
project
management
group
in
the
plain
stage
of
get
lab,
bringing
you
the
13.4
release,
planning
issue
for
the
project
management
group.
It's
gonna
be
a
fun
release.
We're
gonna
highlight
a
couple
of
them:
real,
quick,
high
level,
we're
gonna
complete
the
iteration
chart
for
iterations
we're
also
gonna,
deliver
the
burn
down
trap
for
iterations,
so
real,
quick,
the
burn
down
chart
is
showing
you
your
actual
progress
against
your
estimator.
A
What
should
be
your
burn
down
for
how
many
issues
and
the
pace
over
a
given
iteration
that
you
should
be
bringing
your
issues
down,
and
this
is
going
to
be
selectable
by
weight
or
by
issue
count,
and
so
this
is
going
to
be,
I
think,
largely
driven
by
the
new
event
system.
We've
been
working
on
and
similar
to
that,
but
slightly
different
is
the
burn
up
chart
and
this
is
different
and
that
helps
you
track
and
understand
how
your
scope
changes
throughout
a
given
iteration.
So
you
can
see
if
scope
creeps.
A
A
But
if
you
don't
get
everything
done
completed,
that
was
added
you'll
kind
of
have
this
drift
between
the
two
and
be
able
to
see
that
maybe
you
added
too
much
scope
or
over
committed,
and
it
will
also
be
historically
accurate
and
that
if
you
move
issues
out
of
a
given
iteration
efforts
over,
none
of
these
charts
will
change,
which
has
been
a
big
pain
point
for
our
customers.
So
I'm
excited
to
see
these
two
things
come
to
the
iteration
report.
A
Once
we
get
the
iteration
report
a
little
bit
further
on
we're
going
to
be
back,
pointing
it
to
the
milestone
report
view
as
well,
so
we'll
get
a
fresh
view
app
based
mouse
and
report
view
in
the
very
near
future
on
the
performance
side
of
things,
we're
going
to
fix
an
m
plus
one
in
the
profiles.
Notifications,
controller-
and
this
is
in
your
notification
settings.
A
If
you
go
into
your
your
settings
here-
and
you
want
to
see
all
the
groups
and
projects
that
you
can
change
your
notification
settings
for
right
now,
if
you
have
or
the
member
of
a
lot
of
groups,
it
takes
approximately
one
minute
for
that
page
to
load.
That's
because
of
this
n
plus
one
plus.
There
is
no
pagination
in
that
view,
and
so
we're
committing
to
getting
this
n
plus
one
done
in
13.4
and
a
stretch
goal
for
the
team.
A
If
we
can
get
to,
it
is
adding
pagination
to
the
notification
settings
page,
and
this
is
under
quality
of
life
performance
improvements
goals
within
our
group,
that
we
have
every
milestone
and
yeah.
So
the
the
working
theory
right
here
is
that
if
we
fix
the
m
plus
one
we
add
pagination,
it
should
take
that
minute
down
to
under
a
couple
seconds.
For
that
view
to
load
which
would
be
great
performance
boost
for
the
application.
A
A
We
need
to
track
some
of
these
kind
of
lower
level
events
and
aggregate
distinct
counts
of
unique
users
across
those
events,
and
so
right
now
the
four
tables
that
contain
all
the
events
we
want
to
track
or
spread
across
these
four
different
database
tables
and
we're
going
to
add
the
ability
to
union
these
within
the
usage
things.
A
But
this
is
the
same
problem
that
we're
going
to
face
whenever
we
want
to
look
at
eventually
being
able
to
collect
total
unique
users
are
now
across
all
stages
and
interactions.
You
basically
have
to
start
with
events
like
these.
You
need
up
another
level,
then
you
need
up
another
level
to
get
to
the
stage
level.
Events
so
it'll
be
a
fun
challenge
to
solve,
and
I'm
hoping
we'll
start
to
make
some
good
progress
on
this
in
13.4.
A
If
you
have
any
questions,
you
can
go
check
out.
Leave
a
comment
on
this
release
issue:
it's
in
gitlab,
org,
slash
plan,
that's
issue;
147.
I'll
leave
a
link
to
this
in
the
youtube
video
as
well.
Thanks
for
watching
bye.