►
From YouTube: Merge train visualization - design exploration
Description
Please provide your feedback on the issue: https://gitlab.com/gitlab-org/gitlab/-/issues/277391
A
Hey
everyone,
I'm
vithika,
I'm
the
product
designer
for
the
verify,
ci
siege
group
and
today
I
would
be
walking
you
all
through
some
design
explorations
that
I
have
done
for
the
merge
string,
visualization
exercise
that
was
started
sometime
back.
So
this
is
the
issue
where
this
all
began,
and
this
is
a
design
only
issue.
That
means
we
are
not
having
any
implementation
related
discussions
here.
A
So
this
here
is
what
I
have
started.
I
know
it
had
started
off
with
just
a
I
mean,
a
proposal
that
only
talked
about
having
a
visualization
for
the
train
but
somewhere
in
the
discussion
it
kind
of
evolved
into
like
the
requirement
evolved,
and
there
was
this
issue
that
was
brought
into
light,
which
was
around
merchant
index
statistics
and
summary
page,
and
I
tried
to
evaluate
like
what
is
it
that
would
provide
the
maximum
value
to
user.
A
Like
what
do
we
have
enough
information
that
we
have
to
show
to
the
user
that
we
would
need
a
dedicated
page
and
after
asking
very
difficult
questions,
it
kind
of
felt
that,
yes,
there
are
a
lot
of
information
that
linked
to
merge
trains,
and
why
not
explore
this
idea
of
dedicating
a
page
or
just
to
merge
trains
and
all
the
activities
and
information
related
to
them
all
right.
So
in
this
page,
as
you
can
see,
what
I've
done
is.
A
The
pattern
is
very
similar
to
how
we
have
the
pipeline
overview
page.
So,
for
example,
there's
a
there's
a
graph
on
the
top
which
talks
about
which
is
which
provides
a
very
visual
representation
of
what's
happening,
the
train.
So
the
kind
of
information
that
I
got
my
hands
on
with
the
help
of
the
engineers
was
that
at
one
point
of
time
we
could
have
a
maximum
of
20
merchant
pipelines
running.
A
A
Besides,
what's
going
on
with
the
active
merch
train
and
those
are
the
history
of
the
train.
That
means
what
are
the
like
previous
merge
requests
that
have
been
merged
as
a
part
of
the
stream
and
then
a
list
of
all
the
cued
merge
requests
like
beyond
this
20
items.
What
else
do
I
have
here,
which
is
waiting
to
get
added
to
the
train?
A
All
right,
so
here
is
a
representation
of
what
the
train
history
would
look
like
just
ignore
that
duplication
of
information
is
just
for
the
ease
of
creating
a
quick
ui.
I
just
kind
of
copied
and
pasted
the
rules,
but
this
is
how
it
could
look
like.
The
kind
of
information
where
we
could
show
here
is
the
status
of
the
pipeline,
which
is
the
status
of
the
motion
pipeline.
Then
a
little
information
about
the
most
trained
pipeline
itself,
like
the
id.
A
A
So
I
know
that
there's
a
little
discrepancy
with
the
kind
of
terminologies
that
I'm
using,
but
I
would
definitely
take
the
help
of
our
technical
writers
to
deal
with
this
okay.
So
this
is
the
first
page
what
it
could
look
like
now,
let's
talk
about
like
what
happens
if
users
click
on
the
second
tab
that
I
provided
here,
which
says,
queued,
merge,
requests.
A
What
they
could
do
from
here
is
they
could
either
remove
this
from
the
train
and
get
back
to
this
merge
request
and
deal
with
it
separately
or
from
here
itself.
I'm
adding
this
option
to
merge
immediately
okay,
so
these
were
the
tabs
and
the
basic
information.
That's
going
to
be
placed
here
and
I'll
quickly
also
touch
upon
this-
that
I'm
trying
to
like
give
a
reference
of
the
time
in
this
graph
in
here.
A
But
that
was
the
idea
all
right
now
talking
about
the
interactions
for
for
the
mrs,
which
are
lined
up
for
in
the
active
merge
room,
which
means
that
for
the
mrs,
for
which
there
are
four
string
pipelines
running,
there
are
certain
pieces
of
information
that
make
that
that's
very
relevant
for
users
and
those
are
like,
what's
the
for
a
way
to
better
identify
the
merge
request,
that's
linked
with
this.
So
just
the
id
you
would
not
give
them
a
pretty
good
idea.
A
A
And
apart
from
that,
another
interaction
that
I
thought
would
make
a
lot
of
senses
like
if,
if
I
have
something
in
the
train
itself
here,
I
showed
that
in
the
second
position.
But
let's
say
if
it's
in
ninth
or
tenth
position-
and
I
still
I
couldn't
afford
to
wait
as
a
user.
I
couldn't
afford
to
wait
even
for
those
few
minutes,
and
this
is
very
urgent.
It's
a
very
urgent
update
that
I
have
to
make
so
from
here
itself.
A
There
will
be
two
options
available,
merge
or
remove
much
immediately
or
remove
from
the
train,
and
what
I'm
expecting
is
like
in
workflow
wise
when
one
clicks
on
merge
immediately,
there
should
either
be
some
sort
of
like
some
confirmation
that
they
have
to
go
through,
or
maybe
a
treatment
for
this
button
that
conveys
the
urgency,
which
it
doesn't
do
right
now
yeah.
This
is
the
very
first
pass
sorry
and
one
I
was
just
playing
through
with
this
thinking
about
the
possibilities
like
what
this
craft
could
become
in
the
future.
A
What
this
visualization
could
become
in
the
future
like
what
are
interactions
that
we
couldn't
think
of
at
this
point
of
time.
Could
be
enabled
from
the
graph
itself,
so
maybe
just
maybe
that
we
can
provide
this
drag
and
adjust
interaction
here,
for
example,
the
liberty
to
change
the
sequence
like
change.
A
The
priority
of
the
train,
and
one
thing
that
would
be
linked
to
this
feature
would
be
like
only
providing
this
access
to
a
particular
role
like
like
restricting
the
access
to
this
feature,
because
otherwise
I
can
understand
that
this
could
get
really
messy,
so
maybe
only
maintainers
can
re-prioritize
train
and
so
on,
yeah.
So
that
was
it,
and
this
is
all
still
work
in
progress,
but
I'm
a
fan
of
getting
feedback
early.