►
From YouTube: 2023-01-24 Product Analytics Sync
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
A
So
as
far
as
open
there's
just
a
brand
new
issue
that
I
added
in
ping
Max
on,
but
there's
one
that
I've
been
going
through.
All
the
issues
and
I
saw
this.
One
I've
been
seeing
reminders
of
it
as
I've
been
working
through
the
cube,
schemas
and
such
but
I
thought
it
might
be
a
something
to
look
at
this
Milestone.
Sorry
to
surprise
you
Max
on
this
one.
B
But
referring
specifically
go
ahead,
already
started
looking
at
that
this
morning,
I
just
hadn't
moved
it
into
workflow
and
Dev
yeah,
absolutely
I'll.
Look
at
that
yeah.
A
Last
week's
work
with
getting
Q
working
I
was
just
seeing
a
lot
of
references
to
Jitsu,
and
that
is
I
knew
we
had
an
issue
for
it,
but
I
just
only
found
it
today,
so
anyways
cool
well.
Looking
on
looking
at
issues
that
have
a
workflow
status,
we've
got
the
onboarding
API
to
retrieve
the
state
of
the
product,
analytics
stack
as
well
as
the
learnet
setup.
These
two
have
not
changed
since
last
week,
so
I
will
just
skip
over
them.
Someone
feel
free
to
interrupt
me
if
we'd
like
to
discuss
them.
A
Otherwise
we
can
look
at
the
add
dashboard
items
to
group
analytics
submenu,
which
is
blocked.
A
C
That
shouldn't
be
on
this
Milestone
at
all:
okay,
I've
just
removed
the
mask,
don't
it
yeah
that
was
my
bad.
It's
supposed
to
copy
metadata
and
forgot
to
remove
it.
No.
A
Worries
all
right
and
then
moving
on
ahead.
We
have
move
GPC
to
a
configurable
option,
still
a
JS
SDK
work
that
we
haven't
really
taken
on
yet,
but
we
should
definitely
address
that
for
the
customer
preview
and
then
I
have
one
of
many
infrastructure
issues
that
I
need
to
actually
get
set
up.
But
this
is
the
data
persistence
issue
with
the
Jitsu
ready
Services,
specifically,
why?
A
When
the
redis
pods
get
rebuilt,
they
don't
persist
the
data,
therefore,
the
configuration
of
the
destinations,
API
keys
and
so
on,
gets
lost,
which
is
not
good.
So
that's
something
I
will
be
starting
to
work
on
later
this
week.
We
also
have
the
renamed
widgets
to
panels
in
alignment
with
the
dashboard
working
group
not
assigned
currently,
but
the
working
group
has
effectively
decided
on
using
the
term
panels
to
contain
the
visualizations.
A
These
are
the
containers
within
a
dashboard,
and
so
we
need
to
rename
any
references
to
of
widgets
to
panels
to
make
sure
that
we're
all
in
alignment
there
moving
on
we've
got
in
Dev
Jan.
You
have
the
first
one
for
filters
for
dashboard,
State,
Range.
D
Yeah
I'm,
currently
working
on
that
it
may
be
a
bit
more
tricky
than
I,
initially
thought,
because
the
dimensions
for
each
different
measure
is
going
to
be
slightly
unique,
like
we
can't
use
ajitsu
time
dimension
on
a
sessions,
measurements
and,
for
example,
stuff
like
that
so
I'm
busy
figuring
that
out,
hopefully
I,
can
create
like
a
hash
that
maps
to
all
the
correct
time
dimensions.
A
Yeah
I
think
so
as
well.
I
think
we
just
need
to
be
consistent
with
our
naming
across
the
the
schemas
so
that
we
can
just
refer
to
one
for
dashboard
level
control,
but
we
can.
We
can
play
with
that
cool.
A
We've
got
the
internal
preview,
dashboard
issues
from
audience
and
behavior
I,
don't
think
the
chain
the
status
has
unchanged
has
changed
since
last
Meetup
in
that
there's
definitely
some
kind
of
Polish
and
follow-up
for
ux
issues
here
that
we
have
some
separate
issues.
So
it's
a
kind
of
a
side
note
or
referral
to
a
later
point
in
the
agenda,
I'm
looking
to
try
to
make
sure
all
the
issues
are
organized
and
up
to
date.
A
So
maybe
we
can
just
close
these
out
or
any
specific
follow-ups
with
regards
to
polisher
bugs
with
these
dashboards
we
can
address
in
separate
issues.
Moving
on
we've
got
adding
dashboard
items
to
the
projects
analytics.
Submenu
Rob
you've
got
this
one.
C
Yeah
started
cartoons
today
there
are
a
wider
discussions
in
the
further
agenda,
Point
around,
which
has
led
out
from
the
conversations
that
have
been
held
around
this
item,
but
this
actual
the
actual
code
for
this
should
be
fairly
straightforward.
So
I'm
hoping
laugh
that
out
for
review
by
tomorrow.
E
Yeah,
so
that's
a
tiny
one.
It
is
more
of
an
educational
experience
for
me,
so
I
plan
to
have
a
advantage
of
having
it
moved
to
review
today
and
maybe
continue
with
the
rest
of
the
of
the
random
kid
and
I
forgot
the
word,
but
yeah
I'm
going
to
continue
with
the
other.
The
other
related
issues.
A
All
right
and
then
we've
got
the
spike
for
determining
a
plan
for
product
analytics,
export,
Max
I
just
assigned
this
one
to
you
since
I
know,
you've
been
working
on
this
one
anything
you
would
like
to
hold
on
here.
Yeah.
B
That's
what
was
only
a
couple
of
potential
ways
we
could
do
this,
one
of
which
is
just
well
details
were
on
the
issue,
but
one
of
which
is
using
Cube
to
export,
basically
a
list
of
Dimensions
which
wouldn't
require
any
infrastructure
work.
Alternatively,
we
can
use
click
house
to
generate
a
CSV
file
and
upload
that
to
configured
object,
storage,
that's
quite
a
lot
more
work
and
will
require
some
infrastructure
work
as
well.
B
So
yeah
there's
options
there,
but
we'll
need
to
decide
how
far
down
that
rabbit
hole.
We
want
to
go
this
early
on.
A
Makes
sense
cool
moving
on
we've
got
in
review,
so
we've
got
the
add
button
to
go
back
to
tracking
view
from
dashboard
listing
and
the
legislating
the
product
on
the
display
designer
component
actually
get
these
two.
B
Yeah
this
is
done.
There
was
a
failing,
CI
job
yesterday,
so
the
maintaining
couldn't
merge
it.
That's
all
sorted,
so
it's
back
with
the
maintainer,
so
hopefully
it'll
get
merged.
Today,
the
maintainers
in
America,
so
yeah
today
or
tomorrow.
B
And
and
building
other
functionality
a
bit
further
right,
so
it
only
supports
page
views.
If
we
want
to
add
other
types,
then
we'll
have
to
add
support
for
that,
but
it's
a
relatively
simple
task
at
this
point.
A
It
yeah
so
I
think
we'll
start
touching
on
the
kind
of
funnels
Builder.
However,
however,
we
want
to
call
that
workflow
similar
to
the
core
designer
cool
awesome,
exciting
stuff.
We've
also
got
two
issues
and
verification.
A
Rob
you've
got
both
of
these
updating
the
product
analytics
documentation
with
all
the
feature
Flags
needed,
as
well
as
adding
the
stack
introduction
to
the
product
analytics
stocks.
Anything
you
want
to
call
out
here.
C
Yeah,
that
is
thanks
to
Lorena
and
Max,
for
diving
in
reviews
on
that
I
joined
these
up
into
one
of
our
waiting
for
it
to
hit
staging
just
so
I
can
verify
that
the
changes
actually
look.
How
I
expect
them
to
look,
they
should
do
and
then
I
can
close
these
off.
A
Awesome
and
then
I'm
just
going
to
quickly
check
our
bookmark,
which
is
stack
integration
with
staging
production.
A
So
we've
got
six
I
believe
new
issues
in
the
closed
column.
So
we
can
cover
these
first,
one
being
enabling
the
single
stat
widget
to
round
decimals
and
set
default
truncation.
Anything
we'd
like
to
call
out
here.
A
C
I
need
that
we're
now
a
little
bit
more
stable.
It's
a
little
techy
bug,
Improvement.
A
A
E
A
E
Know
we
have,
we
have
the
we
have
the
full
cycle
now
we
we
might
need
to
polish
a
few
things,
but
we
are
able
to
to
accomplish
the
onboarding
from
the
UI.
So
yeah
excited.
A
Just
some
time
for
us
to
change
how
we
get
there,
but
we
can
discuss
that
later
in
the
agenda
cool
and
then
the
last
issue
we've
got
is
for
their
encrypting
connection,
details
with
the
analytics
stack
integration
Max.
Anything
you'd
like
to
call
out.
B
Which
is
done
on
introduction
and
I
missed
a
not
so
Edge
Edge
case,
whereby,
if
you
haven't
ever
set
that
value,
then
you
could
no
longer
save
any
application
settings.
So
thank
you
to
Dennis
for
picking
that
up
and
getting
it
fixed,
but
yeah.
The
issue
is
closed
now
and
it
should
be
encrypted
in
the
database
by
default.
B
A
A
All
right,
then,
on
to
the
actual
agenda.
I
think
I
have
a
couple
of
points
here
so
yeah.
As
far
as
the
kind
of
social
budget
stuff
I
was
thinking
it's
a
little
late
for
a
Tuesday
dinner,
but
this
coming
Thursday,
perhaps
for
a
social
dinner
for
those
in
emea.
That
way,
we
can
then
I
think
basically
Sam
and
I
can
and
perhaps
Axel
as
well,
can
join
for
a
breakfast.
A
B
Please
don't
let
me
stop
you
yeah.
Unfortunately,
sorry,
no.
A
All
right
we'll
respond
on
the
agenda
for
everyone
else.
Otherwise,
I'll
send
out
the
invite
and
we
can
go
from
there
other
than
that
just
wanted
to,
as
as
you
as
a
group's
probably
seen
with
post
to
well
I,
don't
want
to
spell
attempts
point,
but
I
was
able
to
finally
get
the
dashboards
and
query
designer
API
calls
to
work
in
production.
A
They
are
not
working
in
staging
which
we'll
get
into
that.
But
basically
that
means
we
require
clusters
for
every
environment,
which
is
a
reasonable
expectation.
But
thanks
chairman
we'll
talk
to
work,
we've
officially,
you
know
got
a
end-to-end
solutionworking
in.com,
even
for
an
internal
preview.
That's
really
I
mean
it's
for
an
internal
preview,
but
it's
that
that
will
be
what
we
use
for
for
all
of
our
future
Milestones.
That's
a
huge
achievement
for
us.
F
C
And
thank
you
Tim
for
spearheading
the
career,
Designer
work
and
pretty
much
taking
that
on
entirely
on
his
own.
G
Thank
you,
yeah
back
to
you
all
great
work,
everyone.
This
is
really
awesome
to
see
this
now
really
going
from
an
event
seeing
it
straight
on
in
the
UI
is
a
huge
thing,
and
the
other
good
thing
I
think
for
the
for
this
group
here
is
also
that
anything
that
we
are
going
to
get
merged
and
moved
into
production
is
now
really
visible,
and
it's
not
anymore,
like
should
be
great,
should
should
be
working,
but
it's
something
that
every
change
everyone
here
does
should
be
also
visible
very
soon
than
in
production.
A
Yeah
and
they
kind
of
give
us
a
sneak
preview
until
what
that
looks
like
in
terms
of
visibility
and
Direction,
we
want
to
start
tracking
custom
events
in
the
internal
handbook,
so
we'll
obviously
be
able
to
enhance
the
behavior
dashboard
for
the
internal
handbook
itself.
We're
also
discussing
how
we
can
dog
food
and
add
analytics
to
our
own
features
within.com
and
get
really
dog
foodie
about
it,
and
that
also
ties
in
with
the
enabling
analytics
on.com
for
people
who
have
opted
in
specifically
so,
namely
this
group.
A
So
it's
going
to
get
pretty
exciting
there
and
it'll
it'll
be
nice
to
see
what
we
can
combining
that
with
protracting
how
our
features
are
being
used.
We
can
then
see
you
know
who's
using
or
yeah
how
we're
using
our
own
features,
so
that
combined
with
funnel
workflow
designer
will
be
pretty
exciting,
so
yeah
great
work,
rob
you
have
the
next
point.
C
Yeah
and
the
big
point
is
too
sorry:
I've
just
been
juggling
a
lot
of
different
discussions
and
conversations
that
and
I
felt
like
is
probably
about
time
that
I
brought
it
to
the
wider
group.
C
Those
who
aren't
following
those
issues,
especially
because
the
left
side
menu,
adding
that
is
sort
of
the
next
I
guess
quite
a
big
deal
for
us,
especially
from
a
customer
preview
perspective,
also
making
it
easier
to
access
our
content
for
the
internal
preview
with
people
who
want
to
check
out
what
we've
been
doing
a
lot
easier
and
it
makes
our
docs
much
simpler
to
read
if
we
could
just
say
go
to
this
dashboard
item
this
item.
C
So
a
little
update
on
where
we
are.
We
are
adding,
as
discussed
in
the
abort,
we're
adding
the
main
dashboards
menu
item
to
the
smartphone
right.
Now,
that's
going
to
point
to
the
product
analytics
dashboard
that
we've
already
created,
but
that
will
eventually-
and
it's
going
to
be
behind
a
feature
flag.
This
I
this
menu
item
and
it
will
eventually
point
to
a
more
shared
location,
other
left
side
menu
items
can
configuration
funnels
experiments
since
we've
done
a
UI
for
that.
C
Yet
we're
not
creating
those,
but
there
are
issues
created
to
set
those
up.
So
we're
not
going
to
forget
about
them
with
the
shared
in
listing.
There
is
a
few
conversations
happening
right
now
with
those
one
is
with
mate,
because
all
of
our
work
hasn't
had
any
ux
as
a
ux
designer
of
any
kind.
C
Take
a
look,
we're
just
sort
of
doing
our
best,
so
I
involved
mate
from
optimize
just
to
make
sure
that
what
we're
doing
works
for
them
for
optimizing
General
and
what
they're
doing
in
terms
of
their
designs
for
dashboards,
because
they're,
very
nice
and
so
far
mate
is
very
positive,
with
what
we've
done.
There's
a
general
idea
of
concept
of
tidying
up
the
design,
but
that
Nest
doesn't
necessarily
mean
that
it's
a
blocker
for
us
to
get
that
new
page
out
and
Tim.
G
Yeah,
no,
you
just
read
that
because
I
I
knew
from
foundations
that
they
have
now
this
pattern
of
the
project
like
listing.
So
that's
what
I
based
it
on
very
early.
If
mate
is
Happy,
let's,
let's
move
on,
let's
focus
on
the
next
things
forward.
We
can
polish
and
we
will
add,
most
probably
more
things
later
any
answer.
C
Yeah
I've
asked
mate
to
if
he
could
put
his
words
great
ability
at
design.
I'll
come
up.
We've
used
a
different
English
word
to
doing
that
polish.
Just
to
get
that
final
10
affection
and
we'll
see
what
he
says
on
that,
but
that
the
general
concept
is
not
a
blocker
now,
at
least
we
know
that
they
are
happy
with
the
general
idea.
So
we
can
proceed,
as
is
in
terms
of
the
other
point,
is
so
in
optimize.
C
They
have
a
con,
a
new
feature
that
they're
building
out
that's
currently
in
private
beta,
called
exec
dashboards.
I
didn't
have
time
to
find
the
link
before
this
meeting
I
apologize
feel
free
to
Google
or
if
anyone
can
find
the
link
Chuck
it
in
that
is
situated
on
forward
slash
analytics
for
slash
dashboards
on
the
group
level,
which
is
ideally
where
we
would
want
to
put
our
work
because
we
are
doing
a
list
of
analytics
dashboards.
So,
logically,
that
makes
sense.
It's
also
in
the
code
bases
using
the
same
naming.
C
So
there
was
a
conversation.
There
was
also
a
conversation
taking
in
that
more
General
dashboard
conversation
around
how
to
best
to
circumnavigate
that
complexity
to
keep
up
velocity
Tim's
idea
is
actually
a
pretty
damn
good
one,
just
randomly
thought
of
after
after
a
lot
of
conversation
and
being
involved
already,
I
don't
know
if
anyone
else
feel
free
to
jump
in
anyone
else.
C
That
wants
to
have
a
conversation
around
that
the
cons
it's
around,
trying
to
find
a
place,
a
location
if
that
is
consistent
for
everyone,
for
the
shared
location
for
the
dashboards.
Eventually,
what
we
plan
on
doing
is
having
the
shared
dashboard,
where
all
yaml,
based
and
gitlab
created
dashboards
can
live
in
one
location
for
users
to
easily
locate
these
Tim.
Your
do
you
want
to
vocalize
your
idea
just
to
show
her
how
amazing
it
is
yeah.
G
Yeah,
it's
simply
leaving
out
the
slash
analytics
and
going
for
dashboards
directly.
This
feels
a
little
bit
like
domain
name
grabbing
in
the
2000s
and
yeah
I
think
this
would
would
make
it
even
easier
because
to
be
honest,
I
I
strongly
believe
that
there
will
be
more
stash
boarding
stuff
very
soon.
So
plan
is
already
interested
in
building
burn
down
charts
for
dashboards
security.
Having
a
couple
of
things,
value
stream
analytics
has
multiple
Topics
in
their
designs
that
are
not
really
value
stream
analytics
but
are
corresponding
to
it.
G
So
I
I
can
see
yes
building
a
foundation
also.
The
suggestion
that
Sam
did
yesterday
is
that
we
add
a
product
category
to
the
non-product
item
so
that
we
are
basically
the
owner
of
of
dashboarding
and
and
are
happy
to
happily
to
lead
that
and
I
think
this
was
quite
good.
It
makes
makes
it
easier
so
yeah.
C
Yeah
I
agree,
I
think,
there's
probably
the
most
sane
solution
right
now,
I
slightly
I'm.
It
slightly
concerns
me
that
we
are
taking
over
that
forward,
slash
dashboards
URI
for
groups
and
projects
which
I
know
we
say
we're
going
to
own
the
dashboards,
but
that
might
cause
conflict
further
down.
The
line,
I,
don't
know,
should
be
relatively
straightforward,
I
guess
to
migrate
off,
but
we
do
need
somewhere.
C
F
Yeah
I
I,
really
like
the
Simplicity
of
the
the
slash
dashboards
to
your
point
about
a
user's
perspective.
I
think,
if
someone's
expecting
to
find
dashboards
dashboards
is
a
great
place
to
to
look
for
it,
and
since
we
are
very
early
days
on
this,
if
anyone
has
some
objections,
we
can
revisit
this
topic
if
we
do
need
to
move
it
at
some
point
in
the
future.
A
Yeah
Dennis,
I
I
agree
as
well.
I
think
the
solution
works,
at
least
in
the
short
term
I'm.
My
main,
my
main
point
is
that
I
still
think
optimize
still
needs
to
move
off
of
that
the
analytics
dashboards
one,
because
that's
that's
very
general
and
very
confusing
I
would
say
if
they're
going
to
stay
with
that,
but
that's
a
conversation
we
can
have
with
that
group.
A
So
that's
specifically
for
dashboards,
putting
a
slash
dashboards,
but
for
things
like
configuration
or
funnels
or
experimentation,
are
we
still
looking
to
put
that
behind
analytics,
slash
or
just
making
sure
like
this
is
just
for
the
dashboard
itself
right,
because
we're
not
going
to
put
like
dashboard
funnels
for
when
we
actually
have
like
the
funnel
workflow
designer
right.
Okay,.
C
In
terms
of
the
configuration
aspects,
those
are
analytics
specific,
so
I
would
say
that
it
goes
under
analytics
because
you're
configuring
potterton.
This
is
all
VSA
analysis
and
stuff.
You
don't
necessarily
I
assume
you
don't
need
configuration
to
make
to
create
a
dashboard,
necessarily
especially
if
it's
a
gitlab
owned.
One.
A
Cool
I
guess
I
can
follow
up
with
optimize
on
that.
C
Yeah
sorry
I,
don't
know
how
to
pronounce
his
name.
Fine.
Thank
you.
I
is
included
in
the
conversation,
I,
don't
think
they've
commented,
but
they
have
been
copied
into
the
conversation.
So
I'll
update
the
conversation
with
the
suggestions
using
dashboards
and
start
making
changes
from
there,
but
other
than
that.
C
I
feel
like
I,
really
appreciate
everyone
diving
in
on
and
listening
to
me
run
worth
saying
in
Tangent
all
this
there's
also
discussion
around
the
onboarding
flow,
as
noted
by
Dennis
earlier
we
have
a
flow
whereby
someone
goes
to
product
analytics
dashboards
and
it
goes
oh
you're
not
registered
yet
go.
C
Do
your
onboarding
stuff,
here's
the
flow
to
set
that
all
up
when
we
have
a
shared
listing,
that's
not
going
to
work
so
I
am
working
on
coming
up
with
some
call
to
action
Concepts
to
get
that
onto
the
dashboard
listing
to
make
it
as
easy
as
possible
for
users
to
start
using
our
work,
not
a
blocker
at
all.
For
any
of
this,
but
I
thought
I'd
point
it
out.
C
The
only
thing
that
does
block
the
customer
facing
preview
is
the
menu
item
and
getting
that
shed
listing.
But
it
sounds
like
we've
got
a
Way
Forward,
which
is
what
I
wanted
out
this
conversation.
So
I
appreciate
it.
If
anyone
has
any
questions
or
any
further
points,
either
say
so
now
or
let
me
know
in
group
chat.
A
Just
out
of
I
have
to
I
have
to
jump
into
another
one
soon,
but
for
the
the
call
to
action,
do
you
know
which
what
you'll
be
hooking
into?
Is
it
going
to
be
the
project
Global
pointer
or
like
I
guess
how
does
the
user
get
into
that
flow
with
the
shared
listing
or
how
do
you?
How
do
you
plan
or
how
do
you
think
of
it
right
now,
a.
C
Few
different
concepts,
the
most
prominent
one,
is
following
a
similar
vein
to
what
we
do
for
the
emerge
request:
approval
rules
where
we
say
licensing
compliance
set
up
here
and
it
looks
like
a
listing
item
on
the
approval
rules,
but
isn't
so
something
along
those
sort
of
lines
having
a
call
to
action.
Nursing
set
up
contact
analytics
link
off
to
that,
but
you
can
also
do
a
banner.
You
could
have
a
empty
State
on
the
configuration
page
there's
a
variety
of
different
options
that
I'm
going
to
take
a
look
at.
A
Sorry,
yeah
I'm
I'm,
not
so
much
focused
or
I,
wasn't
asking
about
how
the
presentation
of
it
was
like
what
what
are
we
are?
We
are
we
calling
the
API
to
see
if
there's
any
dashboard
set
up
currently
or
like
what
what's
going
to
prompt?
What's
going
to
be
the
trigger
state
for
those
those,
however,
it
manifests
off.
C
We're
gonna
have
to
follow
the
same
onboarding
prompt
that
we
do
now.
Okay
to
make
that
decision,
because
we're
going
to
need
to
be
able
to
list
the
our
dashboards
we're
going
to
have
to
hook
into
that
listing.
Somehow
aren't
we.
A
Yeah,
so
so
we'll
show,
however,
we
decide
to
The
Prompt
or
empty
state
or
whatever,
based
on
whether
or
not
we
get
dashboards
returned
or
not.
Yeah
amazing.
C
Whether
the
features
enabled
for
their
level
of
license
plus
whether
they
actually
have
any
dashboards
registered
in
yaml
configuration
and
stuff
got
it
cool.
Thank
you.
C
G
D
G
Post
adapted
in
the
CEO,
Channel
I
hope
everyone
has
seen
it
thanks
again,
also
for
all
your
work
there
in
that
Fred
I
recorded
as
an
updated
video
for
especially
that
one
or
five
minutes,
thanks
for
the
DSM
took
me
only
four
or
five
or
six
takes
I
forgot,
I
deleted
them
all,
and
this
is
also
showing
the
younger
support,
so
the
files
are
that
are
currently
safe
or
the
customer
dashboards
are
already
yaml
files,
so
that
works
and
a
couple
of
UI
updates.
G
The
other
big
thing
is
that
on
Friday,
the
project
point
for
groups
was
merged,
which
means
we
can
hand.
Now
this
setting
over
to
the
dashboard,
editor
and
say:
hey
here
is
a
point
to
a
project
where
you
can
save
this
stuff
and
basically
based
on
that,
we
can
build
already
into
the
dashboard
editor
the
loading
and
saving
functionality
of
customizable
dashboards
from
there,
on
which
it
would
be
a
big
step
forward,
then,
to
especially
enable
value
stream
analytics
Dennis.
You
had
a
point
there.
A
Yeah
I'll
just
briefly
touch
on
this
since
we're
almost
a
time
but
you'll
be
singing
things.
You'll
be
seeing
things
from
me
from
very
old
issues
that
everyone's
created
just
to
make
sure
that
they're
still
relevant.
Some
are
blocked,
but
now
are
unblocked
because
we've
shipped
dashboards
shipped
some
visualizations,
and
things
like
that.
So
keep
an
eye
out
for
that.
A
At
the
same
time,
Sam
and
I
will
be
working
to
create
more
issues
based
on
the
bugs
and
polish
that
we
previously
discussed,
but
as
well
as
what
needs
to
happen
for
the
customer
preview.
A
Since
we're
kind
of
you
know
we're
we're
nearing
the
end
of
what's
remaining
as
far
as
issues
in
the
internal
preview,
epic,
so
we're
kind
of
going
to
be
approaching
a
little
bit
more
ambiguity
and
lack
of
requirements,
so
we'll
be
working
to
clarify
that
and
then
just
as
a
read-only
point,
in
addition
to
Sam's
I've
kind
of
written
down
some
rough
findings
on
what
I've
put
together
or
what
I
found
during
my
time
connecting
cube
in
production.
So
take
a
look
at
that.
A
If
that
interests,
you
at
all
there's
a
call
to
action
there
for
those
interested,
but
take
a
look
other
than
that
we're
at
time.
Does
anyone
have
anything
else
they'd
like
to
call
out
before
we
end.
A
All
right:
well,
it's
good
to
see
everyone
have
a
great
rest
of
your
week
and
looking
forward
to
seeing
what
we
do
next,
thanks
folks,
bye.