►
From YouTube: Epic Boards MVC 3 Kickoff
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
I
was
one
level
up
two
levels
up
here
we
go
so
we're
going
to
be
discussing
mvc2,
which
is
looking
close.
Everything
is
in
1312,
that's
in
there,
as
well
as
kicking
off
mvc3
and
just
level
setting
to
see
how
we
feel
on
this
and
what's
in
the
epic,
if
we
might
be
missing
anything,
this
is
kind
of
the
last
chance
to
kind
of
look
at
it
from
a
high
level.
A
We
also
have
another
epic,
that
scott
added,
which
I've
added
here
to
the
top,
which
is
called
epic
parody
with
existing
boards,
and
I'm
wondering
too,
if
we
could
take
the
action
of
maybe
moving
some
of
these
into
mvc3
or
moving
this,
maybe
even
just
this
whole
top
level,
epic
into
mvc3,
so
we
don't
miss
it,
and
our
customers
also
see
that
it's
coming
in
that
third
bunch.
A
So
that's
high
level
kind
of
what
I
wanted
to
go
through,
and
the
first
item
I
had
was
so
just
first
talk
through
mvc2
and
then
mvc3,
so
I'm
just
going
to
open
it
back
up.
Are
there
any
questions,
concerns
things
we
should
talk
about
in
terms
of
these
last
two
open
issues
here.
B
Simon
simon
merged
in
the
not
filter
yesterday
and
then,
if
you
scroll
down
all
the
way
to
the
bottom,
all
the
way
to
the
bottom
john
said
something
yeah
so
john
said:
are
you
actively
working
on
this
we're
ready
to
move
part
to
into
development?
So
I
would
say
this.
This
issue
can
be
closed
because
then
this
issue
that
he
referenced
is
referencing
road
maps
for
il
for
filters
in
road
map
view.
A
B
B
So,
let's,
let's
close
this
out
and
okay.
C
Okay,
so
there's
one
down
and
the
one
that's
left
yanka
is
still
working
on
some
back
end
things
about
relative
positioning,
the
reorder
of
epic,
so
what's
left
so
the
drag
and
drop
between
lists
is
technically
done,
but
it
currently
does
not
support
the
order
of
the
epics
within
a
list.
C
So
I'm
keeping
an
eye
on
the
back
end
that
request
for
this
and
as
soon
as
it
gets
merged
I'll
just
need
to
like
add
a
few
parameters
to
the
drag-and-drop
mutation,
so
that
it
supports
relative
positioning
and
we'll
be
done
nice.
It
it
just
depends
on
when
the
back
end
gets
merged.
Basically,
and
then
yes
I'll
make
sure
the
front
end
supports
positioning
as
soon
as
that's
possible,
and
that's
this
one.
Yes,
so
this
this
is
the
back
end.
Merge
request
that
java
is.
C
Working
on
well,
it's
it's
an
if
there's
an
issue
and
a
merge
request,
yeah
and
then
there
will
be
a
little
bit
of
front
end
which
be
pretty
minor.
A
C
So
I
would
say
we
are
on
track,
but
janka
is
the
one
who
knows
all
the
technical
details
of
that,
I'm
hoping
we
can
get
it
in,
but
I
wouldn't
promise
anything
just
because
I
don't
know
what
that
entails.
On
the
back
end,.
A
Okay,
well,
it
looks
like
we're
on
track
if,
for
some
reason,
we
don't
make
the
final
for
this
one,
we'll
just
skip
that
release
post
and
we'll
just
go
out
with
the
14-0,
with
everything
in
in
the
main
feature.
So
the
only
I
mean
and
when
it
merges
our
customers
with
the
feature
flag,
could
still
keep
trying
it,
regardless
of
whether
it's
in
the
release
post,
so
we'll
still
be
well
ahead.
D
A
Okay,
so
that's
good,
so
it
looks
like
we'll
make
it
for
mvc2
and
then
for
mvc3.
A
B
B
So
there
was
something
to
donald,
and
I
think
I
want
to
say
this
is
like
your
call
there's
a
few
things
that
are
in
here
that
are
like
customer
feedback
from
one
of
those
issues
that
we're
doing
so,
for
example,
the
epic
count
and
epic
boards.
That's
like
theoretically,
parody
with
issue
boards.
B
So
you
could
call
it
like
a
bug,
but
I
don't
know
if
I
would
block
a
release
for
that
and
then
also
there's
a
few
little
edge
cases
that
I
was
speaking
with
donald
about,
and
I
think
we
should
80
20
like
are
these
features
actually
being
used
and
will
anyone
notice
it
and
should
that
clog
like?
Should
that
block
what
we're
doing-
and
I
think
yeah
so
like
the
second
one
down
in
epic
board,
search
when
clicking
on
board
card
labels
it
like?
B
A
Do
you
think
that
corner
case
to
me
that
one
seems
less
to
me
like
I
would
put
that
in,
but
we
could
call
this
one
feedback,
maybe
and
then
have
it
outside
of
the
main
mvc
nbc.
B
B
Yeah
so
because
we're
switching
to
graphql
for
this
new
implementation,
when
you
click
like
author
equals
and
then
it'll
always
put
your
like
the
current
user
yourself
on
top,
so
that's
not
happening
in
graphql,
it's
a
pretty
low
fix,
but
I'm
not
sure
who
would
notice.
A
A
B
End
graphql
query:
so
we
have
a
we
have
the
ticket
and
then
it's
mainly
a
backendish
issue,
but
in
has
been
really
clogged
up
with
other
work.
So
we
just
need
to
prioritize
it.
Okay,
but
it's
a
pretty
straightforward
thing.
D
A
E
A
Boop,
I
don't
know
where
the
heck
in
this
priority
list
it
should
go.
I
probably
just
messed
up
everyone's
billboard,
let's
put
it
down
here,
okay,
so
it's
in.
A
C
A
I
don't
think
so
either
I
don't
know
where
the
cut
line
is,
but
it
seems
like
we
should
have
some
work
in
fortino
still.
So
if
there
are
ones
you
you
all
want
to
preemptively
fort,
you
know
like
the
rollout
boards
feature.
I
could
move
that
right
now
and
some
of
these
others.
A
Too,
but
yeah
you
all,
can
help
move
these
as
well
like,
as
you
see
the
ones
that
you
think
should
go
towards
the
end
or
if
this
list
looks
out
of
order
to
you.
A
C
One
thing
the
get
ancestors
of
an
epic
using
graquel
is
technically
blocking
one,
that's
above,
which
is
allow
users
to
gain
more
context
about
an
epic
okay,
because
ancestors
are
yeah,
so
the
sidebar
is
almost
so
that
that
one,
the
yellow,
allow
users
to
gain
more
context
is
decipher.
C
That's
almost
finished
we're
just
missing
like
honestly
for
nbc.
It's
finished,
we're
just
missing
participants
and
ancestors,
which
is
actually
like
iteration.
I
don't
know
three,
I
think
of
sidebar,
but
I've
had
time
to
work
on
that
and
for
ancestors
we
need
the
back
end
on.
We
need
a
graphic,
curling
point
that
doesn't
exist.
C
It's
a
it's
a
blocker
for
finishing
the
sidebar,
but
at
the
same
time
I
don't
think
ancestors
are
necessarily
like
it's
not
a
hard
requirement
to
release
a
big
buzz.
I
would
say
there's
a
lot
of
stuff
in
that.
Actually
that
should
be
an
epic
like
the
issue
about
the
sidebar
should
be
an
epic
because
it's
actually
huge
now,
but
I
like,
given
the
information
that
alexis
has
provided
for
it.
I
would
say
it's
not
a
hard
requirement
for
mvc3.
C
And
the
other
one
is
the
create
a
new
epic
within
the
list,
which
is
another
big
one
that
hasn't
been
picked
up
yet
that
could
also
be
moved
to
14-0.
I
think
the
epic
with
the
three
issues
in
it.
C
Oh
this
whole
one
yeah
yeah
this
one,
because
it
requires
quite
a
bit
of
graphql
work
on
the
back
end
and
the
conversation
I
had
with
donald
about
this
was
that
it
was
less
likely
that
people
would
like
adding
a
bunch
of
epics
at
once
into
a
board
like
they
do
for
issues,
because
epics
are
much
bigger,
so
we
could
move
that
to
1400
comfortably.
C
I
feel
like
there
are
yeah,
it's
probably
other
things
that
are
more
urgent,
but
these.
These
are
last
bits
that
haven't
been
picked
up
and
I
don't
think
they're
terribly
urgent.
So.
A
A
A
E
B
E
A
There
was
very
few
trackers
for
boards
when
I
looked
in
the
database
like
I
couldn't
find
any
redis
trackers
or
anything,
so
I
don't
think
there's
even
a
really
robust
set
of
actions
for
issue
boards,
we're
kind
of
paving
new
territory
here.
So
things
like
like
adding
a
new
list,
there's
a
lot
of
actions.
A
A
A
E
I
have
a
pretty
what
feels
like
a
pretty
silly
question:
the
title
of
mvc3.
I
don't
understand
some
of
it.
Okay,
let's.
A
E
A
A
E
Is
that
one
word
I
don't
know
yeah,
that's
a
spelling
error,
nuances!
Looking
it
up
and
I
was
like
I'm
only
getting
offensive
dances.
E
A
A
E
E
I
just
I
just
it
was
one
of
those
things
where
I
kept
looking
at
it
and
then
thinking
I
have
to
ask
about
that
and
then
it
does
not
happen.
E
Feedback,
I
I
would
say
the
the
priority
of
the
aggregate
counts.
One
could
I
mean
all
it's
been
already
being
worked
on.
Maybe
it's
not
a
problem,
but
maybe
maybe
that
could
be
lower,
because
it
is
something
that
we
could
do
later.
Or
do
you
think
that
the
priority's
okay.
A
I
think
well,
if
I
had
to
pick
you're
right
yeah,
I
would
put
that
to
the
bottom.
However,
that
takes
some
30
days
for
them
to
ramp
up
for
them
to
get
into
the
system.
So
like
the
fact,
those
are
already
in
we're
pretty
much
done
like
what
would
be
necessary
to
have
tracking
on
day
one
on
when
the
14-0
release
goes
out
with
just
these.
A
E
E
That's
a
good
question:
do
we
have
any
I
mean
if
the
front
end's
not
after
it,
then
is
that
part
of.
E
E
C
E
C
E
C
C
Grabbing
weight
from
children's
issues,
and
so
on.
I
I
think
what
the
conversation
was,
that
we
could
release
a
big
balls
without
this
given
complexity
interest,
it
would
be
a
future
iteration
for
airports.
D
B
Is
that
is
that
calculation
pretty
expensive.
E
It's
it's
beefy
yeah,
but
it's
entirely
possible
that
we
could
use
a
bat,
a
batch
sort
of
thing.
So
at
the
moment
you,
you
feed
the
lazy,
epic
aggregator,
you
feed
it
an
epic
id
and
then
it
has
a
a
big,
huge
query.
That
does
the
thing
that
you
want
it
to
do
and
it
can
also
do
count
at
the
same
time.
If
you
ask
it
to
do
that,
so
it's
designed
so
that
you
can
pile
things
on.
E
If
you
need
to
now,
we
might
be
able
to
get
away
with
doing
something
I
mean
in
graphql.
You
can
do
some
things
some
of
these
batching
things
quite
nicely,
but
because
it's
kind
of
an
aggregate
query
rather
than
just
off
one
thing,
it's
entirely
possible
that
it
will
not
be
easy
to
do.
D
B
We
can
take
this
offline,
but,
like
maybe
something
we
would
want
to
consider
is
like
on
visual,
like
on
the
user
visually
seeing
the
epic.
Then
we
just
go,
get
the
weight
so
that
we're
not
doing
a
bunch
of
extra
work
that
we
don't
need
to.
But
that's
a
technical
implementation
thing
that
we
can
discuss
offline.
A
A
A
So
all
of
the
work
that
we
all
did-
or
you
all
did
for
getting
all
the
trackers
in
are
in
the
system.
This
is
I've,
pulled
out
assistance
and
pulled
a
csv,
so
good
job,
everyone,
they're
all
all
lit
up
and
I'm
slowly
going
to
go
through
and
in
column
c,
I'm
adding
a
link
to
getting
the
actual
data
on
a
chart.
A
E
A
April,
I'm
trying
to
get
to
the
bottom
of
why
we
had
such
a
big
leap.
This
is
our
older
counter,
but
these
are
epics
created.
So
it's
a
fairly
massive
jump
in
april
it
may
be
due
to
a
bigger
customer
onboarding
which
I'm
trying
to
get
to
the
bottom
of
as
well,
but
yeah,
it's
pretty
cool.
It's
like
7
500,
new
epics,
which
is
almost
double
our
old
goal
of
3
900,
which
is
really
cool
so
back
to
this.
A
E
E
You
know
we
came
up
with
one
and
then,
as
we
kind
of
did
without
okay,
we
have
to
standardize
some
things
and
it
wasn't
until
about.
I
don't
know
a
third
of
the
way
through
that
we
were
like.
Oh
hang
on.
We
need
to
have
users
in
the
title,
so
yeah
product
intelligence
is
still
figuring
this
out
as
well.
A
E
A
Yeah
and
I
may
be
able
to
also
change
them,
because
these
are
kind
of
like
the
definitions
of
these
kind
of
live
with
me,
so
I
might
be
able
to
put
underscore
users
into
these
ones
so
that
they're
consistent.
A
The
other
thing
that
I
was
just
talking
to
gabe
about
before
this
is
that
I
think
what
we'll
do,
because
right
now
this
is
aggregating
users,
so
it
would
be.
If
we
look
at
like
the
title
one
or
this
one
like
number
of
users
who
edited
a
description
monthly,
we
don't
have
anywhere
where
we're
actually
tracking
how
many
descriptions
were
edited.
So
I
think
I'm
going
to
add
one
where
it's
like,
instead
of
users
like
right
in
here,
it
would
go
to
count.
A
I
don't
know
if
you
all
can
see
what
I'm
doing
if
it's
too
small
and
I
wouldn't
obviously
be
in
capitals,
but
then
for
each
mechanism.
We
would
have
the
total
users
making
the
change
as
well
as
like
how
many
descriptions
actually
got
updated.
A
A
Being
put
to
use
it's
great
yeah,
we're
actually
building
out
a
big
table
with
gabe,
so
I'll
just
show
quickly.
I
can
link
this
as
well.
He
this
is
all
issues
gmail,
so
his
total
users
here
interacting
with
issues,
is
around
310
000,
and
so
we
are
that's
the
aggregate
of
all
of
these
issues
so
down
below.
I
just
started
adding
ours,
so
we
have
we're.
Gonna
have
the
same
format.
A
E
Right
yeah,
thank
you
for
thank
you
for
yeah
that
everything
and
alexis
you're
so
happy.
A
All
right:
well,
that
concludes
mvc
2
and
3
kickoff,
hopefully
the
last
one
for
epic
boards
and
then
we'll
kick
off
boards
again
when
we
have
new
issue
types
and
you
get
to
build
it
a
third
time.