►
From YouTube: Testing PM/UX Meeting - 2021-03-02
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
So
this
is
this:
is
the
verified
testing
product,
ux,
weekly
sync,
with
hyanna,
and
I
and
james
for
march,
2nd
it's
been
a
little
while,
but
we're
catching
up
synchronously.
So
why
don't?
We
kick
off
with
follow-up
you'd
asked
in
our
async
last
week
with
pedro
reopening
the
code
quality
in
the
mr
diff
design
item,
what
the
stack
rank
was-
and
I
put
that
into
last
week's
agenda,
but
just
to
read
it
out.
A
That
was
the
the
rank
I
gave
you
last
week,
but
my
first
topic
to
discuss
when
we
get
to
it
is
sliding
something
in
there
before
the
unit
tests
work.
But
I
think
that
was
the
only
follow-up
that
we
had
from
last
week.
B
B
So
for
the
sake
of
iteration,
it's
not
linked
to
the
issue
description.
I
couldn't
find
on
figma
as
well,
and
I
asked
vitica
for
the
file
for
the
sake
of
the
iteration.
I
added
to
the
issue
description.
The
proposal
of
what
the
behavior
the
size
is,
the
anyways.
The
acceptance
criteria
would
look
like,
but
I
agree
with
pedro.
B
It
would
be
nice
to
have
at
least
the
what
the
ui
looks
like
in
the
side-by-side
mode
of
the
div,
because
that
change
only
applies
to
one
of
the
one
of
the
modes
of
the
request,
view
yeah,
but
then
oops
sorry,
my
screen
is
all
dark
now,
but
then
I
think
that
we
could
potentially
follow
up
on
this
with
a
different
issue.
If
we
say
that
yeah
there
is
some
urgency,
our
content
needs
to
to
start
working
on
this.
B
But
hopefully,
when
I
get
access
to
this,
I
can
just
put
in
a
figma
file
and
detail
a
bit
more.
B
B
And
add
the
ui
like
that,
you
know
you
get
the
legacy
issues
from
other
designers,
but
anyways
feel
free
to
review
that
either
now
the
proposal
an
hour
later
but
yeah.
A
We
we
can
break
it
into
two
merge
requests.
We
can
even
break
it
into
two
issues
if
we
want
to
iterate
even
smaller,
to
do
side
by
side
first
and
then
the
single
file
view,
or
vice
versa.
Okay,
whatever
the
no
you
can
configure
what
your
default
is.
I
think
I
don't
remember
now,
but
yeah
we
can.
We
can
break
that
up
if
we
want
to
yeah.
B
A
All
right
and
then
the
follow-up
vex
debt
issue.
Have
you
created
that
or
will
you
create
that.
B
B
No,
that's
it.
You
mentioned,
like
the
usability
system,
usability
score
issues
I
have
mostly
designed
and
yeah
I'm
trying
to
I'm
gonna
have
too
many
times
I'm
trying
to
find
the
link
with
our
epic
testing
usability.
B
A
A
A
Blabbering
around
so
I
started
in
get
out
of
my
way,
hopefully
you're,
seeing
our
agenda.
B
A
Okay,
so
went
from.
A
Here
into.
A
Not
that
one-
I
don't
know
anyway,
into
this
usability
of
verified
testing,
widgets
and
then
the
visibility
of
system
status
that
matches
up
with
the
quarterly
okr
for
us.
I've
just
rearranged
these
so
that
they're
by
next
milestone.
So
this
one
is
in
flight,
the
sort
metrics
report,
so
that's
just
a
sort,
there's
no
ui
change.
There's
no
design
change
on
that
is
just
sorting
the
existing
design
explain
what
coverage
means
is
a
text
and
a
tooltip
change
that
we've
already
walked
through
clarify
the
dash
icon.
A
B
A
A
Label
pile
with
awaiting
feedback
on
that
one.
A
We
might
split
out
the
license
compliance
issue
to
their
own
issues,
so
they
can
track
that
separately
because
that
isn't
going
to
close
with
us
doing
anything
in
this.
If
dash
has
already
replaced
dot
overall
system
wide,
where
we
can
open
an
mr
for
their
docs
to
explain
what
it
means,
but
they're
going
to
be
the
sme
on
that
and
if
they
want
to
change
up
the
widget
at
the
same
time
they
certainly
can
and
then
the
last
one
is
the
performance
changes
as
a
percentage.
A
A
B
The
issue
correctly,
it's
incorrect
on
how
we
display
it
right.
The
the
performance
change
in
different
parts
of
the
ui.
A
A
This
yeah,
so
we
need
to
at
some
point
sort
through
this,
but
it
isn't
scheduled
it's
in
the
backlog
right
now,
given
the
usage
on
the
browser
performance
widget,
I'm
not
inclined
to
go
in
there
and
spend
a
lot
of
time
on
this,
especially
designer
time
or
ux
time
on
this,
so
I'm
okay
with
it
being
in
the
backlog.
For
now,
the
other
two
are
higher
priority.
For
me,.
B
B
So,
what's
a
comment
about
that
to
doc,
so
this
is
lower
lower
in
your
experience.
A
And
then,
last
week,
scott
and
ricky-
and
I
discussed
in
a
couple
of
issues-
code,
quality,
widget,
cleanups,
and
so
we
have
scheduled
4
1311
in-
and
I
split
these
out
so
there's
two
issues
for
each
organizational
method
for
lack
of
a
better
term,
one
for
the
full
report,
one
for
the
mr
widget.
A
The
first
is
just
sorting
the
violations
so
they're
by
severity.
So
we'll
do
that
in
1311..
No,
no
other
change
there,
just
a
sort,
change
of
the
existing
interface
grouping,
then
things
together
and
just
doing
a
rough
grouping
first
and
then
we
can
follow
up
with
additional
ui.
If
that
grouping
doesn't
make
a
lot
of
sense
and
we
may
get
into
those
first
issues
and
realize
that
hey,
we
need
additional
ui
here,
at
which
point
we'll
just
put
a
pause
on
those
and
go
back
and
do
the
design
work
for
it.
Excuse
me.
B
B
B
It's
trying
to
recover,
so
I
think
it's
second
I'm
trying
to
understand
if
there's
anything
that
you'd
like
to
discuss
today
that
covers
ux.
So
I
can
just
look
into
the
agenda
or
add
any
topics
there.
A
The
last
thing
I
wanted
to
talk
through
was
the
ux
for
the
blocking
merge
and
that
enforce
code
coverage.
Epic.
A
Yeah,
so
we
have
two
issues
scheduled
for
14-0.
The
first
is
a
way
to
configure.
I
don't
want
to.
I
want
to
block
merge
if
test
coverage
as
a
percentage
decreases
in
an
mr
or
if
merging
it
would
decrease
it.
The
way
that
we're
going
to
work
through
that
is,
first
by
just
giving
you
a
visual
indicator
that
you
should
not
do
this
we're
going
to.
Let
you
still
merge
it
but
say
this:
this
will
decrease
your
test
coverage.
You
have
indicated
you
don't
want
to
be
able
to
do
that.
A
Then
we'll
block
that
merge
button
when
a
project
is
configured
but
we'll
still
allow
you
to
do
the
merge
from
a
quick
action.
Then
we'll
go
back
and
do
the
approvals,
so
you
can
get
someone
to
approve
it.
We're
going
to
reuse
the
interface
that
secure
has
already
built
for
that
when
it
comes
to
security
approvals,
like
my
security
team,
so
we're
just
going
to
reuse
that
entire
interface
then
we'll
just
the
back
end
work
to
block
the
quick
action.
After
that.
A
I
think
I
might
have
those
two.
No,
we
need
to
do
those
in
that
order
so
that
you
can
approve
it
and
then
you
can
finally
we'll
block
it
off
and
we
might
do
those
at
the
same
time.
So
we
want
to
allow
someone
to
work
around
this
if
they
need
to,
but
we
want
them
to
do
it
in
the
same
method
that
they
do
for
the
security
approvals.
A
So
if
you
are
fast
tracking,
a
patch
or
something
like
that-
and
you
know
that
you're
decreasing
coverage,
but
you
need
to
to
make
the
change
then
we're
gonna
give
you
that
that
workaround
and
then
after
that,
it's
hey,
we're
gonna,
have
a
target.
So
it's
not
just
a
any
decrease.
It'll,
be
a
decrease
down
to
this
like
this
is
our
floor
and
that
might
break
out
into
its
own
into
its
own
epic,
at
some
point,
but
the
where
we
need
some
ux
is
this
visual
indicator.
A
Let's
add
more
tool
tips,
but
we'll
need
something
to
give
you
that
indication
of
hey.
You
could
merge
this,
but
you
shouldn't,
and
I
don't
know
if
it
should
go
see
if
I
can
find.
A
A
I
don't
know
if
we
want
another
again.
This
is
old
interface,
so
I
don't
know
if
this
label
is
still
here.
This
is
going
to
be
here.
If
you've
selected
delete
the
branch
we
could
put
something
else
in
there,
but
that
could
start
to
be
a
lot
of
stuff
in
that
area,
but
I
don't
know
where
else
we
would
put
it.
A
B
Do
I'm
trying
to
find
the
merger
class
widget
anatomy,
I'm
not
sure
if
you've
seen
this
this
initiative
by
who
did
this
pedro?
Oh.
B
B
Anyways,
I'm
just
thinking
of
how
we
do
with
ours
today
and
and
how
we
form
users,
we
don't
use
tooltips.
We
do
change
the
color
of
the
button
right
when
it's,
for
example,
you
want
to
merge
something
add
to
the
merge
string
and
bypass
the
the
order
in
the
train
you're
able
to
do
that.
The
button
label
changes
the
the
color
of
the
label
changes
and
there
is
also
a
method
in
the
ui
that
today,
that
shows
what's
going
to
happen
pretty
much.
B
If
the
user
decides
to
go
through
that
flow
and
there's
another
I'm
trying
to
find
but
anyways
the
fedor
is
doing
some
work
around
the
merge
request
documenting
all
the
states.
B
I
don't
care
if
it's
on
mural
or
here
on
figma,
but
I
think
would
be
easy
if
we
could
just
map
that
scenario
to
some
ui
that
is
in
place
today.
We
don't
reinvent
the
wheel,
so
I'm
gonna
find
that
and
add
to
the
to
the
dock.
A
B
And
if
you
want
to
get
approval
as
a
user,
that
has
no
no
access
right
to
to
merge
that
manually
to
merge
that
in
the
ui.
Would
I
just
trigger
an
action
to
someone
else
to
do
and
then
that
merge
request
continues
in
you
know
in
standby?
B
A
I
don't
know
I
was.
I
figured
that
sorry.
This
is
why
I
figured
we
would
just
follow
what
secured
already
built,
because
they've
done
through
all
of
this,
and
we
want
to
be
consistent
with
that
experience
so
and
we're
going
to
reuse
the
same
thing
to
block
a
merge
request
on
a
code,
quality
degradation
to
say:
hey
your
code
quality
decreases
with
this
merge,
that's
not
allowed
per
the
way
the
project
is
configured
the
same
way.
You
can't
merge
if
you're,
introducing
a
security
risk
or
if
there's
security
violations
found.
A
A
A
A
So
I
think
the
next
step
would
be
for
me
to
create
a
issue
design
issue
and
assign
it
into
1311.
for
this
new
interface
that
you're
going
to
work
out
with
or
talk
to
pedro
about.
B
Yeah-
and
just
so
I
understand
correctly,
the
security
approvals
flow
is
in
place
today.
It
already
exists
right
in
a
product.
Yes,
okay,.
A
A
Cool,
well,
that's
it
for
me
today
just
to
talk
through
that
one
thing.
Otherwise
it
feels
like
things
are
moving
pretty
well
and,
like
I
said
I
want
to
slot
that
in
ahead
of
the
work
for
the
screenshots,
so
I
will
I'll
drop
this
one
into
your
epic
for
the
verify,
testing
runner
stuff,
and
I
will
swap
it
so
that
design
updates
for
unit
test
reports
falls
back
below
the
line
and
moves
out
of
1310,
okay,
okay,
I
hope
that
doesn't
cause
too
much
turn
for
you.
I'm
changing
something
out!
B
No,
it's
okay!
I
haven't
started
working
on
that
one
specifically,
so
that's
it
and
then
yeah
feel
free
to
ping
me
it's
like
once
you
update
that.
So
I
can
start
looking
into
this,
but
then
I'll
really
focus
on
wrapping
up
the
good
quality
div,
because
I
think
that's
one.
That's
been
standing
there
for
too
long
now.