►
From YouTube: PD UX recommendations for Merge Requests
A
A
All
right,
so
here
we
are
in
the
in
the
in
the
mural
board.
What
we've
done
so
far,
or
at
least
the
preparations
which
have
done
the
same
with
ci,
which
was
pretty
successful,
white
boarding
session
is
basically
we
place
these
on
here
and
we
review
each
one
of
them.
Give
little
stickers
like
hey.
Does
this
need
a
lot
of
design
work
or
just
a
small
amount?
This
is
the
validation
you
know
to
give
a
little
bit
extra
context
towards
the
you
know
the
feasibility
of
it.
A
A
A
B
B
B
B
B
A
A
A
A
Yeah
this
is,
this
is
a
badly
written
issue
and
it's
very
opinionated
about
its
solution
without
describing
the
problem,
I
would
say
it
is,
though
I
put
it
in
the
table,
just
as
it
was
related
towards
merch
quest
and,
like
hey,
wanted
to
get
your
opinion
on
like
how
much
of
an
you
know
over
me.
Do
you
suggest
this?
This
is
like.
I
personally
would
put
this.
A
A
A
A
A
B
A
Yeah
I
personally
personally
like
from
my
my
like
my
personal
perspective.
I
would
not
always
say
like
that
is
the
only
like.
That's
one
side
of
the
problem
space.
The
other
side
of
the
problem
space
is
like.
Did
this
pipeline?
Have
a
review
app
at
all
or
not
like?
Is
there
something
to
review
here
in
a
review
app,
or
does
this
pipeline
not
create
a
review
app
at
all
like
there's,
there's
no
trace
of
it
being
being
there
so
to
say.
B
A
To
the
logs,
like,
I
think,
if
we're
gonna
make
review
apps
available,
for
example,
community
members
to
be
able
to
click
in
and
play
around,
you
know
those
kind
of
things,
then,
for
those
less
involved,
I
mean
this
is
from
like
community
contribution
perspective
right,
open
source
user.
They
will
not
immediately
go
towards
any
logs,
like
they
just
say
like
hey,
is
there
something
or
is
there
something?
A
A
B
A
B
B
B
A
A
A
A
B
B
A
A
B
A
A
The
review
app
has,
of
course,
so
here
in
this
case
right
we're
looking
at
somebody's
like.
We
want
to
see
if
this
had
a
review
app,
because
that
is
clearly
where
we're
stating
but
there's
no
way
of
us,
knowing
that
there
was
a
review
app
in
this
merch
quest.
That
is
kind
of
what
the
other
issue
is
pointing
at
in
terms
of
like
trying
to
solve.
For
this
use
case.
A
A
A
Inside
artifacts
yeah-
and
they
are
so
we
kind
of
validated
these
are
indeed
the
most
important
ones
and
high
on
feasibility.
So
I
would
say
this
is
kind
of
like
a
success
in
that
sense,
in
terms
of
like
the
like
ultimate
deliverable,
we
want
to
see
from
the
ux
perspective,
for
these
issues
like
similar
to
james
here.
B
A
B
B
A
B
A
B
B
B
A
A
A
A
A
B
So
that's
why
I'm
saying
q3,
because
we
are
focused
now
around
advanced
deployments
and
and
the
post
monitoring
issue
and
getting
feature
flags
out
so
so
review
apps
is
off
context.
The
first
one
that
I
think
we
would
probably
do
is
the
bug
the
p2
bug,
because
we're
also
focused
on
getting
rid
of
them,
so
that
would
be
higher
than
any
p3
bug
that
we
have,
regardless
of
the
category.
B
A
A
A
Yeah
there
were
a
lot
more
issues
and
tao
had
to
go
to
another
meeting
in
the
end,
and
then
I
went
with
fitika.
We
took
our
time
as
well.
You
know
to
get
a
little
bit
of
more
of
an
insight
into
you
know
why
this
is
an
issue
or
why
not
and
how
it
relates
to
current
ui
and
those
kind
of
things.
So
it
was
a
fun
fun
experience
as
well
and
exercise
to
do
anyway.
Thank
you
for
your
time
and
then
I'll.
Let
you
go
and
then
we
speak.
I
think
later
today.