►
From YouTube: Plan stage weekly - 2021-11-03
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
I
have
the
first
point,
a
demo
for
work,
that
kushal
did
around
work
items
and
essentially
adding
support
for
the
for
the
ability
to
edit
the
title
I
think
natalya
had
done
most
of
the
styling
on
it,
but
kasha
added
the
ability
to
edit
it.
Of
course,
we're
still
mocking
the
back
end,
but
it
looks
pretty
cool
on
the
front.
End.
Give
me
one.
A
Second,
I
will
share
my
screen,
and
this
is
still
there's
a
branch
with
this
because
I'll
still
working
on
it,
though
it's
pretty
close
to
being
done
and
it
so
I'm
gonna,
I'm
gonna
demo.
It
locally.
A
Cool
okay:
I
already
have
a
work
item
up
locally
here,
I'll
refresh
it
have
the
title
here.
There
was
some
back
and
forth
with
ux
product
engineering
on
how
we
wanted
to
how
we
wanted
to
make
it
editable,
I
think,
for
now
the
decision
was
made
to
not
have
a
button
to
essentially
just
click
on
it
and
then
you're
able
to
edit
it
change
and
then
enter
no,
not
to
save
off
click
to
save,
and
then
it
should
be
saved
again,
there's
no
state.
A
Let's
see
how
styling
looks
on
this,
some
styling
is
pretty
much
the
same
for
mobile,
so
it
is
for
desktop.
C
A
Yeah,
I
think
now
that
it's
it's
out
there
and
once
it
goes
through
ux
review,
I
think
there's
going
to
be
a
decent
amount
of
back
and
forth
to
figure
out
what
the
right,
it's
kind
of
it's
one
thing
to
to
think.
Yeah
click
to
edit
on
everything
is
nice,
but
when
you
actually
play
around
with
it,
you
can
find
these
use
cases
on
one
of
these
edge
cases.
A
C
Yeah,
so
I
don't
have
anything
to
demo,
because
there's
no
visual
changes
whatsoever,
hopefully
so
the
progress
on
labels
widget,
is
pretty
good.
It's
behind
a
feature
flag
which
we're
going
to
turn
on
today
on
staging
and
the
plan
stage
group
on
fraud,
hoping
to
turn
it
on
on
production
early
next
week.
C
I
need
to
check
with
natalia
that
we're
not
missing
anything,
but
it's
currently
on
epics,
merge,
requests
issues
and
all
types
of
boards
and
there's
heaps
more
to
migrate,
but
the
fact
that
there's
more
to
micro,
it
doesn't
stop
us
from
like
turning
on
the
future
plug
and
removing
it
if
it
works
and
then
keep
migrating
to
the
new
labels
widget
wherever
needed,
yeah.
So
basically
in
the
next
couple
of
weeks,
if
you
see
problems
with
label,
select,
let
us
know
but
yeah.
C
I
think
we're
pretty
close
like
in
my
opinion,
the
labels
widget
itself
is
is
ready
to
be
used
or
at
least
tested
and.
D
C
So
that
that
was,
that
was
a
big
effort
shout
out
to
natalia,
obviously
like
we
mainly
worked
on
it
to
the
two
of
us
union,
helped
a
lot
with
like
regression,
testing
and
reviews
and
stuff
to
make
it
like
as
robust
as
possible,
but
yeah.
Hopefully
we
didn't
miss
anything.
If
we
did
that.
A
Sorry
so
you
said
you're
thinking
next
week,
we'll
get
the
feature
flag
on
for.
C
C
We
may
want
to
do
some
like
more
testing
just
to
be
sure,
but
we've
we've
tested
it
very
extensively
already
on
master,
so
I'm
optimistic
yeah.
We
can
turn
it
on
early
next
week
on
fraud
like
I
just
like.
I
think,
if
something's
wrong
with
it
like
the
best
we
can
do,
is
just
put
it
in
front
of
people
and
if
there's
something
wrong
with
it,
then
it'll
come
back
to
us.
C
There
may
be
use
cases
that
we
didn't
think
about,
because
it's
not
how
we
use
it
like
labels
is
tricky.
It
does
like
this.
Widget
itself
does
a
lot
of
things
and
there's
like
keyboard
shortcuts,
like
there's
a
lot
of
things
happening
in
there.
So
I'm
hoping
if,
if
there's
a
problem
with
it.
A
Yeah,
no,
that
sounds
good.
We
discussed
earlier
about
turning
it
on
for
just
a
planned
stage
group
this
week,
just
to
start
playing
around
with
it.
What
do
you
think
if
we
just
go
ahead
and
turn
it
on
for
gitlab
org
and
then
aim
yeah.
C
Next
week,
and
if
there's
something
major,
we
can
turn
it
off
yeah
we
can,
let's
just
go
ahead
and
break
it.
Let's
do.
A
Yeah:
okay
yeah:
let's
turn
off
forget
lab
org
and
then
next
week
we'll
aim
to
turn
it
on.
C
C
C
D
C
Maybe
what
do
you
think
about,
like
maybe
letting
the
front
end
channel
go
but
like
it's
quite
a
big?
It
could
have
a
pretty
big
impact.
So
I'm
wondering
if
we
should
let
people
know
that
we're
doing
this
just
in
case
like
so
that
people
don't
get
startled.
If
there's
something
that
we
really
missed
about
it
yep.
A
A
Support
channel
yeah
start
with
the
front
end
and
then
just
link
in
the
support
channel
to
your
slack
message.
E
A
E
C
A
And
then
turn
it
on,
even
if
it
is
just
for
gitlab
or
group
in
the
production
channel
instead
of
the
plan
channel
instead,.
A
B
B
C
D
E
Widgets
pre-made
libraries
for
that,
like
pro
something
and
pro
something
else.
B
D
B
B
But
I
had
just
started
seeing
what
the
effort
of
adding
it
is
and
then
yeah.
I
was
just
wondering
like
if
we
want
that
versus
just
tell
people
to
type
markdown.
C
F
F
C
E
My
understanding
that
the
create
team
already
settled
on
a
library
that
comes
with
like
real
time
capability
that
already
includes
this
markdown,
like
rich
text
editing.
So
this
is
something
already
decided
now.
C
B
A
C
A
A
Yeah,
so
it
has
been
asked
by
by
eric
a
little
bit
more
or
yeah
sometime
last
year.
So
it's.
B
Labels
would
be
manageable.
The
main
thing,
the
main
challenge
that
I've
found
so
far
is
getting
all
the
drop
downs
because
tip
tap
uses.
It
different
has
like
its
own
little
drop
down
thing.
That
isn't
tribute,
so
I
don't
know
how
we'd
go
either.
Integrating
tribute
drop
downs
with
it
or
switching
to
use
the
dropdowns
that
it
like
the
different
kind
of
drop
down
model,
yeah.