►
From YouTube: GitLab 12.9 Kickoff - Manage:Analytics
Description
Track what else is in store for Analytics in 12.9 via our planning issue for the release: https://gitlab.com/gitlab-org/manage/issues/15378
A
Hey
friends,
I'm
Jeremy,
Watson
I'm,
a
product
manager
here
at
gitlab
I'm
excited
to
talk
a
little
bit
about
12.9.
What's
the
store
for
the
analytics
group
as
part
of
the
manage
stage,
12.9
is
going
to
be
releasing
on
march
22nd.
We
have
a
lot
of
really
interesting
changes
in
store
make
the
analytics
group.
This
overall
goal
is
to
help
our
customers
and
users
really
better
understand
their
developments,
lifecycle
and
understand.
How
think
you
should
software
faster
and
find
bottlenecks
for
the
process
that
they
can
kind
of
help
alleviate.
A
A
So
what
we
want
to
do
is
we
want
to
actually
explicitly
add
these
terms,
indus
valley
stream,
analytics
to
make
it
more
valuable,
so
now
you'll
be
able
to
explicitly
see
these
KPIs
kind
of
in
the
product
and
be
able
to
understand
and
show
that
and
track
it
over
time.
The
other
thing
I'm
excited
about
is
project
health
analytics.
So
you
know,
as
we
use
value
stream
it
analytics,
is
kind
of
the
centerpiece
and
framework
for
how
we
think
about
analytics
and
get
lab.
A
We
want
to
start
having
deep
dive
analytics
features
that
help
you
really
understand,
like
different
parts
of
your
value
stream.
I.
Think
one
of
those
is
really
going
to
be
this
project.
Health
analytics,
which
is
attended
to
as
an
engineering
manager.
I
want
to
be
able
to
have
like
an
at-a-glance
understanding
kind
of
the
state
of
my
codebase,
where
I
can
see
cycle
time,
merge,
request,
status,
code
coverage
and
kind
of
like
bug,
status
at
a
glance
and
I
can
understand
kind
of
like
if
there
is
action
that
needs
to
be
taken
depending
on.
A
Why
see?
We
can
I
can
take
action
as
an
engineering
manager
without
having
to
develop
a
number
of
sensing
mechanisms
and
look
in
different
areas
of
the
project.
From
the
issue
board
to
merge,
requests
to
releases
to
environments,
I
get
to
see
everything
kind
of
in
one
place,
so
we're
going
to
start
with
it
with
us
with
a
small
NBC
in
12.9
that
introduces
kind
of
six
containers
in
this
new
feature.
A
We're
gonna
iterate
on
this
over
time
add
more
interesting,
visual
Asian
visualizations
in
KPIs
once
we
kind
of
validate
this
is
valuable,
but
I
think
that
that's
kind
of
the
vision
of
where
we
want
to
go
overall.
Our
goal
is
to
have
a
very
single
view,
high
level
dashboard
set
at
a
glance
as
a
project
maintainer
you
can
really
understand
and
at
moment's
glance
kind
of
what
is
happening
with
your
project.
A
The
review
time
is
currently
defined
as
the
time
it
takes
for
first
common
until
merged,
and
that's
not
the
definition
that
works
for
all
organizations,
and
so
we
want
to
make
this
more
useful,
but
making
her
the
logic
that
when
coder,
we
actually
starts
a
bit
more
flexible.
So
the
changes
that
we're
introducing
our
team
code
review
on
actually
assigning
an
amberjack
quest
to
someone
who
is
other
than
the
author
and
also
starting
code
review
time
after
the
merge
request.
First
approval.
A
So
any
of
these
events,
you
know
an
approval,
assigning
the
merge
request
to
someone
other
than
the
author,
and
also
a
line
comment
by
someone
than
the
author
are
all
going
to
start
triggering
code
review.
So
you
will
hopefully,
regardless
of
the
kind
of
the
way
that
you
review
and
manage
your
merge
requests.
You'll,
be
able
to
benefit
for
code
analytics
and
see
where
they
bottlenecks
are
kind
of
in
your
country
process.
It
that's
really
all
for
for
12.9.