►
From YouTube: Manage:Analytics 13.6 release kickoff
A
Hey
there
team,
my
name
is
nick
post
and
I'm
the
senior
product
designer
for
manage,
analytics
and
I'll
be
standing
in
as
pm
for
analytics
in
13.6,
and
I
want
to
talk
to
you
today
today
about
some
of
the
great
things
that
we
had
scheduled
for
for
13.6.
A
So
we
have
two
key
personas
that
we're
focusing
on
within
this
milestone.
The
first
persona
is
our
application
development
director
and
this
development
director
is
specifically
within
the
enterprise
devil's
reports
category
and
with
regards
to
this
persona,
they
are
looking
to
understand
more
effectively
how
git
lab
is
being
used
and
then
the
impact
on
their
organization
and
their
workflows
since
adopting
gitlab.
So
that's
one
of
the
key
things
that
will
be
helping
to
add
some
some
functionality
and
insight
around
and
then.
A
Secondly,
we
will
also
be
helping
our
everyday
gitlab
team
members
and
everyday
users
with
some
some
general
dog
fooding
features
as
well.
So
our
key
objectives
here
are
to
lay
the
foundations
for
devops
reports
as
a
feature
set
for
our
application
development
director
and
also
continue
providing
some
great
features
which
will
be
used
by
git,
lab
team
members
and
everyday
users
in
in
software
development
teams
as
well
as
this,
we
hope
to
also
add
some
components
to
our
data
visualization
library.
A
So
we
can
continue
to
build
better,
ux
and
and
and
ship
with
greater
velocity
through
using
reusable
components.
A
So
I
want
to
show
you
our
billboard
and
point
out
a
few
of
the
things
that
I'll
take
you
through.
So
with
regards
to
our
devops
reports,
we
have
a
devops
reduction
adoption
mvc
right
here
we
have
a
devops
segment
which
goes
hand
in
hand
with
this.
We
also
have
user
availability
which
we'll
dive
into
in
a
bit
as
well
as
some
great
enhancements
to
mr
analytics
and
potentially
issue
analytics,
as
well
so
for
the
devops
adoption
nbc.
As
I
mentioned
before,.
A
So
we're
going
to
start
here
with
an
mvc
that
looks
a
little
bit
like
this,
showing
how
different
segments
which
I'll
talk
about
in
a
bit
are
adopting
different
parts
of
gitlab,
with
a
boolean
expression
of
true
or
false,
and
seen
that
across
some
of
our
most
popular
feature
sets.
This
will
then
be
iterated
to
include
more
features
and
functionality
in
later
stages,
but
we
found
that
this
is
a
nice
balance
of
an
mvc
to
show
some
of
the
the
features
that
are
being
adopted
across
a
number
of
segments.
A
So
based
on
on
that,
there
are
a
number
I'll
I'll
show
you.
The
issue
around
segments
and
segments
are
a
way
of
categorizing
or
bringing
together
different
groups
and
projects
and
subgroups
in
one
predefined
segment
is
what
we're
calling
it.
So
this
allows
you
to
add
groups
to
a
segment
as
well
as
exclude
subgroups
and
projects
as
well.
In
our
first
iteration,
we
will
just
be
having
top
level
groups
within
our
segments
and
then
in
later
iterations.
We
will
add
subgroups
and
projects
and
the
ability
to
exclude
them
from
this
functionality.
A
So
we
get
more
finite
control
over
what
actually
is
seen
within
the
segment,
so
segments
and
devops
reports.
Adoption
will
go
hand
in
hand
and
we'll
have
users
being
able
to
define
a
new
segment
with
top
level
groups.
A
And
then
these
segments
will
show
up
within
the
devops
adoption
table
and
we'll
see
how
different
features
are
adopted
for
each
of
these
segments,
meaning
that
our
application
development
directors
have
a
better
understanding
of
what
parts
of
their
company
or
what
parts
of
the
organization
are
are
using,
are
using
git
lab
and
how
effectively
that's
happening.
A
A
And
what
we're
finding
is
that
this
status
is
can
be
quite
difficult
to
report
on,
because
there's
no
standardized
way
of
showing
whether
or
not
you
are
busy
or
whether
you're
out
of
office
and
so
on,
meaning
that
we
can't
be
100
sure
when
trying
to
create
different
analytics
pages,
whether
or
not
a
user
is
actually
busy
or
not
until
until
we
have
some
standardized
way
of
solving
that
problem,
which
means
that
we
don't
have
the
data
for
things
like
reviewer
or
maintainer
dashboards,
availability,
dashboards.
Things
like
that.
A
So
this
right
here
is
a
feature
that
not
only
helps
users
communicate
their
availability
and
status
of
whether
they're
busy,
but
also
sets
up
the
foundation
at
a
later
stage
for
us
to
gather
the
data
in
order
to
have
some
more
sophisticated
analytics
around
merger
crest,
merge,
request,
reviewers
and
and
availability.
A
So
this
right
here
is
set
user
availability
and
effectively
as
an
mvc,
really
simple,
we're
going
to
add
a
check
box
right
underneath
this,
this
status
status
box
and
if
you
check
that
box.
Yes,
that
will
add
a
busy
indicator
and
text
next
to
your
name,
and
this
will
appear
in
various
parts,
the
product
and
from
there.
A
A
A
And
then
mr
analytics
is
getting
more
and
more
popular
and
we're
adding
more
and
more
great
functionality
to
it,
and
we
will
be
adding
the
mean
time
to
merge,
which
is
a
great
indicator
or
metric
for
showing
you
how
productive
your
team
is
and
how
quickly
they're
emerging
their
their
merge
requests.
A
So
we'll
be
adding
a
a
metric
within
merge
requests
at
the
project
level,
showing
you
mean
time
to
merge
within
a
particular
project
and
then
being
able
to
filter
by
different
labels
in
order
to
see
more
specifically,
your
team
or
people
or
or
things
that
you're
working
on
and
how,
in
the
meantime,
to
merge
for
that.