►
Description
This research synthesized the feedback collected from the UX Department, between July 28 and September 8, 2020, on the current experience of the merge request (MR) page. This was done through an async critique in Figma, our UI design tool, where participants left comments on screenshots from the MR UI.
1. Read the ✨ Insights summary: https://dovetailapp.com/projects/14109fbc-dfdd-4204-a54e-9c80ba8b7bba/insights/present/01f97e1e-288e-471e-ab7f-1927ce0449a82.
2. Jump directly to the 🔗 Notes and insights per stage group: https://dovetailapp.com/projects/14109fbc-dfdd-4204-a54e-9c80ba8b7bba/insights/present/ee428c62-68b8-4c09-b60f-6c3242dde0573.
3. Comment on the issue: https://gitlab.com/gitlab-org/ux-research/-/issues/1073
A
So,
let's
start
the
walkthrough
and
I'll
share
with
you
how
all
of
that
happened.
So
this
async
critique
it
happened
between
july
and
september
of
last
year
and
was
done,
as
I
said,
in
figma
our
ui
design
tool.
Where
we
add,
we
had
a
number
of
artifacts
visual
artifacts
that
showed
the
merge,
requests
ui
and
then
asked
the
members
of
the
ux
department
to
comment
on
them.
A
A
A
Some
of
them
are
informative,
so
there's
nothing
really
actionable
that
we
can
do
today,
maybe
in
the
future
we
can
turn
these
into
epics
or
larger
initiatives
that
will
allow
them
to
tackle
them,
and
we
also
have
actionable,
which
make
up
most
of
the
insights
that
we've
created
the
best
place
to
start
digesting.
This
research
is
this
insights,
summary
page
and
also
the
notes
and
insights
per
stage
group.
A
So,
if
you're
interested
in
digging
in
directly
into
what
can
my
stage
group
do
today
to
help
the
merge
request
experience,
I
would
recommend
looking
at
the
notes
in
insights
per
stage
group,
but
also
the
insight
summary
is
a
good
place
to
start.
So,
let's
start
by
the
inside
summary,
so
we
think
that
looking
at
the
inputs
and
outputs
of
the
exercise,
we
think
it
was
a
success,
because
we
had
a
lot
of
participation
from
the
ux
department
across
the
different
disciplines
and
out
of
that
participation.
A
If
they're,
not
a
duplicate
and
so
on,
you
can
also
digest
and
look
at
the
all
of
the
comments
in
the
figma
file.
If
you
want,
if
you
need
more
information
and
contacts
about
how
this
comment
and
where
this
comment
was
made,
and
all
of
this
information
and
instructions
are
available
in
this
page,
the
notes
and
insights
per
stage
group,
everything
is
explained
here.
A
The
related
issues
that
the
ones
that
were
created
or
linked
to
can
also
be
found
inside
of
the
research
issue
of
git
lab,
where
we
have
linked
to
them
in
the
related
issues
section.
So
you
can
also
see
all
of
the
actionable
insights
here
and,
as
you
can
see,
some
of
them
already
either
done
or
they
have
a
version,
a
release
milestone,
which
is
great
now
back
to
the
inside
summary,
going
to
give
you
a
quick
walk
through
of
the
themes
and
research
goals.
A
A
We
were
assuming
that
the
merge
request
page
is
a
project
area
shared
by
many
stage
groups
and
we
believe
the
feedback
and
areas
of
improvement
are
not
directed
at
just
one
of
those
stage
groups,
but
rather
distributed
across
them.
And
if
we
look
at
the
informative
insight
that
talks
about
that,
we
can
see
that
the
stage
group
that
has
the
largest
number
of
issues
is
the
code
review
group
with
47.
A
But
if
we
remove
the
code
review
group
from
that
from
that
count,
we
can
see
that
more
than
half
of
the
identified
issues
around
50
53
are
the
responsibility
of
another
stage
group
or
a
shared
responsibility
across
state
groups,
and
you
can
see
here
verify
testing,
verify
continuous
integration,
release
and
other
other
groups.
So
this
this
finding
indicates
that
there
might
be
a
lack
of
collaboration
between
the
groups
and,
more
specifically,
there's
a
lack
of
guidance
and
oversight
of
on,
what's
being
changed
in
emr
experience.
Why
and
how?
A
The
other
important
assumption
that
we
had
was
that
there
were.
There
are
many
small
improvements
that
we
can
make
today,
but
we
just
haven't,
identified
them
or
prioritized
them
and,
as
I
showed
you
before,
you
can
browse
insights
per
stage
group
or
seed
related
issues
in
gitlab,
and
most
of
them
are
most
of
them
are
usability
ui,
polishing
ui
text
issues
also
because
of
the
nature
of
the
exercise
itself,
because
it
was
very
visual.
A
A
Another
thing
I
wanted
to
highlight
was
that
most
of
the
comments
were
related
to
the
merge
request.
Widget,
as
I
showed
you
here
in
the
figma
file,
you
can
see
the
huge
amount
of
comments
across
all
of
the
different
widgets,
specifically
the
merge
widget,
which
shows
the
actions
and
information
related
to
merging
the
mr.
A
A
And
you
can
see
that's
highlighted
here
as
well.
The
merge
request
widget
compared
to
the
other
areas
of
gitlab,
had
much
more
comments,
and
it's
also
the
area
of
the
merge
request
that
has
the
most
amount
of
overlap
with
the
different
stage
groups,
so
it.
I
think
this
is
a
good,
a
fairly
interesting
correlation
between
the
overlap
of
stage
groups
and
the
amount
of
comments
that
we
had,
and
you
can
see
here.
A
A
lot
of
them
are
not
something
that
can
be
easily
solved
through
specific
small
issues,
but
rather
things
that
we
need
to
take
a
more
a
more
holistic
approach
and
these
prevailing
issues,
things
that
we
can
we
see,
are
happening
over
and
over
again
in
the
merge
request.
Experience
specifically
in
the
merge
requests
widget
because
of
the
overlap
of
stage
groups.