►
From YouTube: Plan group weekly meeting
Description
Plan group weekly meeting for 2019-04-24.
A
Okay,
cool
we're
recording
now
so
this
is
the
new
meeting
invite
for
the
plan
weekly
meeting.
It's
always
running
the
previous
one,
but
now
is
left
I'm
gonna
set
it
up.
Donald.
Thank
you.
So
if
anybody
else
wants
to
be
an
alternative
host,
which
will
also
let
you
set
up
recording,
please
give
me
your
email
address,
because
that's
what
a
zoom
wants
and
I
can
add,
you
I'm
gonna,
add
Donald's,
because
he
had
it
is
email
address,
but
the
more
people
the
better
really
like
it
doesn't
matter.
A
If
everybody
is
a
potential
host
to
be
honest
and
the
way
you
have
to
do
this
it
turns
out
is
it
looks
like
you
have
to
join
from
the
zoom
client
I,
don't
really
get
how
like
zoom
signing
in
works,
but
it
looks
like
if
I
join
like
just
from
a
link.
It
doesn't
recognize
that
I'm
signed
in
and
it
won't.
Let
me
record
where
it's
now:
it
will.
A
A
The
reason
for
that
is
that
there's
some
important
stuff
or
an
important
customer
that
that
team
needs
to
look
at
and
Camille
who
is
on
that
team
at
the
moment,
is
heading
out
after
this
week,
so
yams
using
this
week
to
shadow
Camille
and
get
some
knowledge
transferred
over
there.
I
was
going
to
look
at
what's
in
12.0.
A
I
guess
Annabel
and
Donald's,
like
that's
kind
of
it,
depends
on
how
much
you
can
well
me
as
well
sorry
kind
of
depends
on
how
much
you
folks
want
to
do
it
like
the
main
reason
I
was
doing.
This
was
for
Erick's
benefit
and
I.
Guess,
if
he's
watching
the
recording,
we
can
still
talk
through
what
features
there
are
in
this
release
at
least
and
sort
of
see,
if
there's
anything
else
that
we
think
we
should
be
considering.
A
A
A
The
number
of
people
in
the
team
correctly,
but
I
think
it's
about
50/50
as
well.
Yeah
yeah,
so
yeah
both
front
in
the
back
end
are
probably
about
75%
of
capacity.
Based
on
that,
because
you
know,
we've
got
50%
of
the
people
who
are
going
to
be
out
for
50%
of
the
time
so
yeah
in
looking
at
what's
already
in
there.
So
this
is
they
just
literally
what's
in
there,
I
haven't
like
been
going
through
this
and
doing
any
grooming.
I
don't
know
if
anybody
else
has
I'm
just
sort
of
looking
at.
A
What's
already
there
I'm
going
to
share
my
screen,
so
we've
got
these
features
and
the
top
one
here
about
elasticsearch
is
kind
of
a
shared
initiative
between
create
and
plan
until
Mario's
done
with
the
NBC
forget,
live
comm
system
know
when
adding
and
removing
sub
ethics
I
think
got
bumped
from
an
earlier
release.
Maybe
but
I
don't
see
a
problem
getting
that
done
here.
A
A
So
many,
whether
an
issue
or
Emma's
catalyst
is
complete
player
API
is
100%.
Back-End
obviously
create
issue
from
epic
is
also
going
to
be
interesting
and
warned
before
applying
issue
template
so
I
guess
there
is
three
cloning
issue
with
quick
action,
create
issue
from
epic
and
warned
before
applying
issue
templates
might
be
worth
looking
at
I'll,
probably
do
them
in
reverse
order,
because
I'm
guessing
that
some,
the
last
two
will
be
smaller.
A
A
Is
it
just
completely
replaces
what
you've
written
in
the
description
with
the
template,
and
we
think
that
there
should
be
a
warning
before
you
do
that
if
you
have
changed
anything
like
if
you
typed
in
that
box,
essentially,
so,
if
you
you
just
switch
from
one
template
to
another,
that
should
be
fine,
but
if
you
switch,
you
know,
if
you
add
a
template,
then
start
typing
then
realize
you
want
to
switch
templates.
It
should
warn
you
Anabelle
I,
don't
know.
If
you've
had
a
chance
to
look
at
this
one,
it's
got
quite
a
long
threads.
B
A
B
A
And
then
Donald
I
think
between
this
is
a
front-end
only
issue,
because
the
front-end
should
have
all
the
information
here
needed
to,
like
you
know,
decide
whether
that
warnings
applied
I,
don't
think
the
backend
would
even
have
the
information
so
that
make
sense
to
you
and
it's
been
weighted
as
three,
but
that
was
from
like
six
months
ago.
So
if
you
want
to
change
the
weight
on
that,
please
go
in
and
do
that
cool.
A
It's
also
got
the
internal
customer
label,
so
we
use
that
label
for
people
yet
lab
who
have
a
particular
interest
in
certain
issues
because
we
use
get
ourselves.
This
also.
Has
the
internal
customer
label
create
issue
from
epoch,
Anabelle
gonna?
Ask
you
again,
have
you
already?
Oh,
it
looks
like
alexis
was
commenting
here
so.
B
A
B
B
A
This
is
actually
a
current
design.
The
description
just
says:
it's
how
it
looks
in
boards.
It's
not
saying
we
should
do
this.
It's
just
saying
this
is
what
boards
look
like
and
then
this
is
what
it
looks
like
when
you
create
in
your
epics,
so
I
think
yeah.
If
you
could
update
that
with
the
the
epic
from
epic
design,
because
I
guess
it'll
probably
work
very
similarly
to
that,
that
would
be
great
cool
and
then
what's
this
label
those
at
the
moment.
A
So
this
is
just
labeled
as
front-end
at
the
moment,
I
think
any
back-end
work
will
be
pretty
minimal
Donald.
So
again,
let
me
know
if
you
think
that's
wrong
or
let
me
know
on
the
issue
you
don't
have
to
like
answer
right
now:
cool
and
then
the
final
one
here
is
clone
clone
issue
with
quick
action.
So
we
have
a
quick
action
to
you
know
we
have
quick
action,
it's
like
move
issues
or
mark
initializer
duplicates.
A
What
this
is
saying
is
that
the
quick
action
would
be
called
clone
and
it
would
copy
the
title
description
labels
from
the
original
issue.
It
doesn't
copy
any
comments
and
it
doesn't
copy
the
author,
the
author,
as
the
person
who
does
the
clone,
so
quick
actions
are
typically
100%,
back-end
I
would
say:
I,
don't
know
what
right
okay,
so
this
one
is
another
one
with
the
internal
customer
labels.
So
that's
that's
I,
guess
why
we
scheduled
that's
like
really
help
with
our
internal
customers,
but
also
it
has
a
bunch
of
uploads.
A
A
Does
anybody
have
any
concerns
over
that
behavior
I'm
just
trying
to
think
it
through
so
just
for
context?
Well,
people
think
of
potential
responses.
The
way
moving
in
she
works
right
now.
Is
it
actually
copies
everything
it
can
to
the
new
project
and
then
it
closes
the
old
issue.
So,
like
you
know,
it's
not
a
move
in
the
sense
that
you
would
move
a
file.
It's
a
move
in
the
sense
that
you
would
let's
copy
it's,
not
a
move,
but
then
the
other
one
gets
closed.
A
You
can
reopen
it
if
you
want,
but
it's
you
know.
You
know
it's
trying
to
preserve
the
history.
Basically,
so
this
one's
within
the
same
project,
it's
you
can't
clone
to
a
different
project,
I
guess
in
future
we
could
consider
adding
like,
if
you
specify
a
project
after
it,
you
can
clone
it
to
a
different
project,
but
that
would
that
would
be
a
future
iteration
yeah.
Does
anybody
have
any
questions
there.
C
A
A
So,
for
instance,
if
you
move
an
issue
from
one
project
in
a
group
to
another
project
in
a
group
and
all
the
labels
are
group
labels,
that's
obviously
easy,
but
you
can
move
it
to
any
other
project,
so
we
try
and
match
them
by
label
title.
So
if
there's
an
issue,
a
label
called
bug
in
the
source
project
and
a
label
called
bug
in
the
destination
project
we
will
match.
You
know
we
will
add
the
bug
label
in
the
destination
project.
A
C
A
One
thing
I'm
just
wondering
here
looking
at
this,
so
it
says
that
no
other
attributes
copied
over
in
the
comment
is
not
copied
over.
Would
we
expect
any
other
attributes
to
be
copied
over
so
I'm
thinking
like
assignees,
probably
doesn't
make
sense,
EPIK
might
or
might
not
make
sense,
milestone
might
or
may
not
make
sense.
A
Weight
might
or
might
not
make
sense.
Confidentiality
I
think
we
should
probably
copy
just
in
case
you
would
copy
a
confidential
issue.
You'd
probably
want
the
new
issue
to
be
confidential
as
well,
but
yeah
I,
think
probably
it
makes
sense
to
not
copy
the
milestone
or
the
epoch,
because
you
might
be
copying
like
a
task
list
to
then
do
in
a
future
issue.
A
Great
I'll
stop
sharing
my
screen,
then
I'm
just
gonna
add
those
to
the
dark
as
well.
Just
so
that
other
people
know
that
we
talked
about
them.
Annabelle
you've
got
a
question:
I,
don't
I
assume
it's
okay
to
do
this
one
we
recording
and
putting
it
publicly,
but
if
you
think
we
shouldn't,
then
I'll
stop
recording.