►
From YouTube: Plan Stage Weekly - 2020-05-27 Part 1
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).
B
First
item
yeah,
just
an
FYI
that
Eugenia
will
be
joining
the
portfolio
and
certified
back-end
team.
You
can
check
out
the
mr,
so
as
of
that
on
mr
I
guess,
it's
official
I'll
continue
the
handover
reports
to
Jake
this
week,
but
Eugenia
will
continue
to
report
to
me,
but
you
can
still
pick
up
issues
from
Project
Management
I
shouldn't
have
too
much
of
an
effect
on
velocity
of
AI
there
either
side
of
the
team
will
simply
move
one
of
our
hires
when
we
got
them
from
certified
over
to
project
management.
C
B
C
A
The
first
step
was
just
getting
the
architecture
in
place
and
switching
or
adding
the
drop
down.
Just
as
like
the
initial
part,
and
then
we
can
start
actually
switching
the
data,
because
right
now
we
still
get
issues
on
issue
boards
through
our
I
think
there
are
a
private
API,
one
of
our
Russell
api's,
we're
switching
that
over
to
graph
QL,
which
will
be
the
next
step,
which
I
talked
about
a
little
bit
later
in
the
meeting.
But
that's
what
they
are
going
to.
A
D
So
there's
a
slot
channel
that
we
spun
up.
If
you
want
to
follow
along
there,
as
well
as
a
bunch
of
questions
that
we
posted
there
were
outputs
of
our
meeting
that
we
posted
to
the
epic
that
I've
linked
to
in
there.
If
you
want
to
hop
in
and
follow
along,
if
you
don't
really
care
that
much,
that's
totally
fine
too,
but
just
trying
to
keep
everybody
in
the
loop
about
things
that
are
going
on,
so
that's
it
market.
Next.
E
Excellent
yeah
just
a
quick
update
tomorrow.
Actually
it's
not
tomorrow,
it's
Friday
I
will
be
presenting
to
the
requirements
management
to
the
public
sector
sales
team.
We're
really
hoping
to
raise
some
awareness
here
as
to
our
offering
there's
been
a
lot
of
interest
there
and
currently
some
of
the
sales
folks
don't
understand
it
as
well
as
they
would
like
to
so.
Hopefully,
this
gives
them
a
better
oversight
as
to
what
it
is,
how
to
use
it
and
they
can
start
asking
their
customers
more
and
more
about.
E
You
know
their
needs
in
this
area,
we're
hoping
to
get
a
lot
more
sort
of
interest
in
it
and
you
know
be
able
to
answer
any
questions
and
hopefully
talk
to
these
customers
and
get
a
great
you
know,
picture
of
how
they're
desiring
to
use
it.
So
that
should
be
interesting.
I'll,
you
know,
put
any
notes,
I
get
from
that
or
any
feedback,
so
I'm,
probably
in
an
issue
somewhere.
So
we
can
already
do
it.
A
G
Okay,
so
this
is
a
quick
demo.
We
recently
added
a
possibility
to
create
new
epic
size
confidential,
and
so
let
me
show
you
so
when
you
are
creating
on
your
epic.
You
have
an
optional
to
mark
it
as
confidential.
As
far
as
I
know,
there
is
no
other
place
where
you
can
create
confidential
epic
or
change
an
existing
epic
to
confidential,
which
will
be
a
next
iteration.
G
So
once
a
big
skate
is
as
confidential,
you
can
add
issues
or
new
epics
to
it
as
you
are
used
to,
but
with
the
limitation
that
only
confidential
issues
or
epics
can
be
added
to
it.
So
if
I
try
to
add
confidential
a
big,
they
should
pass,
but
it
should
not
allow
you
to
add
an
epic
which
is
not
confidential,
and
there
is
a
bug
about
this
now
that
no
clear
error
message
is
displayed
user.
G
G
G
H
G
C
Okay,
what
I
did
have
one
coming
so
I
knew
that
when
we
eat
sure
like
a
confidential
issue
in
the
tree
or
and
the
list
who
a
user
who's
authorized
to
see
it,
we
put
the
little
icon
the
I,
with
the
line
through
it.
I
didn't
see
that
for
the
epics
I
just
want
to
make
sure
we
had
that
visual
indication
that
the
epic
is
confidential
as
well.
G
A
They
should
be
merged
here
in
the
next
couple
days,
so
we'll
see
if
it
works,
because
I'll
have
to
switch
branches
to
get
the
other
one
working,
but
alright
new
iteration
page
since
the
display
iteration
page,
including
where
it's
listed
on
the
sidebar,
is
in
the
other
branch
and
we'll
be
able
to
demo
from
here,
but
they,
the
new
iteration
button,
will
be
within
that
iteration.
This
list
page.
A
A
C
D
So
the
things
with
iterations,
where
they
differ
from
milestones,
is
that
a
milestone
you
don't
have
to
have
a
date.
You
can
have
just
a
start
date.
You
can
have
just
an
end
date
so
like
if
we
ever
want
to
work
towards
like
automatically
calculating
what
team's
velocity
was
from
one
milestone
to
the
next
or
from
one
iteration
to
the
next.
You
basically
can
only
have
one
of
the
things
and
there
can
only
ever
be
one
activity
given
time.
I
Does
it
like,
if
there's
so,
if
you
had
a
start
date
of
May
25th
and
an
end
date
of
June
first
and
then
another
iteration
with
a
start
date
of
June
27th
and
an
end
date
of
May,
5th
or
June
5th,
like
there's
overlap
in-between
there,
but
the
dates
aren't
the
same.
That's
not
allowed
is
that
am
I
understanding
that
correctly?
That's.
D
Allowed
you
just
can't,
have
you
can't
create
a
new
iteration
that
has
dates
that
belong
to
a
other
iteration
within
the
same
group
right?
So
if
you,
if
you
did
May
25th
through
June
1st,
and
you
try
to
create
one
that
started
on
June
1st
through
some
other
period
that
wouldn't
be
allowed,
because
June
1st
already
belongs
to
iteration
a
axis.
H
D
Yes,
that
would
make
complete
sense
and
I
think
that's
what
we're
gonna
shoot
towards.
This
was
just
the
first
step
of
getting
something
out
there,
so
you
could
create
them,
but
I,
don't
know
if
you've
seen
pivotal
tracker
and
how
they
do
it.
It's
kind
of
similar,
similar
to
that
approach
and
I've
even
put
in
the
MVC
report
to
shamelessly
copy
what
they
do,
but
they
basically
let
you
pick
the
day
of
the
week
and
the
start
date
of
your
first
iteration
the
day
of
the
week.
D
H
Like
for
me,
ideally,
why
I'm
not
doing
any
too
much
of
project
management
and
so
on?
Ideally
I
think
you'd
want
to
see
some
sort
of
a
calendar
and
then
the
iteration
spent
through
the
calendar.
So
this
is
how
I'm
visualizing
it,
but
then,
as
a
first
iteration,
you
can
just
go
and
pre
populate
these
fields.
That
should
not
be
sort
of
like
too
difficult
of
a
test
where
we
can
do
that
as
a
next
iteration,
three
and
faster
yes,
but
then
I'm,
making
the
UI
he
likes
more
complex
and
more.
H
D
I
think
all
the
builders
show
the
overlay
of
like
the
previous
iterations
on
the
calendar
when
you're
picking,
so
you
don't
accidentally
pick
I
get
just
a
little
bit
of
feedback.
Saying
like
you
can't
pick
this
date
before
even
get
to
that
point.
Get
the
validation
message.
There's
lots
of
cool
things
that
we
can
do
with
it.
Then
I'm
excited
to
iterate
on.
A
Cool
ok,
I'm
back
up
here
so,
as
you
can
see,
iterations
is
added
to
the
issues
drop
down.
There
click
on
that
and
we
see
the
list
of
the
two
iterations
that
have
been
created
and
then
I'll
click
into
there,
but
that
that
is
not
complete.
Yet
the
actual
iterations
page
or
the
report
view.
But
that's
what
we'll
see
when
they
click
on
that.
D
J
Search
experience
is
going
to
be
in
hopefully
13.2
and
so
right
now
I
have
it
some
form
of
experimental
things
running
on
rune,
that
page,
so
on
the
top
portion.
What
you
are
seeing
is
the
traditional
filtered
search
that
we
have
been
running
for
ages.
It
is
implementation
of
Hamel
and
plain
JavaScript.
J
It
has
been
serving
us
well,
but
as
you
know
that
today,
if
you
apply
any
filters
on
whole
map
page
or
an
epic
page
or
issues
or
amounts
anywhere,
basically,
where
we
have
this
type
of
filtered
search
in
place,
you
would
have
to
hit
enter
once
the
filters
are
applied
and
it
could
reload
the
page
add
those
values
in
the
query
patterns
and
then
the
data
will
be
loaded.
We
want
to
make
it
asynchronous
because
most
of
the
pages
or
most
of
the
features
rather
have
the
data
being
loaded
AC.
J
So
it
doesn't
make
sense
to
reload
the
page.
We
can
just
make
another
call
like
the
page
as
it
is
and
refresh
the
data
instead
of
reloading
the
whole
page.
So
this
is
how
it
looks
right
now,
so
the
bottom
portion
is
the
newer
one.
Of
course,
it
doesn't
currently
do
any
kind
of
data.
Filtering
I
am
yet
two
of
the
things
to
make
the
filters
working,
but
this
should
give
you
a
brief
idea
of
how
it
will
look
like.
J
Obviously,
there
are
some
rough
edges
like
the
button
sizes
and
the
models
and
everything,
but
since
this
is
a
component
which
is
coming
from
our
UI
library,
so
that
isn't
already
work
going
on
in
order
to
polish
these
components,
so
it
supports
all
the
necessary
features
that
we
have
like
recent
searches.
The
only
difference
is
that
we
are
not
really
literally
calling
it
calling
it
recent
searches.
We
just
have
the
button
with
the
Rob
down,
and
the
items
show
up
here
and
sorting
also
is
the
same.
J
Just
the
look
and
feel
of
the
drop-down
and
everything
looks
different.
Currently,
labels
support
is
not
there
within
the
component
that
we
are
using.
It
is
working
for
this,
so
it
is
very
experimental.
As
far
as
this
filtering
UI
is
concerned,
our
first
plan,
at
least
for
30
dot,
is
to
make
it
working
for
requirements
page
so
right
now,
requirements
page
only
supports
filtering
based
on
author,
as
well
as
plain
text.
J
So
that's
what
we'll
be
aiming
for
infer
did
not
oh
well
still
get
the
progress
working
for
or
not
just
that
it
will
be
behind
features
like
so
one
syllable
support
is
there
will
enable
it
on
production
by
adding
the
labels
for
over
that
piece.
So
right
now,
if
you
click
on
water,
it
will
list
down
all
the
authors
and
the
author
will
show
it
in
the
same
fashion
as
we
see
in
other
places.
Same
thing
goes
for
drop-down.
J
K
K
K
Right
now
we're
we're
still
missing
some
some
things,
for
example
the
the
quick
action
suggestions
and
some
styling
on
the
label,
but
you
can
fold
that
and
make
a
following
of
that
on
the
on
the
issue:
I
have
the
market
update
it
and
yes,
this
lit
up
pretty
quick
demo.
But
let
me
know
what
do
you
think
about
this.
C
Now
yeah,
this
is
great.
It's
like
one
of
the
larger
kind
of
pieces
of
feedback
around
like
creating
epics
is
wanting
a
page
that
looks
similar
to
the
issue
page,
so
that
looks
familiar
and
users
can
actually
spin
up
the
full
epic
instead
of
creating
a
clicking
over
to
it
so
being
able
to
create
an
epic
with
a
third
of
the
clicks
it
requires
now,
as
is
a
huge
improvement,
so
well
done.
It
looks
great.
D
Yeah,
that
does
look
great
one
thing
that
I
happen
to
notice
just
when
looking
at
this
is
the
similarity
between
this
and
the
great
iteration
view,
like
the
only
difference
is
like
the
labels
picker
and
maybe
some
validation
rules
which
we've
come
from
I
guess
you
could
set
that
one
is
confidential,
but
is
there
like
how
we
thought
about
making
some
sort
of
reasonable
component?
The
creation
type
form
thing
where
it
doesn't
have
like
a
bunch
of
conditionals
within
it,
but
you
can
more
or
less
like
configure
it.
D
K
Yeah,
like
oh,
the
the
improvement
I'm
making
here
I
believe
the
the
biggest
one
is
going
to
be
to
create
these
this
company,
because
this
is
a
different
company
in
a
different
home,
basic
component
style
as
the
diversity
of
the
guild
of
UI
elements,
but
but
yeah
I
believe
what
nothing
proofing.
Well,
it's
going
to
be
to
add
these
two
to
get
sub
you
guys,
so
we
could
use
it
in
the
rest
of
the
forest,
for
example,.
A
Yeah
so
I
think
a
lot
of
this
was
taken
from
the
iterations
form.
I,
don't
think,
we've
put
it
put
these
components
within
a
wrapper.
That
might
make
sense,
though,
to
do
because,
like
you
said,
gave
a
few
of
the
creation
forms
are
sharing
a
lot
of
these
components.
The
actual
form
components
on
this
page
are
all
be
reusable
right.
Correct
me
if
I'm
wrong,
XO
but
I
think
they're
all.