►
Description
UX Scorecard Issue: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1692
--------------
A
Hello,
welcome
to
this
walkthrough
of
the
ux
scorecard
for
source
code
track
project
changes.
My
name
is
tim
noah,
I'm
a
senior
product
designer
in
the
fulfillment
license
team.
This
evaluation
is
in
partnership
with
the
source
code
group
and
mike
nichols.
Who
is
the
group
product
design
expert,
so
I'll
start
off
with
the
job
to
be
done
statement
when
changes
are
introduced
into
my
project.
A
My
manager
has
also
given
me
some
useful
information,
the
the
page
that
has
the
bugs
is
located
inside
of
the
public,
folder
and
inside
of
the
scorecard.html
file.
My
manager
has
also
given
me
some
more
information
about
how
changes
are
done
to
this
file.
They
are
always
done
through
the
branch
scorecard.
So
that's
some
useful
bits
of
information
to
take
with
me
as
I
go
into
this
task.
A
A
There's
a
lot
of
information
here
and
at
this
point
as
I'm
new
to
the
product
and
to
emphasize
I'm
new,
I'm
a
new
developer
on
the
team
doesn't
necessarily
mean
that
I'm
using
gitlab
for
the
first
time,
but
I
am
new
to
this
potentially
new
to
this
organization.
So
I'm
I'm
gonna,
put
my
hat
on
and
be
as
empathetic
as
I
can
be
to
a
new
team
member
and
I'm
assuming
that
they
they
are
also
fairly
new
to
gitlab.
A
So
I'm
looking
around
at
this-
and
I
see
that
there's
lots
of
information
here,
there's
things
that
I
immediately
want
to
dive
in
and
start
investigating,
namely
the
the
repo
and
the
files.
There
is
also
a
readme
that
has
some
more
information
and,
interestingly,
I
can
see
that
there
is
a
a
pipeline,
a
github
ci
pipeline
that
is
running.
A
A
So
let's
see-
and
I
can
hover
over-
and
it
gives
me
a
tooltip,
but
I
like
the
fact
that
I
can
hover
over
and
I
know
exactly
where
my
cursor
is
at
all
times
and
here's
that
file
that
I
need
to
investigate.
So
let
me
click
into
it.
I'm
not
sure
why
there's
a
tooltip
that
is
giving
me
the
same
information
that
I
can
see
on
the
on
the
screen,
but
nevertheless-
and
this.
A
Okay,
so
this
is
clear
I
do
like
the
theme.
It's
very
you
know
easy
to
read
and
to
understand.
I
can
see
where
the
two
bugs
are
on
the
screen
and
and
now
that
I
feel
a
little
bit
more
confident
with
the
ui.
I
think
the
patterns
are
making
sense
to
me,
even
though
that
there
are
a
lot
of
things
here
that
I
may
not
actually
need
right
now.
They
all
seem
to
be
in
their
correct
and
proper
place.
A
Spacing
and
hierarchy
seems
to
be
working
quite
well
and
I'm
not
overwhelmed
with
what
I'm
seeing
on
the
screen
so
far,
it'll
be
interesting
to
see
what
that
main
is
at
the
top.
I
think
that's
the
that
has
to
be
the
the
branch
and
okay.
So
the
next
thing
that
I
in
my
exploring
phase,
because
I'm
new
to
the
team,
I'm
exploring
the
the
project,
I'm
gonna.
A
A
It
makes
sense
to
me
to
now
jump
into
editor,
because
I
don't
really
want
to
see
past
pipelines
that
have
run.
I
want
to
see
what
exactly
is
inside
the
pipeline
in
this
project,
because
who
knows?
Does
it
contain
something
that
alters
the
code
on
commits
or
does
it
contain
something
that
runs
or
automatically
merges
a
branch
into
another
branch?
You.
B
A
A
I
was
not
expecting
that
at
all
there's
a
lot
to
read
there
and
I
feel
compelled
to
read
it
because
it's
there
and
there's
you
know
it's.
It's
very
bold
we're
not
very
bold,
but
it's.
You
know
it's
quite
dominating
on
the
page,
there's
like
a
an
elevation
hover
shadow
going
on
there,
so
it
feels
quite
like
it
feels
like
it's
really
important.
A
But,
as
I
read
through
the
information,
I'm
not
sure
it's
as
important
as
I
think
it
is,
and
it's
not
really
relevant
to
what
my
task
is
in
terms
of
investigating
this
project
and
finding
out
when
changes
were
made,
so
at
least
it
doesn't
cover
up.
What's
inside
of
the
editor,
I
can
see
that
you
know
it's
a
very
simple
pipeline
that
will
deploy
a
certain
path
which
is
which
is
cool,
but
the
the
readme
was
correct.
A
B
A
Now
I
understand
what
the
zero
means:
it
means
that
there
are
zero
open,
I'm
assuming
merge
requests,
and
it's
asking
me
whether
or
not
I
want
to
start
a
new
merge
request
and
I
just
want
to
investigate.
What's
done,
what's
been
previously
done,
what's
been
previously
worked
on,
so
I'm
going
to
click
into
the
merged
tab
and
I'm
immediately
presented
with
four
merchandise
and.
B
A
A
But
one
thing
that
I
I
still
am
concerned
about
is
the
fact
that
all
of
the
all
of
the
the
dates
are
still
relative
and
I'm
gonna
need
to
quickly
be
able
to
assess
when
the
change
was
made
and
relative
dates
are
just
not
helpful
for
me.
So
at
this
point
actually
I'm
going
to
see
if
I
can
investigate
how
to
change
the
dates
if
possible.
A
A
Would
help
if
I
could
spell
timestamp,
that's
not
really
bringing
up
anything
that
I
can
use,
maybe
relative
time,
okay,
so,
relative
time
I
can
see
something
here
time
preferences
under
profile
preferences.
I
think
this
is
exactly
what
I
need,
so
I'm
at
this
point.
I'm
quite
I'm
quite
happy.
It
didn't
take
me
too
long.
Although
you
know
I
could
have
probably
searched
a
few
search
terms
and
maybe
not
have
found
this.
So
maybe
there
could
be
some
refinements
to
to
some
some
keywords.
A
I
suppose,
to
help
find
this
setting,
because
I
think
it
could
be
quite
useful
for
people
specifically
tasked
with
tracking
down
changes.
So
I'm
going
to
click
in
there
and
I'm
going
to
see
that
I
okay.
If
I
go
into
my
preferences
and
I
go
into
time
preferences,
there's
a
use
relative
times
option
that
I
can
maybe
turn
on
or
turn
off,
probably
turn
off.
A
A
Okay,
so
at
the
moment,
use
relative
times
is
is
checked,
so
I
suppose
I
should
just
check
that
off
now.
What
do
I
do?
Okay,
so
save
is
right
at
the
bottom.
That
could
be
quite
that
could
be
missed.
You
know,
if
I
just
I
don't
know
whether
or
not
I
have
actually
accomplished
anything
from
an
interaction
standpoint.
I
think
that's
something
to
investigate
here.
I
may
miss
this
save
changes
and
think
to
myself
that
everything
happens
in
real
time,
almost
like
on
the
mac,
where
there
is
no
ok
button.
A
So
that's
interesting
and
maybe
actually
a
radio
would
work
better
here,
because
I'm
turning
something
off,
but
it
doesn't
give
me
any
indication
or
affordance
as
to
what
I'm
turning
on
so
maybe
there's
a
refinement.
We
can
do
with
this
relative
times
check
box,
maybe
turn
it
into
a
radio
between
two
options:
relative
time
and
absolute
time
for
use
of
a
better
term.
So
anyway,
I'm
going
to
save
those
changes,
and
I'm
going
to.
A
A
I'm
ordering
by
merge
date,
I
think
what
usually
is
displayed
is
last
updated,
but
for
the
purposes
of
my
task
I
really
need
to
see
when
something
was
merged.
Last
updated
could
be.
You
know
when
someone
left
a
comment,
or
you
know
something
was
checked.
Something
other
was
changed
within
the
merge
request.
A
For
me,
it's
most
important
to
see
when
something
was
deployed
when
something
was
changed
when
it
was
committed
or
merged
rather
and
toggling.
The
merge,
I
think,
is
really
important
now
the
sort,
I
think
the
sorting
could
be
a
lot
better
here,
because
I
want
to
see
the
most
recent
at
the
top
and
the
the
oldest
at
the
bottom.
B
A
A
So
I'm
looking
at
four
merge
requests
and
what
I
really
want
to
do
is
investigate
each
one
of
them
individually
to
just
really
ascertain
what
they
contain
and
whether
I
can
deduce
what
has
happened.
So
I'm
going
to
open
the
first
one
in
a
new
window
and
I
load
it
up
and
what's
really
helpful
is
now
all
of
the
dates
are.
You
know
I
can
see
all
of
them
in
absolute
in
there.
You.
B
A
And
they're,
probably
in
their
full
format,
I
can
see
that
this
was
a
a
branch
called
scorecard
example
03
that
was
merged
into
scorecard,
so
this
wouldn't
have
gone
live
because
I
know
that
scorecard
would
need
to
be
merged
into
master.
But
it's
still
interesting
to
see
that
this
change
was
merged
by
mike
nichols
at
8,
40
48.
A
B
A
Actually
see
those
changes,
what
was
actually
merged
in
so
I
can
I'm
clicking
on
the
the
tab
at
the
top
here
to
navigate
to
see
what
has
changed,
and
if
I
put
the
hat
on
of
a
a
new
member
of
the
team,
a
developer
that
is
looking
at
this
for
the
first
time.
This
all
seems
really
really
clear.
I
think
this
works
really
well.
The
the
segregation
of
overview
commits
and
changes
you
can
compartmentalize
exactly
where
you
are
on
a
merger
quest.
I
think
that
works
really
well
for
a
user.
A
The
one
thing
that
would
be
really
useful
would
be
on
this
page
on
the
list
of
merge,
merge
requests.
It
would
be
really
useful
to
see
if
there
was
a
way
of
saying
it,
what
branch
merged
into
what
branch.
So
it
would
be
really
useful
at
this
stage
to
see
if
source
code
when
source
code
was
merged
into
into
master,
because
I'm
assuming
that
this
is
what
happens
in
this
merge
request,
because
I
can
see
that
master
is
the
target
branch.
A
B
A
A
But
now
I've
opened
the
the
second
merge
request
and
I
still
don't
think
that
there's
anything
else
that
I
really
need
at
this
point.
I
don't
think
I
need
to
go
into
the
repo
again
to
look
at
any
files.
I
think
I
can
find
exactly
what
has
changed
in
through
going
through.
All
of
these
merge
requests,
so
I
can
see
that
there
are
14
commits,
and
I
can
see
that
seven
and
three
are
here.
A
Maybe
a
text
editor
for
easy
reference,
maybe
along
with
the
url
for
use
later
at
a
later
date.
When
I
need
to
document
all
of
this-
and
here
you
can
see
that
scorecard
has
been
merged
into
master,
which
is
really
important,
because
that's
what
my
manager
told
me
is
that
scorecard
always
gets
merged
into
master.
A
So
I
can
see
this
is
exactly
when
the
the
the
bug
was
or
the
bugs
rather
were
first
introduced
and
that's
interesting,
because
we
still
have
two
two
other
emerge
requests.
So
I'm
going
to
leave
this
merge
request
open
because
I
really
want
to
go
back
and
investigate
what
the
other
two
merge
requests
are,
what
they
have
in
store
for
me
to
to
find
out.
So
I'm
going
to
click
into
this
reverb.
Merge
branch
store
card
into
master,
so
I
can
see
that
this
was
a.
A
A
A
A
A
A
B
B
A
I've
been
able
to
detect
when
the
the
bugs
were
first
introduced
and
I've
also
been
able
to
detect
when
they
were
removed
and
then
when
they
were
added
all
by
going
through
the
merge
request
list-
and
this
was
all
helped
by
the
fact
that
there
are
only
four
merge
requests.
So
this
you
know,
the
merge
request
list
feature
really
does
help
in
just
going
through
sequentially.
It
does.
A
But
it's
highly
effective
because
you
have
a
pattern
of
what
you're
looking
for
each
page
is
the
same.
The
templates
are
the
same
and
you're
expecting
the
same
thing
as
you're
going
through.
So
I
was
definitely
most
happy
when
the
dates
were
changed
and
I
could
really
start
digging
into
some
of
these
numbers
some
of
the
times,
and
that
was
a
real,
a
real
help.