►
From YouTube: GitLab 13.3 Kickoff - Manage:Analytics and Manage:Import
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
friends,
I'm
jeremy
watson,
I'm
a
group
product
manager
here
at
gill,
lab
I'm
here
today
to
talk
a
little
bit
about.
What's
ahead
for
the
manage
stage
in
13.3,
which
is
releasing
august
22nd,
20
2020.,
I'm
here
sharing
my
screen
and
I
wanted
to
point
out
that
we'll
only
be
talking
about
analytics
and
import
today.
Melissa
and
matt
on
access
and
compliance
respectively
have
already
recorded
some
great
videos
talking
about
what's
ahead
for
those
groups
in
13.3.
A
So
please
check
those
videos
out
if
you
haven't
so
talking
a
little
bit
about
what's
ahead
for
analytics.
So
here
at
gitlab,
we
track
a
number
of
kpis
that
are
available
in
our
public
handbook,
and
you
can
see
one
of
those
here.
We
actually
use
these
charts
and
track
them
and
create
them
in
sysense,
which
is
a
third
party
product,
and
you
can
see
we
embed
those
dashboards
here.
A
One
of
the
goals
that
we'd
like
to
be
able
to
do
is
be
able
to
effectively
measure
throughput
in
our
products.
So
we
can
start
dog
fooding
some
of
these
analytics
directly
in
gitlab,
and
that
is
kind
of
what
we're
excited
to
kind
of
center.
Our
efforts
in
13.3
around
around
this
concept
and
this
new
feature
that
we're
calling
merge,
request
analytics
and
really.
This
is
all
about
how
we
measure
throughput.
So
throughput
is
really
this
measure
of
productivity
commonly
used
across
many
different
companies
and
and
teams
around.
A
That
you'd
like
to
kind
of
understand
a
little
bit
better.
So
that's
really
the
kind
of
the
the
the
goal
for
for
analytics
in
13.3.
So
we'll
start
with
by
prioritizing
the
chart
that
I
mentioned,
which
we'll
fix
originally
to
a
12
month
period.
So
you
can
see
the
number
of
merge,
requests,
closed
and
merged
kind
of
over
time.
A
We'll
also
make
sure
that
we
add
a
filter
bar
which
allows
some
powerful
filtering
capabilities
by
projects
assignees
and
we're
investigating
also
adding
branches
as
well,
so
that
you
won't
just
be
able
to
default
to
master
only
but
you'll
actually
be
able
to
see
other
branches
as
well.
So
powerful
filtering
is
also
something
that
we
see
as
really
important
for
this
feature
and
we'll
also
be
able
to
show
like
deep
a
data
table.
So
you
can
really
understand
interval
individual
merge
requests
how
much
time
they
took
to
merge
what
milestone
they
were
in.
A
I
know
a
ton
of
metadata
on
exactly
what
happened
with
that
merge
request.
So
if
a
merger
quest
took
a
particularly
long
time
to
merge,
you'll
be
able
to
sort
by
it
see
how
long
that
took
and
identify
kind
of
some
of
the
reasons
that
why
that
may
have
happened,
so
your
team
can
kind
of
improve
in
future
milestones
a
stretch
goal
that
we'd,
like
to
kind
of
like
consider,
also
is
actually
being
able
to
directly
embed
some
of
these
chart.
Throughput
charts
in
the
handbook.
A
You
know
our
goal
here
at
gillab
is
to
focus
really
heavily
on
dog
fooding
and,
going
back
to
this
page,
we
would
love
to
be
able
to
take
a
chart,
that's
actually
in
our
product
and
slowly
start
to
replace
some
of
the
charts
that
we're
currently
leaning
on
other
tools
for-
and
I
think
that
a
stretch
goal
that
we'll
like
we'll
set
for
ourselves,
although
we
may
not
get
to
in
13.3,
it's
really
accomplishing
that
by
replacing
at
least
our
throughput
chart
with
a
chart
that
is
directly
tied
to
to
real-life
data
in
our
product.
A
So
that's
really
what
I'm
really
excited
about
for
the
analytics
group
and
I'll
turn
my
attention
kind
of
over
to
the
import
side
as
well
and
on
import.
I
think
that,
right
now
the
focus
is
going
to
be
around
removing
legacy
code
from
our
github
importer
from
a
strategic
perspective,
github
tends
to
be
a
competitor
that
we
tend
to
focus
on.
We
want
to
make
sure
that
we
have
a
great
scalable
experience
when
you're
importing
and
exporting
projects
from
github,
and
so
while
there's
not
going
to
be
any
major
user
facing
changes
for
this.
A
The
team's
going
to
be
hard
at
work,
replacing
any
occurrences
of
this
legacy
code
in
our
code
base.
This
is
going
to
unblock
some
other
great
improvements
that
were
that
we're
currently
planning
on
and,
more
importantly,
it's
going
to
ensure
that
that
our
github
importer
performs
well
especially
at
scale,
especially
for
customers
and
users
that
are
importing
hundreds,
if
not
thousands,
of
projects
over
for
github
from
over
from
github.
We
want
to
make
sure
that
that
experience
is
great,
performant
and
and
failure
tolerant.
A
The
the
issues
that
I'm
excited
about
this
I'm
blocking
are
going
to
be
a
better
experience
in
terms
of
how
we
present
projects,
especially
when
you're
trying
to
do
a
bulk
import
for
for
a
large
number
of
repositories
and
we're
also
going
to
introduce
pagination
in
the
future
in
a
future
iteration
you're,
probably
most
likely
using
infinite
scroll.
So,
while
you
know
removing
legacy
code
from
from
our
importer
is
something
that
I'm
personally
excited
about.
A
We
may
not
see
any
user
facing
changes
until
future
iterations,
although
the
team
is
working
hard
to
get
to
get
there.
So
that's
all!
That's!
That's
ahead
for
analytics
and
import
in
13.3
really
excited
about
this
release.
As
always,
please
check
out
accessing
appliances,
videos
because
we
do
have
a
lot
of
great
great
great
improvements
planned
for
13.3.