►
From YouTube: Digital Experience GitLab Analytics Walkthrough FY23-Q1
Description
Barker walks through the FY23-Q1GitLab analytics for the Digital Experience team and their projects:
- Onboarding for
- Slippers UI
- Buyer Experience
https://gitlab.com/gitlab-com/marketing/digital-experience
A
How's
it
going
barker
here
it
is,
may
10
2022
and
I'm
gonna
walk
through
some
of
the
analytics
of
our
digital
experience
projects
through
git
lab.
So
here's
our
group,
digital
experience
within
the
marketing
group
and
the
first
one
we're
going
to
look
at
is
this
onboarding
for
digital
experience,
and
this
is
where
we're
creating
issues
that
our
team
members
will
complete
for
onboarding.
A
We
go
over
to
analytics
and
we
can
go
into
the
issue
analytics.
We
get
some
really
cool
data
here
october
whoa
hired
a
bunch
of
people,
lots
of
onboarding
issues
created.
We
can
see
it
quieted
down
november
december,
started
adding
new
team
members
in
january
march
april
may
and
it
could
be
a
team
member
or
onboarding
issue
is
created
for
the
team
members
because
we
might
have
new
team
members
that
were
existing,
but
now
we're
on
boarding
them
to
new
systems.
A
A
We
had
lots
of
issues,
three
issues
created,
we
can
see
really
heated
up
there.
August
2021
looks
like
about
16
and
then
again
in
january
march
last
month
april,
and
these
are
all
issues
that
are
opened
within
the
slippers
design
system
project
and
we
can
see
the
age
status
if
there's
a
weight
given
merge
requests
will
give
us
a
little
bit
different
data,
so
that
was
when
merge
request
was
created
and
then
either
closed
or
merged.
A
A
Lines
of
code
changed
just
really
good
data
to
look
at
so
the
big
one
that
I
know
everyone's
wondering
about
that
buyer
experience
repository.
This
is
the
big
one.
So,
let's
take
a
look
at
the
issue
analytics
first,
so
may,
like
we
have
the
pro.
This
repository
is
just
starting
to
get
booted
up,
so
those
months
were
pretty
quiet,
but
we
can
see
it
really
started
heating
up
right
around
that
october
ipo
and
then
it
kind
of
stayed
hot
all
the
way
through
may.
A
A
We
can
see
it
right
there
in
the
code
and
the
data,
and
again
here
march,
I
mean
geez
who's,
that
181
merge
requests
holy
moly,
we
launched
a
whole
new
marketing
site
yeah,
that's
what
happens:
some
pretty
cool
stuff
and
some
other
cool
things.
We
can
take
a
look
at
if
we
go
back
to
this
group
level.
A
Come
over
here,
analytics
dev,
ops,
adoption
this
one's
kind
of
a
favorite
and
we
can
see
we're
doing
real
good
in
these
three
stages.
Dev
security
and
ops.
We're
four
out
of
four.
We
got
approvals.
We
got
code
owners,
we're
doing
issues
submitting,
mrs
and
in
the
op
stage,
we've
got
deploys
pipelines
and
runners
security
looks
like
we
gotta
work
on
that
one,
and
then
this
last
one
is
the
q1
value
stream.
A
Let's
see,
I
forgot
where
that
one
was
oh,
it's
right
here,
value
stream.
Well,
I'm
just
I
have
that
staged
over
here.
So
I'm
just
gonna
pull
that
into
the
screen,
this
one's
cool,
because
it
tells
you
the
lead
time,
new
issues
and
number
of
commits-
and
this
I
have
for
fiscal
year.
22
q1
dates,
and
I
really
liked
these
little
blurbs
up
here.
The
planned
stage
issue
first
associated
with
milestone,
or
the
issue
was
added
to
a
board
to
the
stop
time.
Issue
first
mentioned
in
a
commit
of
and
then
code
issue.
A
First
mess
mentioned
in
a
commit,
and
then
the
stop
merge
request
was
created
test
stage,
merge,
request
last
build
start
time,
merge,
request
last
build
finish
time
and
for
us
with
the
buyer,
experience
repository.
That
means
merge,
requests
and
we're.
Looking
at
the
review,
apps
we're
testing
we're
looking
at
the
pipeline
and
then
this
review.