►
From YouTube: GitLab 13.0 Kickoff - Analytics
Description
Agenda and issue links for the Manage stage are publicly available at https://docs.google.com/document/d/e/2PACX-1vRnN91k9Rx1AyF8cIQga3KGFpjkI-sheTB16Jg-4e8fO3snZas2Th4hJC5C5wKIrNWbzr8aYDjI-T7-/pub.
A
Hello
and
welcome
to
the
release
kickoff
for
get
lab,
13.0,
I'm,
John,
Shackleford,
new
product
manager
for
analytics
and
today,
I'll
be
covering
three
initiatives
and
baby
steps
were
taking
and
release
13
to
bring
greater
functionality
in
that
area.
To
you,
let's
start
with
a
first
issue
in
this
issue.
What
we're
going
to
tackle
is
the
idea
of
providing
an
additional
drill
and
experience
to
our
issues
analytics
capability.
A
This
is
a
baby
step
towards
a
larger
initiative
where
we
want
to
bring
this
capability
not
just
to
this
chart,
but
to
any
of
the
charts
that
we
make
available
in
analytics,
and
so
our
attention
is
not
to
just
deliver
this
capability,
but
also
the
underlying
framework
that
we
can
then
apply
to
each
of
our
charts
and
turn,
and
so
after
release
13.
You
can
expect
to
see
this
showing
up
in
a
lot
more
places
as
well.
A
The
next
issue
I
want
to
talk
about
is
the
SLA
story
that
we
were
mentioning
earlier
again:
customers
often
use
workflow
labels
or
team
oriented
labels
to
indicate
who's,
got
the
ball.
What
state
it's
in
and
so
on
and
an
important
question
when
you're
looking
at
SLO
s
is
you
know?
How
long
is
that
label
been
on
that
MRR
or
on
that
issue?
A
How
long
has
it
remained
in
a
given
state-
and
it's
not
too
hard
today
with
our
api-
is
to
get
that
information
one
issue
at
a
time,
but
if
you
want
to
look
across
all
project
or
a
group
that
gets
a
lot
more
tricky
requires
a
lot
of
custom
scripting.
We're
gonna
enhance
the
API
in
order
to
allow
you
to
pull
that
for
quite
a
few
items
at
once.
First
using
standard,
Jason
based
api's
and
then
we'll
follow
on
with
CSV
export,
so
that
that
data
is
even
more
consumable
now.
A
A
We've
got
a
lot
of
ambition
for
where
we
would
like
to
take
this
we're
going
to
start
with
some
baby
steps
that
just
involve
correcting
some
things
in
the
back
end
and
the
api's
that
will
allow
us
to
track
some
really
important
pieces
of
data
so,
for
example,
the
way
that
we're
recording
time
stamps
today
for
to-do
items
makes
it
impossible
for
us
to
tell
how
much
time
has
been
spent
on
given
to
do.
Well.
A
That's
really
important
to
know
how
long
to
do
is
waiting
so
that
we
can
help
prioritize
those
and
and
also
alert
you
and
others
when
things
are
have
been
waiting
so
long
that
they're
unlikely
ever
to
be
done
to
make
sure
that
things
that
are
urgent
or
getting
their
attention
and
then
we'll
also
be
updating
the
API.
Similarly,
so
that
we
can
pull
this
data
out
and
I've
been
getting
doing
some
calculations
after
that,
you'll
see
more
and
more
work
on
this
capability
and
really
look
forward
to
your
feedback
on
that.