►
From YouTube: Manage:Analytics Weekly 2020-06-30
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
Yeah,
that's
I'm
on
throne,
again
it's
like
working
from
booth,
so
yeah
welcome
everyone
to
a
new
analytics
weekly
call.
We
had
a
couple
of
XY
eyes
today,
so
please
make
sure
to
read
through
them
and
then
the
next
agenda
item
is
already
it's
old
it
for
me
to
walk
the
board.
So
let
me
share
my
screen.
Real
quick.
A
On
the
P
one
column,
we
only
have
the
carry
over
from
the
last
milestone,
which
is
about
adding
filter
results.
Control
on
the
group,
value
stream
analytics
page
so
is
a
kill
posted
an
update
earlier
today,
where
he
mentioned
that
this
for
the
last
Amara
got
already
merged.
It's
not
deployed
on
staging
yet,
but
we're
expecting
this
to
to
happen
in
the
next
one
or
two
days.
A
So
once
this
is
deployed,
we
should
be
able
to
test
that
I
think
there's
two
more
outstanding
issues
that
he's
working
on
at
the
moment,
but
they
shouldn't
really
Glock
us
from
from
testing
this.
So
once
this
is
deployed,
we
can
test
this.
It's
behind
a
fleet
feature
flag
and
I.
Think
Isaiah
has
already
enabled
the
feature
flag
on
staging.
So
on
the
p2
column,
we
have
the
the
group
activity
M
our
chart
with
similar
serious,
so
maybe
Brendan.
Maybe
you
can
give
us
an
update.
C
B
B
A
Corp
sounds
great
yeah.
I
guess
we
can.
We
can
add
the
d
blocked
label
for
now,
since
we
have
a
dependency
on
the
skeleton,
so
that
makes
sense
just
to
have
the
context
what
we
are
waiting
for,
the
next
one-
I
guess
the
next
one.
Maybe
we
should
also
add
a
block
label
to
the
issue
chart
because
that
actually
depends
on
post
skeleton
and
the
a
march
art.
If
I,
if
I
remember
correctly
so,
that's
the
that's
actually
kind
of
the
light.
A
B
A
Awesome
yeah
I
think
that's.
That
was
the
intention
here.
So
ideally,
there's
not
too
much
front-end
effort
required.
Once
we
have
the
basic
implementation
for
the
skeleton
and
mr
chart
so
yeah
I
guess
we.
We
should
definitely
split
that
into
into
a
separate
back-end
issue,
because
I
believe
there's
more
second
work
involved
in
order
to
get
this
working
so.
D
Intent
behind
the
issues
chart,
a
single
series
is
that
there
should
be
nothing
to
do
other
than
creating
the
yml
file
and
then
linking
it.
So
you
know
creating
that
yml
file
I'm,
not
sure
that
that
would
I
mean
it
could
be
done
by
somebody
on
the
back
end,
but
the
intent
is
that
it
should
be
able
to
be
done
by
somebody
like
me.
Even
so,.
A
Right
so
maybe
maybe
we
just
leave
it
for
now
and
wait
until
we're
done
with
the
first
MVC
4
for
the
NR
chart,
and
then
we
can
catch
up
on
that
later
and
see
if
it's
really
that
easy
which
we
are
hoping
for.
But
then
we
will
see
if
the
embassy
we
were
we're
doing
a
great
job
and
embassy
or
not
cool.
C
A
E
F
I
was
actually
checking
on
that
yesterday
and
having
a
little
bit
of
trouble
finding
it
let's
go
ahead
and
close
it
and
all
all
handle
verification
as
soon
as
I
figure
out
how
to
get
a
hold
of
the
data.
So,
basically
in
the
usage
ping
data
that
I
have
access
to
this,
you
know
staged
specific
stuff
is
not
showing
up
so
I'm
working
on
figuring.
That.
A
A
A
D
A
D
A
Okay,
let's,
let's
coordinate
afterwards
cool.
A
D
Don't
have
new
content
I
wanted
to
go
over
today.
I
know
Nick
had
some
items
last
week
that
we
never
got
to
if
he
wanted
to
have
the
time
I'm
happy
to
turn
it
over
to
him.
The
other
thing
I
did
want
to
cover.
Was
you
know
how
we're
doing?
On
the
estimation
we
we
had
made
a
plan
in
the
planning
issue
to
try
to
estimate
some
issues
each
week,
it'd
be
nice
to
see
how
we're
doing
with
that.
F
Right
so
there
were
a
couple
of
pings
towards
the
end
of
last
week
and
then
a
couple
more
pings
yesterday
on
on
separate
issues,
so
I
think
we're
just
we're
waiting
to
hear
back
on
some
of
that
or
maybe
not
because
I
just
started
my
day,
and
maybe
some
people
have
already
responded.
So
I
need
to
get
caught
up
on
that,
but
yeah
we
have.
We
have
a
couple
of
things
outstanding,
so
I
guess
engineers
on
the
call
please
keep
an
eye
out
for
for
pings.
In
terms
of
estimation,.
A
G
Working
on
the
dark,
UI
color
palette
at
the
moment,
because
transparencies
not
not
too
not
too
accessible
or
usable
in
the
slightest
when
when
we've
got
the
dark,
UI
applied.
So
this
is
sort
of
where
we're
converging
at
home
from
stuff
like
this,
which
also
has
implications
on
on
the
colors
and
stuff
that
we
use
in
the
light
UI.
So
that's
something.
A
G
This
basically
highlights
how
the
relationship
between
the
dashboard
and
the
report-
we
can
have
a
report
as
a
page,
but
we
could
also
have
a
report
as
something
that
we
potentially
bring
up
within
a
lightbox,
meaning
that
as
you
as
you're
in
the
page,
it
means
that
you
can
sort
of
bring
that
stuff
up
really
quickly
in
context.
So
you
can
drill
into
the
data
I.
G
G
F
G
A
A
D
I'm
used
to
looking
at
the
data
from
snow
plow
and
also
that
gets
synced
over
from
the
database
tables,
but
the
usage
pink
data
I
haven't
figured
out
that
I
get
to
yet
and
it's
it's
not
refreshed
at
the
same
pace
as
that
other
data.
So
you
know
we're
somewhat
dependent
on
the
timing
of
that
synchronization
job.
F
D
D
You
know
that
may
not
be
achievable,
but
that's,
let's
see
what
we
can
do
and
then
planning
is
July
9
and
my
hope
is
that,
this
time
round
by
our
planning
meeting
in
July,
9
we've
gotten
through
estimates
on
everything,
and
we
can
really
have
our
final
planning,
locked
and
loaded
July
9
and
not
have
other
things
show
up.
Afterward
that'll
give
us
our
best
chance
of
starting
that
work
on
time.
D
A
F
E
F
Like
compliance
group,
for
example,
has
decided
to
start
using
it
for
their
own.
You
know
their
own
North,
Star
metrics.
You
know
just
because
telemetry
hasn't
built
their
solution
yet,
and
so
many
different
groups
have
North
Star
metrics
that
depend
on
pageviews
and,
and
you
know,
actual
user
usage
of
features.
So
yeah
compliance
group
is
going
to
be
using
what
you
built.