►
From YouTube: Product Analytics 15.10 frontend group kickoff
Description
In this call we discuss the frontend issues we have planned for 15.10
A
B
A
B
Yeah
find
out
I'm
relatively
flexible
mornings,
is
harder
for
me
honestly,
like
my
mornings,
because
I
often
have
to
take
the
kids
to
school
at
the
same
time
that
we'd
normally
be
having
one
of
these
meetings.
So
if
I
have
to
jump
back
on
to
work
in
the
evening
to
catch
him,
then
and
his
morning,
then
I
can
do
that
if
needed.
A
A
And
then
moving
on,
we
have
the
planning
issue
for
a
15
scene.
Please
have
a
look
but
I
feel
like
the
main
focus
we
really
just
need
to
discuss
here
is
completing
the
internal
preview.
That's
like
the
main
thing
that
we
want
to
keep
in
mind
for
the
front
ends
and
Rob.
You
had
a
item
to
discuss
there.
Yeah.
B
The
largest
item,
or
still
within
the
internal
preview,
is
also
marked,
as
the
second
point
in
the
planning
issue
a
bit
weird,
and
that
is
the
shared
listing
work
that
I'm
doing
currently,
which
is
apparently
has
two
Mrs
in
review.
One
Mr
I'm
working
on
and
two
more
MLS
on
top
of
that,
it's
about
four
thousand
lines
of
code
that
has
had
to
be
broken
down
into
some
manageable
chunk
of
work
could
have
been
multiple
issues
to
be
fair.
A
B
B
You
know
everyone
that
was
here.
That
is
why
there's
so
many
lines,
it's
not
because
it's
hard
I
mean
it
took
me
a
few
days
to
copy
it
all
over.
It's
just
a
real
pain
to
maneuver
that
much
work,
because
it
is
just
it's
just
lots
of
lines
and
files
that
need
to
be
copied
and
your
idea
of
actually
of
porting
over
of
migrating
the
components
and
then
referencing
them
in
the
old
Quantum
analytics.
Instead
was
a
really
good
idea
to
reduce
that
line
Camp
rather
than
directly
copying
them.
A
Yeah
I
still
feel
like
in
terms
of
just
surfacing
the
amount
of
work
that
this
is
like
in
the
amount
of
time
that
it
takes,
and
so
that
we
can
get
a
better
like
idea
of
like
tracking
the
amount
of
work
that
we
can
accomplish.
As
a
team,
I
feel
like
five
would
be
a
better
representation
than
three,
because.
C
A
It
is,
it
is
a
there's
like
two
schools
of
thought
on,
like
you
know,
wait
for
like
agile
purposes.
It's
like
yeah.
Is
it
complexity
or
like
effort
who
really
knows
I
feel
like
you
should
use
whatever
the
the
highest
or
like
the
most
impactful
is?
Is
it
like
super
complex?
Well,
then,
it's
going
to
take
you
a
lot
of
time.
Is
it
going
to
be
a
lot
of
effort?
A
B
At
obviously
we're
both
originally
from
compliance
so
looking
at
what
we
waited
previously
freeze,
classified
as
a
simple
change,
but
the
code
front
is
bigger.
Eg
lots
of
different
files
are
test
affected
requirements
are
clear,
whereas
five
is
a
more
complex
change.
Will
impact
multiple
areas
of
the
code
base.
There
may
be
some
refactoring
involved
requirements
are
understood,
but
you
feel
there
are
likely
to
do
some
gaps
along
the
way.
We
should
challenge
ourselves
to
break
decision
to
smaller
pieces.
A
B
Is
exactly
what
the
what
it
is?
However,
five?
We
should
challenge
ourselves
to
break
this
into
smaller
pieces.
This
is
definitely
one
of
those
that
could
have
been
broken
down
into
smaller
chunks,
just
because
of
the
line
changes
involved.
So
it's
sort
of
like
a
between
a
three
and
a
five.
Can
we
do
four.
A
B
B
A
B
A
A
So
this
means
that
we
should
just
keep
this
in
mind
whenever
we're
working
on
the
front
end
states
that,
whatever
we're
adding
this
Milestone,
the
next
Milestone
probably
needs
to
be
transported
to
the
back
end.
So
we
should
try
and
keep
that
work
as
small
as
possible
if,
if
at
all,
in
the
other
thing
that
I
listed
here
is
all
the
front
end
issues
as
of
noteds
down
below
that
this
seems
to
be
all
an
assigned.
A
So
it
would
be
great
if
I
think,
if
we
could,
during
this
call
quickly
like
get
an
idea
of
who's
going
to
work
on
what
and
also
pick
out
some
like
good
starter
issues
for
Alvin.
To
start
with
that,
you
know
it's
like
a
good
introduction
that
has
like
a
good
implementation
plan
and
isn't
too
vague,
or
you
know
it's
going
to
cause
too
many
headaches.
A
Yeah
I
feel
like
there's.
Definitely
a
theme
when
it
comes
to
these
shoes,
like
one
thing
that
I've
identified
that
I
would
potentially
like
to
work
on
is
like
the
column
charts,
but
I
also
feel
like
working
on
the
ux
polish,
in
conjunction
with
us
and
I.
Think
the
US
polish
still
needs
to
I,
don't
see
it
listed
here.
I
think
I
think
it's
only
to
automatically
slip
over
to
this
milestone.
A
C
A
B
A
B
A
B
Yeah,
it
needs
to
coincide
with
what
Tim
is
doing
with
the
visualization
design.
Their
books
I
mean
he
just
posted
in
the
channel,
the
workflow
for
using
the
project
and
group
level
selection
for
where
to
retrieve
the
dashboard
listing
so
I'm,
assuming
there
is
some
Concepts
there
that
he's
thinking
of
in
terms
of
adding
the
button
or
doing
that
whole
ad
to
flow.
A
C
A
B
What
I'm
going
to
do
is
valid
I,
don't
thinking
about
like
for
me
my
perspective
as
a
user
that
has
used
analysis
in
the
past.
I
would
compare
times
with
time.
Against
Time,
like
a
Time
range
with
another
time
range,
which
would
be
this
year
versus
the
previous
year
or
this
month
versus
last
month
or
whatever
it
might
be
so
I'd
say
having
that
range
of
one
year
makes
sense
to
me.
Yeah.
B
B
A
Still
yeah,
so
what
I'm
going
to
do
is
I'm
not
going
to
remove
it
I'm
going
to
change
it
from
a
default
to
a
configurable
value
yeah.
So
as
we
change
our
mind
or
figure
out
like
what
the
user
wants
or
what
our
constraints
are,
we
could
easily
change
that,
but
you
do
bring
up
some
good
points
that
I
think
we
can
discuss
like
during
our
group
call
tomorrow,
yeah
but
yeah.
B
Assignments
would
probably
make
sense,
not
that
one,
sorry,
the
that
one
should
probably
make
sense
to
be
me,
because
I
am
working
on
all
the
line
changes
so
from
a
response.
Perspective
of
Simplicity
I
already
know
what
needs
to
be
stripped
out
and
swapped
over
and
replaced
cool
I
have
the
context.
So
it
makes
sense
for
me
to
do
that,
even
though
it
is
something
that
could
possibly
be
given
to
Elwyn.
C
A
A
B
B
B
A
A
A
I
feel
like
this,
we
should
this
could
potentially
be
something
that
we
could
like
be
a
good
start
issue,
because
it
gives
a
good
introduction
into
what
this
is
and
testing
it.
But
I
feel
like
we
need
to
add
a
bit
more
description
to
the
implementation
plan,
for
what
it
exactly
is
that
we
want
tested
I.
Looking
at
this,
like
I,
don't
even
know
like
what
should
we
actually
test
on
the
query
designer,
because
there's
a
lot
visualization.
A
B
B
A
Like
this,
this
is
the
thing
where
the
name
of
this
issue
makes
me
really
unsure
about
what
we're
testing,
because,
if
we're
adding
feature
specs
for
the
entire
visualization
designer
I
think
this
should
have
a
weight
of
like
5.
or
be
multiple
issues,
because
the
visualization
designer
has
different
paths
to
it.
It's
testing
all
the
visualization
like
the
panel
contents
as
well,
because
you're
creating
the
visualization
that
is
also
Something,
That
We're
Not
testing.
A
Yet
on
the
dashboard,
so
I
wonder
if
we
shouldn't
do
the
same
for
the
visualization
designer
and
just
test
the
first
black
step
of
of
the
interaction
flow
and
basically
be
like.
Can
you
select
one
thing
and
then
see
the
first
like
thing
that
you
need
to
see
or
does
it?
You
know,
load
up,
fine
and
connect
your
Cube
for
like
the
first
query,
but.
B
B
C
B
Dimension
and
then
be
able
to
see
the
free
panels,
the
data
visualization
and
code
panels
and
check
that
the
items
are
shown
in
there.
You
don't
I'm,
not
I,
don't
particularly
want
to
test
the
visualization
itself
functions,
necessarily,
but
more
that
a
content
of
visualization
appears.
Does
that
make
sense.
A
B
Because
then
you're,
you
might
not
be
you're,
not
it.
It
covers
the
basics
and
then
we
can
go
in
and
be
more
descriptive.
Like
you
say,
the
current
dashboard
doesn't
test
each
visualization
either
make
sure
that
all
the
visualizations
render
exactly
how
I
would
expect
to
do,
because
I'd
expect
the
unit
test
to
handle
that
yeah.
A
Yeah
so
I
think
you're
you're
already
as
good
like
test.
The
first
flow
of
your
picking,
a
measurement,
picking
a
dimension
and
then
we're
just
confirming
that
those
three
panels
are
shown
yeah
and
that's
it
at
the
start,
like
the
visualization
isn't
going
to
be
shown,
because
you
also
need
to
pick
a
visualization
which
is
yet
another
interaction
but
I
feel
like
that's
by
default.
I
think
the
first
thing
that's
shown
is
the
data
panel
or
the
data
table.
So
it's
showing
you
the
results,
so
I
think
that's
actually
the
most
important.
C
B
A
B
A
B
B
Believe,
there's
a
comment
which
I
have
I
have
not
got
back
to
this.
It's
been
on
the
last
priority
which
Dennis
we've
had
our
one
to
once
and
I
have
apologized
and
said
it's
just
really
low
on
my
priority
list,
because
we
don't
technically
need
it
for
internal
preview,
it's
just
something
that
would
be
really
nice
to
have
so.
The
answer
to
this
is:
it
needs
to
be
fought
out
from
a
user
flow
perspective,
but
most
likely
scenario
is
there
will
be
a
configure.
A
B
B
That
is
a
separate
issue,
but
the
general
concept
of
that
page
is
where
this
is
gonna
probably
end
up
leading
to,
and
then
we
would
add
that
next
that
regeneration
percent
requires
back-end
work
as
well
as
front
end
and
all
with
stuff.
It
doesn't
exist
as
a
concept
yet,
but
that's
the
idea,
so
this
is
more
or
less
a
ux
conversation
not
a
front
end
one
just
yet.
Okay,.
B
A
B
A
A
A
B
B
B
Yeah,
it's
figuring
out
the
flow
of
the
Pro
itself
in
the
Pro
figure
out
the
flow
to
solve
the
problem.
The
problem
exists,
as
I
said
before.
Our
new
handbook
page
needs
to
list
out
the
our
workflow
again
like
it
did
on
compliance,
so
I
can
just
go
reference
it
every
time.
I
need
to
know
which
label
to
apply.
A
C
A
B
A
B
B
A
B
A
B
A
I'll
assign
it
to
myself
for
now,
since
after
your
reviews,
I
should
have
some
capacity
to
start
working
on
stuff
again.
So
let
me
let
me
first
take
more
of
a
look
also
at
this
and
see
if
I
can
also
add,
because
this
is
ready
for
development
without
a
actual
implementation
plan
or
any
real
context.
So
let
me
first
try
and
find
that
out
and
then,
if
I
won't
be
able
to
work
on
it,
I'll
just
unassign
myself.
A
A
C
B
A
B
I
mean
if
you
want
to
if
we
want
to
just
go
column,
chart
for
now,
because
that
each
other
wrapper
will
need
to
update
all
of
our
charts
to
match
that
so
I'm
happy
for
us
to
go
coven
chart
for
now,
and
then
you
and
then
have
a
separate
issue
to
con
to
update
all
of
our
charts
to
each
art
later
on
yeah.
We
want
to
do
that.