►
From YouTube: Manage:Analytics 13.3 Planning Meeting
Description
See our planning issue at: https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17138
A
A
So
we
have
been
working
off
this
planning
issue
which
I
had
but
just
a
moment
ago,
13
30
planning
and
we
did.
The
team
did
awesome
work
on
knocking
out
tons
of
estimations
all
through
the
week.
So
we
are
in
a
good
place,
with
lots
of
content
for
the
release.
Here's
our
rank
order
of
things,
and
then
I've
been
trying
to
reconcile
that
on
a
new
planning
board
that
breaks
down
the
front
end
and
back
into
the
issue.
So
we
can
get
a
kind
of
a
total
number
of
points
and
figure
out.
A
You
know
when
we're
full
one
tricky
thing
with
boards.
I
discovered
this
week
is
that
you
cannot
both
look
at
items
in
a
milestone
and
items
not
assigned
to
any
milestone
at
the
same
time,
which
is
really
a
pain.
It
would
be
nice
to
have
you
able
to
see
all
the
things
that
are
estimation
needed
and
not
assigned
to
any
milestone
and
then
just
be
able
to
drag
them
over
to
assign
them,
but
no
can
do
so.
A
A
A
B
B
One
thing
I
I
recall
from
from
one-on-one
earlier
with
the
safe
kill,
was
that
he
said
he
he
underestimated
some
of
the
issues,
especially
the
the
filtered
one,
which
I
believe
we
we
we
estimated
as
a
two
or
three,
but
eventually
it
was
more
towards
a
five.
So
I
think
if
we,
if
we
take
the
total
amount
or
the
total
weight
for
13.2,
I
guess
it
was
actually
a
little
higher
than
than
was
originally
estimated.
So
I
could
take
a
look
and
I'll
do.
A
You
know
there
are
a
few
items
for
which
we
don't
don't
actually
have
estimates
down
here,
so
I
have
to
figure
out
what
what
to
do
about
them,
but
they're
they're,
primarily
back-end
related
to
bugs
that
we
wanted
to
fix,
but
yeah,
I
think,
for
the
most
part,
we've
got
the
back
or
we've
got
the
rank
order.
The
question
is
what
fits
and
and
that's
what
this
board
was
supposed
to
help
us
try
to
answer.
A
C
B
A
Good,
well,
we
have
the
good
news.
Is
we
have
enough?
Because
I
I
see
29
more
points
worth
of
points
for
the
front
end
here.
So
that's
good.
I'd
rather
have
too
much
than
not
enough,
and
we
can.
We
can
just
start
pulling
things
out
until
we
get
to
a
size
that
we
like.
That's
one
thing
I
hadn't
thought
of
is:
where
do
we
put
them
if
they
are
not
going
to
fit
see.
B
B
So
some
of
the
of
the
stuff
is
already
shared,
but
not
like
the
filter
bar
itself
and
that's
something
where
we
would
like
to
spend
some
time
and
effort
into
creating
one
shared
component.
Eventually,
that's
something
that
we
can
re
use
for
all
our
analytics
features.
I'm
not
sure,
if
that's
that,
if
that
will
also
fit
the
generic
report
page,
because
we
have
a
few
like
exceptional
requirements
for
generic
reports,
but
for
all
for
all
the
other
features.
B
That's
something
that
we
would
like
to
work
on
to
basically
combine
what
you
already
have
and
create
a
uni
or
a
generic
component.
So
I
think
that
that's
something
that
I
talked
to
michael
about
and
he
wants
to
take
the
lead
on
that.
I
believe
we
should
also
move
that
to
the
to
the
front
and
column.
I
guess
we
can
probably
add
a
weight
of.
B
A
A
A
B
A
C
A
B
B
A
A
A
A
A
A
A
A
A
A
B
One
thing
that
we
could
probably
also
try
to
have
another
team
to
work
on
is
the
the
stacked,
the
stacked
the
group
and
stacked
gitlab
ui
component.
I
remember
there
there
were
other
teams
in.
If
I
remember
correctly,
there
were
other
teams
also
interested
in
this
component,
so
maybe
we
can
also
reach
out
to
maybe
the
monitor
team
to
see
if
they
also
have
capacity
to
to
fit
this
into
into
the
next
milestone.
B
It's
it's
on
the
on
the
edge.
I
definitely
not
not,
I
wouldn't
add
any
anything
else.
I'd
rather
try
to
do
to
scope
it
or
narrow
it
down,
maybe
a
little
more
depending
on
on
on
the
carryover.
So
we
can
let
let's
keep
it
for
now,
and
maybe
we
can
refine
it
one
more
time
on
friday,
depending
on
the
update
that
michael's
going
to
give
me
okay.
B
C
A
C
C
Which
I'm
guessing
is
like
two
yeah
that
that
one
right
there
right
so
back
end
in
recent
months
april,
26
may
23
june
12.,
so
we
had
a
weird
month
in
june,
but
I'm
I'm
thinking
like
around
20
is
about
right
normally,
but
of
course
we
have
magda
out
for
almost
the
whole
milestone
so
reduce
capacity
there.
So
I
think
we
should
probably
be
staying
under
20..
C
Another
thing
to
consider
here
is
that
adam
being
a
database,
maintainer
has
just
been
flooded
with
code
reviews
lately
and
it's
a
lot
of
his
capacity
like
half
or
like
this
week.
More
than
half
so
yeah,
I'm
I'm
thinking
17
is
like
you
know,
actually
probably
a
little
bit
we're
probably
at
the
top
of
our
expected
capacity
here
for.
A
All
right
great,
this
has
been
a
good
planning
session.
Thank
you
very
much.
I
will
take
the
action
to
add
a
stretch
label
to
a
few
of
these
and
then
everything
that
didn't
fit,
we'll
move
to
workflow
scheduling
and
then
for
for
those
things
which
and
and
I'll
remove
the
milestone,
I'll
put
the
others
in
what
what
workflow
state
should
we
put
the
others
in
maybe
go.