►
From YouTube: Plan stage weekly - 2021-07-15
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
All
right
welcome
everyone
to
planned
stage
weekly
july
15
2021..
We
were
kind
of
discussing
what
the
points
on
our
agenda
were.
We
don't
really
know
what
a
1a
is
so
we'll
skip
that
1b
is
decision
to
use
work
items
table.
A
We
probably
don't
want
to
go
too
much
into
this,
because
I'm
not
100
sure
on
that
either.
If
that
means
the
decision
has
been
made
to
use
a
separate
table,
it
sounds
like
that's
where
we're
leaning,
but
I
also
don't
think
we're
going
to
get
a
full
decision
on
that
until
we
talk
to
the
database
team,
which
is
happening
tomorrow.
A
All
right,
skipping
on
down
to
our
numbering's.
Weird
eleven
hey
is
that
you
yeah.
C
C
C
A
A
good
question
we
can
probably
make
the
well.
We
can
definitely
make
the
argument
that,
yes,
we
own
it
just
anything
related
to
markdown
we
kind
of
own,
but
I
don't
know
if
we
are
the
ones
that
created
that
function.
C
A
Yeah
so
yeah
I
mean
we
should
we
should
go
with
it's
us
for
now
good.
But
is
your
question
you
want
to
know
if
anyone
has
any
like
expertise.
C
A
Don't
think
so
I
don't
think
there's
going
to
be
an
expert
on
on
it.
It
will
be
by
next
week
all
right.
So
there
we
go
dri
for
copy
sgfm
is
now
simon
or
john
or
john
yeah.
There
we
go.
E
The
last
thing
we
added
there
was
the
copy
tables
thing
stan
edit
it
and
yeah.
So
it's
like
plan
really
didn't
like
work
on
it.
Specifically,
it's
like
just
an
extra
thing
that
stan
saw
where
you
copy
tables
from
excel
or
google
sheets,
and
you
paste
it
and
it
shows
up
as
a
table
thing
yeah.
I
think
that's
the
last
one.
I
could
remember
that
where
we
worked
on
the
base
thing-
or
maybe
this
is
different
and
only
happens
on
code-
I
don't
know
if
it's
the
same
code
or
different,
but
I
don't
know.
E
E
It's
planned
mostly.
Actually,
if
you
look
at
the
like,
the
product
category
like
markdown,
is
put
under.
E
E
C
D
Yeah
just
wanted
to
click
quickly
touch
on
on
that
we
are
close
to
defaulting
on
the
feature
flag.
Now.
D
C
B
Can
I
so
that
needs
to
be
defaulted?
Okay,
so
that's
defaulted
on
now.
We
just
need
to
remove
the
feature
for
like
right,
simon
yeah,
and
it
needs
to
proceed
removing
the
feature
flag
for
graphical
boards.
Definitely
that's.
D
Fine,
so
we're
currently
defaulting
on
graphql
boards.
So
then
I
guess
we
can
remove
the
board
new
list
and
delete
the
deprecated
drop
down
to
create
correct
yeah.
E
C
D
And
then
we
can
remove
the
graphql
for
this
feature
flag.
So
yeah
do
you?
Do
you
have
capacity
to
remove
that
feature
flag,
simon.
D
Yeah
well,
you've
done
all
the
work
on
that
so
but
yeah
I
just
wanted
to
quickly
touch
base
on
that
because,
as
I'm
defaulting
on
the
graphql
board
feature
flag.
I've
real,
like
I've,
had
to
update
a
lot
of
things
in
the
docs,
specifically
the
screenshots,
about
creating
a
new
list,
and
I'm
like.
Oh
that's
another
feature
like
so.
We
need
to
think
about
that
as
well.
Yeah.
B
Thanks
flori
for
updating
all
the
screenshots
in
the
talk
it
just
takes.
A
D
Yeah,
I
think
so
there
were
also
a
few
other
things
on
the
issue.
Boards
dots
marcin's
been
helping
me
on
that
anyway.
So.
D
It's
fine
overall,
there
hasn't
like
beside
the
new
create
list
feature.
We
haven't
really
changed
anything
on
issue
boards.
We're
gonna
update
the
sidebar
soon,
but
that's
gonna
be
separate
anyway,
like
the
look
of
the
sidebar,
so
yeah,
I
think
the
create
list
is
the
major
change
really
with
that
feature.
The
rest
is
exactly
the
same
because
we
just
refactored
with
feature
parody
anyway,
so
we're
good.
C
D
A
I'm
sorry
say
that
again,
that's
bulk
edit.
C
C
D
A
A
Sorry,
I'm
lost
as
to
where
we
are
my
pay,
the
run
cuz
my
daughter
was
cooking,
something
and
she
she
lit
a
bag
on
fire
in
the
kitchen.
A
A
Okay,
did
we
get
through
all
the
points
on
the
graphql
boards
update,
then.
A
D
I
could
always
add
the
fact
that
I
need
to
update.
I
need
to
refactor
board
scope
to
be
able
to
remove
legacy
code,
but
it's
not
blocking
the
rolling
out
of
the
feature
itself.
So
yeah
like
it's
just
to
say
that
we're
on
track
to
roll
out
that
feature
flag.
But
we
need
to
fix
a
few
bits
and
pieces
here
and
there
as
we
do
and
then
we
can
remove
legacy
code,
which
is
exciting.
A
Anyone
have
anything
else:
gabe
left
a
nice
little
note
there
on
social
time.
If
y'all
get
a
chance
to
read
it,
learn
that
anything
else
anyone
has
to
discuss.
E
D
I'm
currently
fixing
that
and
it's
a
really
dumb
bug
it's
actually
covered
and
tested,
but
for
some
reason
the
milestone
id
is
stored
as
a
number
instead
of
a
string,
which
is
why
it's
not
being
processed
properly
and
that's
why
we
missed
it.
Basically,
I
just
need
to
add
a
dot
two
string
onto
it
and
it's
it's
working,
I'm
not
too
sure
why
it's
stored
as
a
number.
Maybe
I
should
look
at
that.
D
I
don't,
I
think
it's
just
the
field,
because
it's
a
legacy
field
of
milestone
in
board
scope,
yeah,
I'm
I'm!
I'm
gonna
fix
this
the
easy
way
and
because
I'm
also
separately
looking
at
refactoring
boardscope
anyway,
for
other
reasons,
I'll
look
into
this
and
trying
to
make
it
more
consistent
with
graphql
ids
but
separately,
because
it's
a
it's
probably
a
bigger
piece
of
work.
I
just
want
to
fix
this
bug
right
now,
but
yeah.
It's
it's
a
really
dumb
bug.
E
D
I'm
hoping
that,
once
the
legacy
code
on
board
is
completely
deleted.
We
can
unify
all
of
that
and
only
use
gids
everywhere.
It's
just
we're
still
using
a
bit
of
rest
endpoints
in
a
couple
places
and
the
way
things
are
stored
and
processed
still
using,
not
gids,
which
is
why
we
have
this
issue
right
now,
but
it's
something
that
we
can
iterate
on
later
I'll,
just
push
an
easy
fix
and
get
on
with
it.
D
Out
about
that
yesterday,
we
also
have
inconsistencies
even
in
graphql
mutations
like
not
all
of
them
necessarily
use
gids,
which
can
be
a
little
bit
confusing
when
we
build
mutations
for
working
items.
Maybe
we
need
to
make
it
consistent
and
only
use
gids
that'd
be
great,
just
throwing
it
out
there,
but
yeah.
That's
definitely
something
that's
been
causing
issues.
D
I
didn't
know
about
it
until
yesterday
and
you
just
because
we
we
do
have
a
lot
of
utils
defined
across
the
card
base
to
deal
to
do
like
global
milestone,
id
or
global
epic
id
and
stuff,
and
this
one
you
just
it's
one
function,
you
pass
it
the
type
and
the
id,
and
it
does
it
for
any
of
them
and
those
you
like,
there's
also
global
constants
defined
for
those
types.
D
A
Yeah
because
I
think,
there's
a
specific
util
somewhere
that
does
that
also
that
we
could
probably
remove
and
replace
with
the
global
one.