►
From YouTube: Plan stage weekly - 2020-04-01
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
B
C
D
D
So
here
we
have
the
road
map
and
what's
news
that
for
head
roadmap
for
epics
to
have
child
epics,
you
now
have
this
chevron
at
the
side
indicate
that
you
can
expand
it
and
also
the
rate
of
the
detail
section.
You
have
this
new
icon,
which
tells
you
how
many
child
ethics
that
epoch
has
so
by
clicking
the
Chevron.
You
can
expand
to
see
all
the
child
epics
on
the
roadmap
and
that's
it.
D
E
F
B
This
is
really
cool,
I,
don't
like
talking
to
a
customer
yesterday
and
we
are
showing
them
the
progress
reporting
and
their
next
question
was
like
well.
Why
can't
I
drill
down
to
see
more
we're
like?
Oh
well,
that's
coming
soon,
so
this
is
a
huge
step
in
the
right
direction
and
I
think
it's
gonna
be
received.
Well,
so.
H
B
B
H
Thing
we're
looking
into
is
allowing
users
to
set
time
frame
so
they're,
not
looking
at
like
basically
every
time
every
time
frame
ever
it
would
just
be
the
time
frame
they
care
about,
and
then
maybe
a
future
iteration
could
be
allowing
them
to
kind
of
freshen
zoom
within
that
time
frame
as
well.
So
I
think
I
will
help
performance.
I
I'm
asking
just
because
they're
also
related,
if
you
are
free
to
request
to
be
able
to
expand
the
ball
I
pick
three,
where
we
could
probably
reuse
this
functionality.
If
we
could
just
run
multiple
multiple
requests,
I
guess
we
do
the
same
on
Roma
page
tool
to
load
different
levels.
So
perhaps
we
can
use
it
there
too.
I
A
A
Comments
or
discussions
so
previously
and
I'm
pretty
excited
for
this
one,
because
my
scroll
wheel
is
terrible.
So
when
you
get
that
super
long
list
of
comments-
and
you
just
want
to
or
I'm
normally
at
the
bottom
to
see
the
most
updated
one
and
then
I
have
to
scroll
back
to
the
discussion
on
the
top.
It's
just
a
huge
hassle.
So
Scott
worked
on
the
front
end
for
this
and
this
one
that
was
actually
all
front-end
I
believe
so
far,
but
this
is
just
adding
a
setting
to
reverse
the
order.
A
So
by
default
it
went
oldest
first-
and
this
is
I
just
activated
this
within
our
plan
project.
So
now
we
have
this
here.
This
is
oldest,
first
switch,
it
the
newest
first
that
reverses.
It
also
reverses
the
the
input
field
here,
but,
as
you
can
see
now
we
have
the
most
recent
one
on
top,
which
is
nice.
A
The
reason
why
I
have
not
turned
this
on
for
all
of
gitlab
calm
yet
is
because
we
do
want
to
save
this
setting
so
they're
not
having
the
switch.
So
it's
not
on
an
issue-by-issue
case,
which
it
is
right
now,
but
Scott's,
working
on
and
I
think
the
mr
may
have
already
been
merged
in,
but
using
local
storage
to
save
the
users
preference
there.
B
B
I'll
put
it
through
the
paces
yeah
in
the
planning
project.
This
is
really
awesome
too,
like
this
has
been
a
huge
internal
requests
and
I.
Think
we
wanted
to
tree
is
an
experiment
to
see
if,
like
what,
what
the
same
default
would
be
eventually
so
use
cases
was
largely
around
people
who
are
doing
incident
management
and,
like
don't
want
to
look
at
the
entire
history,
but
like
Neath,
the
last
few
things
and
then
to
respond
to
the
next
thing.
So
I
think
it'll
help
expand
some
of
those
other
workflows
and
I'm
excited
about
it.
E
A
B
J
Sorry
I
missed
the
earlier
part
of
the
call
to
be
like
saving
games
like
I
was
under
the
impression
it
would
be
8:00
p.m.
is
fee
and
the
call
was
an
hour
early
so
totally
missed
it.
So,
following
up
on
pagination
I'm,
not
sure
if
Donna
brought
it
up
around
the
pagination
that
we
are
trying
to
do
on
requirements
management
so
before
I
put
it
on
the
agenda
quickly
demonstrate
on
requirements.
J
So
the
pagination
is
taken
care
of
by
the
backend
during
the
rendering,
as
well
as
how
the
page
numbers
and
everything
works.
One
thing
that
comes
for
free
with
that
approach
is
that
you
get
the
URL
that
can
be
permalink
in
a
way.
So
if
you
go
to
issues
page
on
any
project
currently
which
has
more
than
20
issues,
then
you
can
click
on
next
page,
and
it
will
take
you
to
the
second
page
and
you
can
see
that
the
URL
gets
updated
with
the
page
number.
J
At
the
time
of
opening
the
URL
and
in
case
of
graph
QL,
since
the
entire
entering
happens
on
the
client
side
like
to
be
make
the
request,
we
face
the
first
page
items
and
then
we
render
it
on
the
way
we
need
to
manually
take
care
of
pagination
as
well
in
Bay
that
URL
can
still
be
pummelling
so
that
someone
can
copy
the
URL
and
then
ensure
that
they
are
on
the
right
URL,
so
I'll
quickly
demonstrate
on
how
it
currently
works
at
the
moment.
This
is
something
that
we
haven't
pushed
on.
J
Dmr
branch,
yet
I
will
be
pushing
it
later
today,
but
just
to
give
you
an
idea
on
how
it
differs
compared
to
what
we
have
so
right.
Now,
I
am
on
this
page,
so
I'm
currently
setting
the
page
size
to
only
have
first
five
items
instead
of
20
items.
Obviously,
once
this
Emer
gets
merged,
we
will
default
to
20
items
on
the
list,
so
this
particular
project
has
25
requirements
and
we
are
showing
recent
5
requirements
since
up
in
sizes,
5
and
based
on
that.
J
The
pagination
bar
here
shows
number
of
pages
that
we
have
now,
when
you
click
on
next
notice
that
we
do
not
reload
the
entire
page.
Instead,
we
just
make
another
request
with
the
new
page
number
and
now,
first
second
page,
consisting
of
next
5
items
on
the
list
show
up
and
at
the
same
time
we
are
also
updating
the
URL.
J
So
as
you
can
see
that
in
the
URL
there
are
two
parry
params
appended,
one
is
next
and
then
there
is
the
string
which
is
a
cursor
value,
and
then
there
is
this
page
number
which
is
2
and
when
I
click
on
next
again
the
strain
again
updates.
If
I
click
on
previous
it
will
go
back
to
the
previous
page,
will
fetch
in
whatever
that
was
on
the
second
page
and
then,
if
I
go
to
previous
again,
it
will
basically
go
back.
J
So
this
is
how
the
URL
differs
compared
to
what
we
have
in
issue
space
like
right
now,
if
I
go
to
issues
page
so,
for
example,
if
I
change
it
to
IB,
remove
of
the
parents
here
and
just
reload
the
page.
This
particular
issues
project
has
36
issues.
So
if
I
click
on
next,
it
reloads
the
idle
page
and
then
the
page
number
changes
there
is
no
cursor
value
present.
Although
we
have
page
number
and
cursor
both
present
the
param,
that
is
responsible
for
fetching
results
for
a
specific
page.
J
Is
this
previous
and
the
cursor
value
so
I
just
wanted
to
know
the
thoughts
of
rest
of
the
team
like
whether
you
like
this
approach,
which
is
not
very
consistent
with
the
rest
of
the
places
or
if
at
all,
do
we
need
pagination?
Even
with
this
kind
of
approach
on
requirements
like
at
the
start,
we
can
still
be
fine
without
pagination
or
requirements
like.
J
Obviously,
this
feature
is
still
behind
flag
and
nobody
is
using
is
except
for
us,
but
once
we
do
end
up
with
more
requirements
like
Jung
can
probably
I
mean
like
what
is
the
hard
limit
on
the
page
size
that
we
have
said
currently
four
requirements
globally
in
our
code
base,
because
right
now
on
the
client
side,
I
am
setting
a
requirement.
A
size
is
20,
but
I
am
sure
there
is
some
hard
limit.
Similarly,.
J
So
these
are
the
only
possible
option
as
of
now,
but
is
it
fine?
Well
this
kind
of
approach,
because
there
are
other
caveats-
has
been
like
right
now.
We
are
updating,
query,
parameter
RS
without
reloading
the
page.
This
is
something
that
requires
us
to
use
certain
browser.
Api
like
we
are
updating
browser
history,
API
to
change
the
values
of
URL.
So,
for
example,
if
I
click
on
next
and
now
click
on
back,
you
can
see
that
the
page
does
not
update
it.
J
So
we
we
do
use
push
state
just
that
the
the
idea
of
having
history
dot
push
state
as
an
API
was
to
use
with
hash
tags
and,
unlike
other
places,
we
are
not
using
hash
tags
here
like
if
you
go
to
web
ID
today,
and
if
you
open
any
file,
then
the
state
of
the
web
ID
is
preserved.
You
know
hash
tag
description,
so
when
you
do
back
end
forward
hash
tag,
events
are
propagated
correctly
into
the
front
end.
J
App
and
app
is
aware
of
those
hash
tag,
changes
which
is
not
the
case
here
like
here.
We
are
updating
weary
params
right
away
because
we
don't
want
to
introduce
you
to
handle
query
parameters
just
for
the
requirements.
This
page,
like
you,
you
can
notice
immediately.
We
have
here
question
mark
which
denotes
that
these
are
query
parameters
and
the
hash
tag
parameters.
J
We
do
not
have
a
hash
tag
mechanism
at
all,
so
if
we
are
fine
with
those
inconsistencies
between
the
two
sides
of
things
like
requirements
is
obviously
a
new
area,
but
at
the
same
time,
people
are
going
to
look
at
it
similar
to
how
other
listing
pages
work
like
issues
and
Amar's
are
adjacent
to
requirements
list.
So
you
want
to
make
sure
we
are
consistent
to
other
places
as
much
as
possible
like
we
do
not
want
to
introduce
a
new
approach
just
because
it's.
K
E
J
So,
as
you
can
see
that
I
copied,
whatever
that
was
there
on
car
keys
and
just
opened
it
here
and
there
it
is,
it
directly
dropped
me
on
the
third
page
and
provided
me
with
the
values
which
were
present
on
the
first
page.
So
obviously
we
are
using
these
values
and
passing
it
on
as
very
parents
to
the
app
while
it
gets
initialized
and
passing
on
those
values
into
the
query
as
well.
J
A
Yeah
I
agree
with
that
and
I
think
eventually
down
down
the
road
issues
and
em
ours
and
all
of
our
search
pages
will
be
migrated
to
a
graph,
QL
and
I.
Think
that
the
cursor
based
pagination
is
just
not
only
incorrect
well
but
like
searching
like
through
elastic
search
I,
think
they
use
a
cursor
based
pagination
too
so
I
think
most
places
we're
moving
courser
based
versus
offset
or
page
number
on
pagination
I.
A
Think
the
only
question
is:
are
we
okay
from
a
UX
perspective
of
having
that
cursor
in
the
attached
as
part
of
the
URL?
So
one
question
I
had
on
that,
though
Kashan
and
yon?
Is
there
any
way,
so
the
cursor
is
huge
and
a
little
ugly?
Is
there
any
way
we
can
use
like
ID
as
a
cursor
like
idea
of
the
requirement?
That's.
I
The
sort
of
question
I
suppose
that
in
theory,
yes,
but
it
will
be
better
to
check
with
Fred
Walker,
who
did
most
of
the
stuff
on
graph
girl
stuff
for
pagination,
because
I
think
that
is
just
base64
encoded
string,
which
wraps
ID
with
some
model
representation.
So
in
theory
it
you
should
be
able
to
still
take
requirement,
ID
and
encoded
in
base64,
but
I'm,
not
sure
if
it's
preferred
by
or
not
so
better
to
check
like.
A
L
E
From
from
back
inside,
it
is
functional
at
this
point,
I
did
on
github
hope,
I
didn't
draw
any
input,
so
it
does
input,
but
we
still
need
to
work
on
the
UI
UX.
So
that
part
is
now
is
not
implemented.
A
up
and
I
know
we're
working
right.
So
that's
I
think
that's
what's
kind
of
flat
to
be
sure
they
have
to
be
very,
and
there
is
not
to
say
that
there
is
an
out
back-end
work
to
be
down
there.
E
There
is
a
craftwell
part
at
the
very
least,
and
then
there
is
some
refactoring
that
I
would
really
love
to
do
in
the
MVC
to
bring
it
into
MVC.
In
regards
to
word,
and
how
do
we
store
the
JIRA
import
progress
and
all
the
data
associated
with
it
and
not
store
it
in
the
sort
of
the
legacy
tables
and
data
structure
so
that
we
don't
to
do
all
sorts
of
migrations
afterwards
and
just
I
love
fun,
cleaning
that
up
so
I'd
love
to
get
that
into,
and
hopefully
I'll
do
so.
D
And
from
my
side,
I've
just
been
working
on
creating
the
various
UI
screens.
Everything
is
going
frame
so
far
and
the
most
recent
thing
that
I
know
is
that
for
the
year
import
form
there's
been
discussions
on
and
how
well
there's
been
discussions
on
tweaks
on
it.
So
that's
a
most
recent
thing.
That's
kind
of
blocking
the
front
end
I,
guess
in
regards
to
completing
an
UI.
K
For
so
the
question
that
we
currently
have
is
surrounding
the
label,
portion
and
I.
Think
we've
already
got
it
built
in
that
labels
are
automatically
generated.
I
think
what
we're
kind
of
trying
to
sort
through
right
now
is
what
the
UI
looks
like
for
that
particular
screen,
which
I've
already
got
a
wireframe
in
place,
I'm
just
making
some
minor
tweaks
to
it.
K
It
makes
the
label
like
this
make,
which
is
something
I
don't
like,
but
it's
clear
and
it's
thorough,
so
the
user
definitely
knows
what
import
that
label
is
associated
with
it's
easy
to
determine
the
project,
it's
a
little
harder
to
clarify
if
they
have
imported
multiple
times
which
import
that
you're
looking
at.
So
that's
why
it's
kind
of
long
and
I.
Don't
love
the
solution,
but
I
think
that
it's
clear,
so
that's
that's
kind
of
where
that
discussion
is
right.
Now.
E
K
Could
be
that
could
be
a
more
succinct
way
to
show
it
more
than
anything,
I
want
to
understand
what
all
of
that
means
to
the
user.
Is
it
meaningful
enough
to
them?
Does
it
do
they
understand
what
that
information
is
telling
them,
and
can
they
easily
find
the
issues
associated
with
that
information?
They
need
to
so
I'm
kind
of
thinking
on
it
today
and
I
hope
to
have
a
solution
in
place
by
the
end
of
the
day,
so
that
we
don't
hold
that
kong.
L
C
L
K
I
think
we
might
end
up
doing
that.
I,
just
can't
I
can't
move
forward
without
feeling
like
I
spent
at
least
a
little
bit
of
time.
Thinking
about
what
the
possible
consequences
are
that
decision.
So
that's
my
plan
for
now
is
we
probably
will
move
forward
with
it,
as
is
so
that
we
don't
have
to
do
any
reward
I'm
aside
from
what
Kong
has
already
done
on
the
UI
side,
but
hopefully,
hopefully,
I
can
just
kind
of
think
through
any
challenges
that
we
might
have
and
prepared
for
that.
You.
B
C
K
G
C
There
was
a
plan,
I
think
Jeff.
Then
you
were
going
to
do
like
a
demo
of
the
thing
like
record
it
on
for
YouTube
or
something
so
my
understanding
was
we
have.
We
have
something.
Neither
if
we
lift
the
feature
flag
for
a
project.
Imports
will
allow
users
to
import
issues
from
JIRA
into
github
right
or
am
I
mistaken.
No.
G
I
I
think
it
works.
I
I
wanted
to
do
like
a
cleaner
I
like
I,
wanted
to
go,
create
a
new
jura
project
with
a
handful
of
issues
just
to
kind
of
run
through
it
and
see,
but
I
can
I
can
do
that
today
and
follow
back
up
in
case
I,
see
anything
funky
but
yeah
on.
C
L
Yeah,
no,
that's
a
that's
good
clarity
and
that's
great
because
we're
that
means
we
check
the
box
before
the
end
it
the
end
of
12
in
which
is
good,
I,
think
yeah.
So
I,
it's
really,
let's
just
be
cognizant
of
the
10
working
days
and
if
there's
improvements
that
we
are
confident,
we
can
get
done
in
that
timeframe.
That's
great
hammer
amount,
let's
get
it
through,
but
again
like
the
worst
thing
that
could
happen
is
for
this
did
not
work
like
in
by
the
by
the
17th.
L
Don't
don't
bring
it
yeah
I
know.
Nobody
would
obviously
do
that
intentionally,
but
I
think
we
just
need
to
be
a
little
more
careful
with
this
one,
because
it
does
have
the
visibility
it
does,
and
it's
got
the
there's
a
lot
of
emotion,
wrapped
up
in
it.
So
I'm
I'm
really
proud
of
the
team
for
getting
this
to
where
it
is
now
and
it's
like
yeah,
let's
just
bring
home
and
keep
moving
board
go
team.
That's
pretty
cool.
I
realized
we're
already
at
that
point.
What.
G
I
B
Charlie's
mentioned
that
it
would
be
helpful,
especially
for
her
as
it's
like
very
early
in
her
day,
I
think
to
have
a
better
time
zone
for
like
the
APEC
area
and
also
doing
it
weekly.
So
we
took
a
little
bit
of
time.
I
show
you
play
some
scribble
or
Scrabble,
or
was
it
scribble
anyway?
It
was
fun,
yeah
yeah!
No,
no!
It's
like
scribble
I,
think
it's
scribble
Dada
or
something
with
the
K
yeah.
B
It
was
super
fun
and-
and
so
she
just
said
like
a
it
would
be
nice
if
it
was
a
better
time
slot
for
her
and
then
also
to
do
it
weekly
and
so
on.
Tuesday
it'd,
be
you
know
the
times
at
one
time,
zone
on
Thursday
beat
the
other
time
zone
and
how
that'd
be
like
a
standing
weekly
thing,
so
I
just
wanted
to
check
the
pulse
and
see
if
anyone
was
interested
in
doing
that
and
if
so,
what
time
works
best
for
folks
I
would.
C
L
B
Okay,
well,
I
will
I
will
I
think
it's
also
good
Justin.
It
looks
like
opened
up
a
recurring
plan
team
day.
I
think
that
that
was
like
a
cool
thing
to
do
like
a
bigger
one
across
everyone,
but
I'll
also
open
up
an
issue
to
get
a
sink
input
from
folks
in
the
different
time
zones
about
what
would
work
best
for
them
to
make
sure
we
can
do
that
except
it
was
a
ton
of
fun
yesterday
and
I
think
it's
it's
a
good
thing
to
do
more
frequently
so
yeah.
L
B
Think
I
had
the
last
item
and
I
just
I
wanted
to
apologize.
If
my
tone
and
the
ad
hoc
retrospective
came
across
like
negative
towards
in
like
any
individual
on
our
team
and
that
wasn't,
my
intent
at
all,
I
am
very
passionate
about
what
we're
working
on
and
very
passionate
about
our
values
and
about
serving
our
customers
well
and
also
being
a
good
team
member,
and
so
sometimes
that
can
come
across
as
like
I.
Don't
don't
think
we're
doing
anything
valuable,
which
is
not
the
case
whatsoever.
B
I
think
we're
doing
amazing
work
I
also
in
the
spirit
of
Bing
lean
and
I,
want
to
continuously
improve
and
focus
on
doing
that.
So
I
just
wanted
to
first
apologize
and
let
folks
know
that
the
goal
is
talking
about
process
improvement
and
not
that
I'm
we're
not
doing
a
good
job.
The
other
is
is
like
how
can
I
help
and
if
nobody
has
feedback,
that's
fine
too,
but
how
can
I
help
make
that
document
or
that
ad
hoc
retrospective
a
little
bit
more
inclusive
for
everyone?
G
E
Most
of
the
points
were
kind
of
splashed
on
so
yeah
I
didn't
feel,
like
repeat
what
was
well
really
mentioned,
makes
too
much
sense.
Try
to
eat
a
couple
emoji,
they
are
bad
yeah
and
then
one
other
aspect
is
I
saw.
There
was
a
retro
call,
I'm,
not
sure
if
what
it
was
based
on
on
the
he
shoots
out
for
just
a
retro
call
on
the
release.
L
That
plan
iteration
retrospective,
yes,
yeah,
yeah,
sorry
about
that
yeah
we
yeah
that
was
a.
They
are
piloting
a
new
set
of
onboarding
tasks
and
training
for
new
employees
to
like
lean
into
it,
a
ssin,
and
they
asked
the
PM's
and
Ian's
to
kind
of
go
through
a
first
round
and
get
feedback.
So
that's
what
that
was
yeah.
There
wasn't
anything
specific
about
us
or
the
team.
We
just
kind
of
got
asked
to
pilot,
and
it's
really
just
going
through
an
issue
and
Syd's
iteration
offer
office
hours
and
I.
L
E
G
I
think
I've
seen
my
because
I
made
a
comment
on
Gabe's
retrospective
issue,
because
I
thought
we
had
a
pretty
good
discussion.
I
should
encourage
all
of
you
to
watch
that
video,
because
kina
did
post
on
YouTube.
If
you
haven't,
we
had
a
good
discussion
on
like
what
went
well
from
like
a
process
standpoint
with
the
JIRA
importer
work.
G
It's
something
we'll
obviously
talk
about
in
the
formal
retro
for
twelve
ten
I'd
assume,
but
it
was
because
we've
been
doing
this
training
or
piloting
this
training,
and
it
gave
a
good
opportunity
for
us
to
chat
about
it.
So
I'd
encourage
you
to
watch
it,
and
if
you
have
suggestions
or
comments
or
feedback,
you
can
drop
it
on
Gabe's
issue
or
do
it
elsewhere.
But.
L
C
Ya-
just
from
my
point
of
view
like
to
say
thanks:
okay
before
for
coming
in
and
person,
and
that
I'd
encourage
everyone
to
go
in
on
on,
have
read
through
everything
in
the
issue
and
if
you
have
anything
to
add,
please
like
to
add
it
and
like
to
feel
like
you
can
add
it
to
the
issue.
If
you
don't
feel
like,
you
can,
of
course
contact
one
of
us
and
be
happy
to
reassure
you,
but
it
is
a
blameless
retrospective.
So
it
should
be
possible
for
now
that
we
have
some
perspective
of
from
Gabe.
L
Yeah
yeah
I
mean
it's
a
big
bit
of
journaling.
You
know
what
we
do
is
hard
and
we
all
there's
different
different
parts
of
it
or
hard
for
different
roles
and
it's
hard
to
rest
all
to
see
that
and
I
think
retros
are
a
great
opportunity
for
us
to
like
talk
through.
Like
you
know,
from
like
the
PM
side.
L
I'll
admit:
I
I
probably
have
I
need
to
be
more
cognizant
of
tone
when
I
ask
questions
because
I
got
to
realize
it's
being
read
and
not
heard,
and
so
yeah
just
will
keep
improving
together.
Just
be
honest-
and
you
know
have
some
understand-
assume
good
intent,
I'm
really
trying
to
work
on
that
too.
Personally,
so
I
don't
I
love
our
team,
we're
doing
good,
we'll
keep
him
there.
C
C
It
would
be
good,
maybe
we
could
talk
for
the
health
status
stuff,
for
example,
we
could
to
find
ways
where
we're
doing
both
we're
we're
like
feeding
back
better
quality
information
to
PM's,
but
also
protecting
our
workflows
from
from
interruptions
in
focus
time
and
things
that
actually
do
cost
us
dearly
in
terms
of
like
how
I
can
ship
stuff
you
know,
so
I
do
believe
that
there
are
process
improvements
that
optimize
both
right.
Yeah.
Oh.