►
From YouTube: Admin Runner table new list design proposal
Description
Gina Doyle (Product Designer: Runner & Pipeline Insights) walks through the new proposed list design for the Admin Runners view.
Issue referenced: https://gitlab.com/gitlab-org/gitlab/-/issues/343133/
A
A
A
If
we
want
to
do
that,
so
what
I've
been
working
on
is
trying
to
do
exactly
that
and
I've
been
trying
to
recreate
what
we
have
today
so
still
using
the
same
data.
But
you
can
see
that
one
thing
I'm
bringing
in
is
owner,
which
is
something
that
we
didn't,
or
we
don't
show
today
and
to
give
you
context
around
what
that
means.
A
When
you
have
a
specific
runner,
you
can
have
multiple
projects
that
are
associated
with
that,
which
means
it's
assigned
to
those
projects
and
those
projects
can
use
that
runner
to
run
jobs,
but
there's
always
the
original
project
that
was
attached
to
that
runner.
Who
is
the
owner?
In
that
case,
an
owner
is
different
from
the
person
who
created
the
runner.
So
I
could
create
the
runner
and
I
attach
it
to
my
project
a
and
then
I
share
it
with
b
c
and
d,
and
at
that
point
a
is
the
owner
and
I'm
the
creator.
A
A
The
icon
that
I
need
to
create
is
an
upgrade
icon,
because
we
don't
have
one
for
that
today,
I'm
using
the
up
arrow
just
because
usually
what
I
see
is
an
up
arrow
with
like
a
circle
anyways
I've
translated
a
lot
of
the
other
metadata
that
we
had,
like.
I
p
address
jobs
like
the
number
of
jobs
that
this
runner
has
run
and
the
last
contacted
I've
translated
all
those
into
icons
and
then
for
the
other
metadata,
like
the
description,
the
version
when
it
was
created
and
who
created
it.
A
I've
kind
of
combined
that
all
here,
using
these
little
dots
to
separate
it,
and
I
stole
that
from.
I
think
we
use
that
in
issues
in
the
issue
list.
I
believe
so.
I
would
appreciate
any
feedback
that
you
have
around
the
design
of
this.
I
think
that
this
will
definitely
make
it
easier
to
combine
or
continue
to
add
data
if
we
want
to
to
the
table,
but
now
that
we
don't
have
to
rely
on
the
multiple
columns
breaking
responsively.