►
Description
The System Usability Scale is a quarterly initiative that helps us understand the needs, challenges, and pain points of GitLab users.
In this series, Katherine Okpara (UX Researcher, Create) will discuss the top themes we’ve gathered from the SUS surveys conducted thus far and highlight opportunities for improvement.
Learn more about the insights and action items from the SUS here: https://gitlab.com/gitlab-org/gitlab/-/issues/228906
A
The
users
often
share
that
they'd
like
to
see
more
polish
and
consistency
in
the
ui,
and
there
are
various
product
behaviors
that
do
not
match
user
expectations,
especially
when
they've
transitioned
to
gitlab
from
competitor
tools
oftentimes.
We
have
an
explicit
reason
for
why
a
pattern
is
inconsistent
or
unexpected
in
gitlab.
A
A
One
example
of
that
would
be
removing
a
label
from
an
issue,
so
in
order
to
remove
a
label
from
an
issue,
the
user
needs
to
click
on
this
edit
link
scroll
down,
see
if
they
can
find
anything
decide
to
type
in
the
label.
They'd
like
to
remove
so
in
this
case
I
would
put
auto
updated
so
once
you
find
the
label
in
the
search
results,
you
need
to
click
on
it
and
then
you
need
to
click
away
to
remove
the
label.
A
So
this
interaction
requires
quite
a
few
clicks
and
steps
to
get
to
that
final
point
of
removing
the
label,
which
can
be
surprising
if
you
come
from
other
platforms,
where
you're
able
to
simply
click
on
an
x
to
make
the
label
go
away.
So
we
do
have
an
open
proposal
to
improve
this
behavior
by
making
changes
to
the
interaction.
A
Another
usability
issue
is
the
behavior
of
the
assignee
drop-down,
and
so
the
problem
here
is
that,
if
you're
searching
for
a
particular
user
to
assign
this
issue
to-
and
this
menu
will
only
start
to
show
relevant
results
after
you've
typed
a
minimum
of
three
characters.
If
I
was
looking
to
sign
this
issue
to
get
lab
bot,
I
would
have
to
type
in
g.
A
A
Additionally,
there
is
a
lack
of
visual
cue
that
explains
that
a
user
needs
to
continue
to
type
results
in
order
to
get
the
right
person.
So
here
it
just
says
no
matching
results
which
can
be
confusing
if
you're
not
as
familiar
with
this
interface.
So
if
a
user
does
not
continue
to
type,
it
will
appear
as
if
no
results
are
available,
so
we
do
have
several
open
issues
related
to
this
point.
A
So
before
I
even
type
in
anything,
it
shows
me
a
list
of
some
of
the
possible
places.
I
can
move
this
issue,
but
it
doesn't
have
any
particular
nesting
or
hierarchy
that
demonstrates
to
me
the
significance
of
these
options.
The
lists
the
lists
are
often
unordered,
so
it's
not
easy
to
tell
which
of
these
results
may
be
most
relevant
to
the
projects
that
you
tend
to
work
with
in
your
day-to-day
work
or
the
ones
that
you
personally
have
created
or
the
ones
that
your
teams
have
created.
A
And
another
example
of
this
is
again
in
the
settings.
If
you
go
to
settings
general
merge,
request
approvals
and
you
try
to
click
to
add
an
approval
rule.
You
can
search
for
users
or
groups
and,
as
you
click
into
this
drop
down,
you're
immediately
met
with
a
list
of
different
groups
that
you
could
potentially
select
approvers
from.
A
However,
they're
not
organized
in
a
certain
fashion,
so
it
can
be
difficult
to
understand
why
these
groups
are
being
shown
to
you
and
whether
these
groups
contain
the
people
that
you
need.
You
are
able
to
start
searching
for
a
certain
group.
So
in
this
case
I
want
to
search
for
senior
developers,
because
I
know
that
I
have
a
group
name
senior
developers,
but
it
took
me
typing
out
the
whole
name
in
order
to
get
this
group
to
pop
up.
And
if
you
look
previously,
this
group
was
nowhere
to
be
found
in
the
list.