►
From YouTube: Plan stage weekly - 2020-07-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
B
B
A
A
A
A
Icon
was
added
here
and
also
you
could
tell
it's
confidential
there.
That
also
did
not
exist
previously
and
then,
where
it
did
exist,
was
there's
a
lot
of
comments
on
this.
One
was
here:
I
did
show
that
it
was
a
confidential
epic,
but
actually
said
it's
a
lot,
the
old
copy
or
the
copy
from
issue.
So
it
said
I
believe
this
is
a
confidential
issue.
D
Yeah
iteration
report:
let's
do
it
so
I
shall
demo
twofold.
Here's
the
first
part
of
the
demo,
which
is
the
actual
thing
we
got
get
out
of
the
way
there
zoom
we've
added
everything
below
the
iteration
description
here
on
an
iteration
page
they've
got
these
boxes
with
completed
stats
and
stuff,
and
then
a
list
of
issues.
These
issues
have
boring
titles,
because
I
haven't
figured
out
how
to
do
custom
titles.
D
D
The
other
neat
thing
in
this
example
is:
this
was
feature
spec
I
wrote
because
I
wanted
some
better
numbers.
My
dev
numbers
are
always
really
low
and
manually
creating
iterations
and
issues
and
stuff
was
challenging,
so
I
found
out
about
create
list
in
feature
specs,
so
I
just
wrote
like
there
was
this
existing
feature
spec
if
the
iteration
related
stuff
and
I
just
thought,
how
can
I
create
like
60
issues
and
assign
them
to
this
iteration?
D
A
You
sweet
it's
exciting.
It's
looking
good
all
right
back
to
me
for
Kong
in
York,
the
next
step
in
JIRA
user
map.
A
All
right,
this
one
I
am
demoing
locally
and
already
here
on
the
page,
I,
don't
remember
what
it
was.
What
it
looked
like
last
time
we
demoed
this,
but
we
have
actual
data
now,
which
is
great.
So
we
have
our
JIRA
users
here
on
the
left
hand,
side
and
for
each
one
they
can
change
and
a
tag.
It
lab
username,
there's
an
issue
we're
still
working
through
on
the
graph
QL
API
to
get
users
within
a
project.
So
it's
currently
being
worked
on
so
we're
not.
A
E
E
And
the
other
small
change
whoops,
the
other
small
change
is
I-
have
dated
the
collapse.
Tate
the
headers
here
and
the
tooltips
on
this
are
all
custom
depending
on
what
type
of
list
it
is,
so
it
works
for
assignees
labels
milestones
and
whichever
type
of
list
it
is.
So
this
is
much
Freyr
like
it
used
to
use
the
normal
collapse
state.
So
this
is
all
fixed
now
and
it's
pretty.
A
Lastly,
it
looks
like
unless
we
have
other
things
to
talk
about
afterwards,
I'll
go
through
the
goals
for
the
front-end
team
for
the
for
the
next
week,
just
real
quickly.
We
want
to
get
done.
First
thing
is
add
the
iteration
report
that
we
saw
that
Simon
demoed
I'm
edit
projects,
hoping
I,
get
that
done.
There's
that
can
work
for
that
too,
but
we're
hoping
to
get
it
done.
A
E
E
The
ones
under
epochs
would
be
accurate,
but
the
ones
under
unassigned
could
not
be
accurate,
because
the
backend
would
not
be
ready
for
it,
and
I
would
need
to
do
some
data.
Manipulation
which
we'd
probably
be
done
later,
like
the
goal
for
next
week,
would
be
displaying
some
issues
in
there
and
make
sure
that
it
looks
pretty
and
that
it
works
and
that
you
can
scroll
through
things,
and
it
just
makes
sense
when
you
display
issues
on
that
screen.
A
E
A
Perfect
for
the
ListView
we've
been
doing
work
to
get
the
list
view
on
issues
over
to
view
the
next
week.
We
want
to
finish
up
that
within
projects
and
groups,
but
then
also
I
get
epics.
Could
that
explicit?
You
refactor
it
over
to
to
view
also
last
goal
we
have
is
to
add
health
status
to
issue
lists,
since
we
are
so
close
on
the
issue.
Let's
refactor
for
projects
and
groups
are
able
to
now
add
things
to
that
to
the
view
app.
So
the
first
thing
we're
gonna
do
is
add
the
health
status
to
it.
A
C
Yes,
sorry
except
my
computer,
wasn't
working
so
I
just
found
out
why
Project
issuable
lists
wasn't
working
when
I
turned
it
on.
There
was
a
response
header
that
was
put
in
place
to
get
the
total
count
of
the
issues,
but
in
11
something
I
think
that
one
of
the
teams
decided
not
to
send
that
header
over.
If
the
number
of
issues
exceeded
10,000,
so
pagination
won't
show
up
now.
So
we
have
to
figure
out
how
we
want
to
retrieve
that
total
count
from
the
API.
C
A
Oh
awesome,
okay,
cool
good
news
is
I
mean
we
probably
don't
have
too
many
groups
that
have
more
than
10,000
epics,
so
it
should
work
for
the
epic
page
when
we
work
on
that,
but
yeah
that
makes
sense,
I
think
to
work
on
to
figure
out
how
to
get
the
pagination
working
on
a
first
before
we
before
work
on
the
epic
yeah,
yeah
cool,
all
right.
Anyone
else
have
anything
else,
no
short
sweet
front,
nd
front
end
heavy.