►
Description
Jackie, Rayana, and Lorie discuss the design direction of the CI/CD Director Dashboard.
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/199739
A
A
B
Yeah
we
have
this
this
pigment
project
with
pretty
much
all
design
information
that
we
collected
so
far
for
the
CIC
dashboards
and
like
what
Jackie
mentioned
when
we
look
at
the
meeting
a
little
bit
more
and
we
look
at
the
jobs
to
be
done
for
the
dashboards
I.
Think
one
of
my
main
questions
is:
how
far
do
we
want
to
go
with
the
customization
and
what
are
the
opportunities
that
we
can
already
identify
for
the
CIT
dashboard?
B
That's
one
already
exists
in
different
dashboards
that
we
can
incorporate
easily,
depending
on
New
York's,
patron
components
etc,
and
to
which
of
this
extra
functionalities.
Can
we
build
committee
right
on
right
when
I
look
at?
Let
me
just
change
the
view
here
when
I
look
at
this
different
dashboards
and
these
different
views
that
we
have
across
it
lab.
B
We
have
different
ways
to
display
and
consume
the
data,
and
that's
one
of
the
things
I
will
discussing
with
Nadia
last
week.
Is
that
do
we
have
like
user
insights,
or
you
know,
numbers
around
adoption
and
how
users
are
interacting
with
these
dashboards,
because
right
now
what
I
found
from
my
from
this
discovery
from
this
design
exploration?
That's
what
I
try
to
do
here.
B
Looking
at
those
three
main
dashboard
views
that
we
have
at
the
group
level
is
that
they
really
provide
different
context,
of
course,
in
different,
but
also
that
you
interact
with
them
completely
differently
and
I.
Think
that's
going
to
be
important
for
us
to,
of
course,
align
with
other
designers,
but
also
to
decide
which
that
actually
wants
you
to
choose
to
standardize
our
dashboard
views.
A
Okay,
so
this
is
super
helpful
for
me:
I'm
gonna,
paying
John
Mason
inside
of
the
GE,
managed
analytics
channel
and
I
see
see.
Do
you
want
it
so
that
we
can
see
if
there's
any
data
on
this
I
think
this
is
a
little
overwhelming
for
me,
insofar
as
my
initial
gut
and
my
initial
priority,
the
thing
I'm
trying
is
the
pain.
A
Customers
are
feeling
when
they're
managing
things
across
a
group
so
when
they
have
multiple
projects
and
they're
trying
to
get
each
of
the
project
level
metrics
just
a
step
higher,
so
that
the
immediate
pain
that
I'm
trying
to
triage
is
is
a
global
pain
and
all
of
these
like
little
pieces
that
we're
looking
at
are
very
user.
Centric
focuses
so
I'm
trying
to
get
my
head
out
of
that
global
pain
of
like
solving
by
giving
them
just
the
visibility
across
multiple
projects
and
get
into
this
to
this
granular
perspective.
A
So
at
my
past
life
users
always
told
me
that
the
actionability
of
a
of
a
dashboard
was
that
they
wanted
to
be
able
to
click
on
a
particular
data
point.
They
wanted
to
drill
into
it
and
then
the
second
priority
was
to
write
and
the
second
priority
was
to
filter
the
subset,
not
necessarily
order,
but
filter,
so
restrict
my
view
by
three
dimensions:
time
container,
which
is
a
generic
term
for
project.
In
this
case
it
could
be
a
person.
A
A
B
Angry
to
solve,
and
that's
why,
while
I
was
especially
when
I'm
working
with
UI
I
had
to
that's
the
way,
I
feel
now
that
we
have
to
make
it
conscious
decisions
about
which
direction
that
we
want
a
week,
and
it
would
be
ideal
if
you
could
do
that
at
this
point
right
because,
for
example,
there
are
when
I
look
at
especially
this
version.
This
is
the
group
analytics
words.
They
really
just
spit
the
grass
on
the
page
right.
B
That's
I'm,
gonna
show
the
proposals
that
I
put
here
and
what
I
learned
by
navigating
through
all
these
dashboards
is
that
yeah.
That
definitely
looks
like
the
low-hanging
fruits,
but
I
want
to
open,
like
the
conversation
for
how
much
effort
would
it
be
to,
instead
of
putting
all
this
dis
data
points
and
work
on
all
these
graphs
components
that
we
don't
have
yet
on
pajamas.
B
B
Okay,
you
know
so
yeah
because
I
see
a
lot
of
other
designers,
for
example,
doing
experimentation
and
in
principle,
when
you
look
at
security,
dashboard,
I'm
sure
if
you're
super
familiar
with
this
stage
of
this,
this
dashboard
lordy
and
you
participated
from
research.
But
when
I
look
at
it,
I
know
that
this
is
new,
look
and
feel
right.
I'm
not
talking
about
the
looking
few,
isn't
you
and
you
can
see
the
differences
in
UI
compared
to
these
dashboards?
B
Think
that's
also
where,
when
I
think
about
how
we're
gonna
implement
this
is
that
we
need
to
be
a
little
bit
careful
so
that
engineers
can
yeah
use
the
right
components
and
that,
if
we
decide
to,
for
example,
move
from
a
view
that
just
resembles
days
where
you
see
one
metric
at
a
time
right,
because
here
you
go
to
this
drop-down
select
any
change
in
the
whole
view
versus
beauty
and
dashboards.
Well
effort
would
that
be
in
the
future.
If
you
want
to
be
something
like
that
from
the
beginning,
so
we.
C
I:
yes,
yes,
because
just
giving
them
the
analytics
is
like
okay
wow.
This
is
great,
but
I
need
to
do
stuff
with
this
thing,
I
need
to
dive
into
it.
I
need
to
export
that
out
and
give
it
to
somebody
else,
but
create
another
dashboard
from
that
dashboard
and
give
it
to
my
CEO,
like
there's
interactions
that
they
have
to
do,
and
if
we
don't
give
that
to
them,
the
adoption
won't
be
there
well.
A
There's
a
difference
between
reporting
and
analytics.
So
what
you're?
Seeing
in
the
previous
the
issue
page
count?
That's
a
report.
There
isn't
anything
packaged
that
tells
you
what
to
consume.
The
you
stream
analytics,
though,
says
hey.
This
is
your
cycle
time.
This
is
your
consumption
and
it
gives
you
a
benchmark
to
then
act
from
within.
So
that's
what
we
want
to.
We
want
to
package
our
data
and
we
want
to
make
it
consumable.
A
So
that's
the
biggest
difference,
I
think
that
you'll
see
with
our
see
ACD
dashboard
and
the
other
reports
that
people
are
generating,
because
people
are
generating
reports
that
even
the
security
thing
that
that
other
dashboard
is
just
a
report
of
you,
because
it
doesn't
show
you
I
mean
I.
Actually,
this
vulnerabilities
over
time
is
its
own
little
dashboard
where
you
have
severity
and
then
the
growth
over
time
so,
like
that's,
a
mini
dashboard
inside
this
greater
dashboard.
A
C
B
A
What's
giving
me
the
heartburn
right
now
is
that
I
want
to
say
yes,
Hana
will
implement
every
pajamas
component
thing
that
we
can,
knowing
that
the
problem
that
they're
gonna
be
solved.
The
problem
that
were
going
to
solve
with
CIC
word
Ethan,
if
it's
ugly,
as
sin
will
be
amazing,
right,
it'll,
be
so
valuable
for
them
to
be
able
to
see
those
insights,
even
though
it
doesn't
matter
our
style.
Mm-Hmm.
B
B
Of
your
assets,
because
then
it's
well
I
have
a
lot
of
questions.
You
see.
My
post-its
here.
I
also
discussed
this
briefly
with
Nadia
last
week
and
I
think
my
main
question
right
now
is
actually
related
to
today's
points.
Let
me
see
if
it
ends
I
mean
to
what
I
wrote
here
in
looking
at
the
pajamas
components,
as
you
mentioned
just
now,
that
yeah
building,
more
pajamas
components,
etc.
I
think
this
is
not
really
the
problem
for
us,
because
there
are
enough
graphs.
B
There
are
enough
kinetic
components,
navigation,
components
whatever
if
we're
gonna
fix
them
to
make
them
look
nice,
that's
a
different
discussion,
but
I
think
we
should
spend
a
bit
of
time
discussing
in
deciding
which
graphs
we're
gonna
use.
For
you
know
each
metric
because
I
that's
one
of
the
things
I
don't
see
documented
anywhere
in
pajamas,
and
we
know
that
when
you
choose
the
wrong
interface
and
the
wrong
graph,
then
people
cannot
consume
the
data
correctly.
So.
A
A
You
should
have
two
lines:
one:
that's
the
projects
that
are
open
and
active
versus
releases
that
are
open
and
active,
because
then
you're,
comparing
the
two
and
you
get
to
see
the
relationships
and
if
you
notice
that
one
of
your
projects
has
a
whole
lot
of
releases
because
they're
implementing
C
D
versus
another
project
that
doesn't
have
any
releases
because
they're
not
doing
CD
they're
only
releasing
quarterly
whatever
it
is.
Then
you
can
compare
that
at
glance.
A
B
B
Here
but
I
think
it's
also
best
if
other
people
can
access
the
information
there
and
that's
that's
a
great
point,
because
we
can
look
at
the
metrics
that
we
want
to
display.
Comparing
then
linking
that
to
the
components
that
we
already
identified
and
see,
these
components
will
be
used
to
show
this
specific
type
of
them.
You
know
why,
because
there
are
so
many
options
and
that's
what
I
was
impressed
when
I
did
that,
try
and
look
at
pajamas
I
thought.
A
B
A
We
shouldn't
do
that,
because
the
design,
experience
and
seamlessness
of
this
persona
is
going
to
be
impacted
by
the
way
that
they
feel
when
they're
toggling
between
dashboards
and
although
I
know
that
my
product
manager
side
is
like
now.
I
want
to
build
more
cool
things.
So
we
need
to
keep
that
in
check
and
if
there's
a
way
that
we
can
identify
these
UI
polish
UX
debt.
Prioritize
importantly,
we'll
do
that
now.
B
B
So
let
me
quickly
go
over
these
three
prototypes
that
are
slightly
different
and
also
based
on
the
screens
that
we
saw
for
the
analytics
the
security
of
the
group
dashboards.
So
this
one
is
build
on
top
of
the
analytics.
You
know
so
many
and
indeed
show
us
all
the
information
Jackie
Jackie
like
what
your
your
luffa
deliberate,
iPad
and
then
a
couple
of
thoughts,
also
based
on
my
experience.
B
Looking
at
the
current
product.
Some
concerns
on
this
I'm
gonna
start
with
a
concerns
with
us.
Why
not
loading
time
is
awful.
It's
so
bad
when
you
have
this
huge
dashboards
and
security
dashboards
like
a
hundred
of
lines
in
a
table
once
you're
logged
in
what's
your
landing
Paige.
So
that's
one
of
the
things
for
us
to
consider
that
the
more
data
you
displayed
here,
the
heavier
this
thing
will
get
and
I.
Think
that's
also
important
for
us
to
consider
like
what
you
mentioned.
Leaving
people
they
have.
B
A
A
Maybe
the
latency
is
also
not
real-time.
Maybe
it
gets
updated
and
then
it's
just
stagnant
initially
until
we
can
figure
out
like
what's
the
right
refresh
rate
and
then,
of
course
we
can
add,
we
can
say
that
it
doesn't
refresh
and
then
you
have
to
manually
refresh
it
which
would
allow
us
to
you
know,
have
a
static
dashboard
that
gets
manually
refreshed.
We
that
might
be
an
option
too.
So
I'd
love,
I
love
it
that's.
What
you're
thinking
we'll
have
crabs?
B
Be
awesome
to
know
what
were
the
possibilities
there,
because
when
I
looked
at
this,
this
viewer
I
think
I,
just
yeah
put
some
UI
elements
here,
based
on,
as
I
said,
your
prototypes,
but
also
things
that
we
already
have
in
UI,
so
historical
versus
upcoming
release.
We
do
have
this
type
of
bar
graph
with
the
comparison,
so
that
will
be
super
cool.
These.
We
also
have
components
for
like
this.
Just
one
data
points
they
call
like
a
text
graph,
the
novel
and
here
for
pipelines.
B
I
was
thinking
that,
since
you
want
to
see
display
the
last
five
pass
us
by
fail
pipelines,
I
love
that
person
to
me.
Similarly,
like
you,
I
write
the
same
language
that
you
have
on
other
pages
here.
So
here's
just
a
screenshot
I
didn't
polish
anything,
but
I
was
wondering
what
information
is
actually
relevant
here.
What
what
ready?
Let
it
regularity
we
want
to
display,
but
also
what
actions
the
user
we
want
to
take.
From
this
view,
yeah.
A
So
from
the
pipeline
view,
people
typically
want
to
drill
into
the
project
from
that
view,
so
we'll
want
an
easy
way
to
like
see
the
project
and
click
into
it
and
take
it
to
you
that
job
people
want
to
be
able
to
see
like
where
are
these
pipelines
have
failed?
Some
more
like
on
the
failed
pipeline
side
which
jobs
they
fail
out.
B
And
that's
exactly
the
second
point
here
where
we
want
to
take
users
because
yeah
we
can
take
them
to
all
these
different
pages
right,
because
here
you
quickly
specifically
in
this
I'll
just
go
to
the
committee
and
then
you
go
to
user
profile,
but
I
think
would
be
nice
for
us
to
have
that
connection
between
departments
dashboards.
So
once
we
polish
that
view
we
have
a
single
story
line.
Yes,
there.
B
Was
a
first
question
and
again
it's
Murli
based
on
the
otter
dashboard
I
did
not
hear
any
like
filtering
editing
capabilities.
This
is
actually
a
little
bit
done
here,
yeah
what
they
have
this.
So
if
you
want,
for
example,
sport
and
it's
to
let
users
configure
these
are
all
components
and
functionalities
that
we
can
reuse
from
different
dashboards
and.
C
A
That
might
be
something
for
me
to
consider
and
build
issues
to,
because
people
will
likely
be
pulling
this
kind
of
data
into
their
own
data,
warehouse
and
re
displaying
it.
So
it's
more
like
the
raw
data
that
people
are
gonna
care
about,
in
addition
to
the
visualization
or
end-state
will
be
that
we
want
to
drive
people
to
come
to
this
page
to
manage
their
stuff,
but
there
might
be
a
place
where
they're
not
managing
those
kinds
of
actions
inside
of
get
lab.
So
here's
how
I
could
see
that
being
teared
up.
B
A
B
There
exactly
that,
what
she
say:
that's
one
one
of
the
big
learnings
from
her
that's
mine,
yeah,
didn't
really
need
that
much
functionality
in
UI.
There
was
a
lot
of
work
on
the
API,
but
then
you'll
be
nice.
It's
good
to
have
the
ability
to
export
and
then
do
whatever
you
want
with
that
data
in
a
different
platform,
all
right,
Coolio
and
then
the
difference
is
now
we're
really
liking
the
interaction
in
UI.
Sorry
about
that
soon
yeah.
So
this
one
you
see
everything's
in
one
page
and
the
next
one
Falls
a
little
bit.
B
B
The
grid
lab,
so
if
you
go
to
all
this
like
in
analytics
all
these
dashboards,
they
are
like
that
I
find
it
I
have
my
concerns.
Of
course,
I
find
a
context.
Switching
a
bit
odd
you're,
not
really
like,
comparing
the
all
the
data
you're,
not
seeing
the
whole
picture,
yeah
and
also
the
discoverability
of
this
conference
right.
A
The
relationship
between
a
release
and
a
potential
pipeline
right
so
being
able
to
understand
that,
like
this
release
is
targeted
to
this
environment,
and
this
pipeline
just
released
this
environment
in
a
single
snap
is
way
more
actionable
than
toggling.
Between
this
releases
view
and
the
pipeline
view.
B
Are
they
actually
the
value
from
these
interactions,
because
it
might
be
that,
for
example,
like
I,
think
this
one
like
in
these
dashboards
oops
that
you
have
the
ability
to
I
think
this
one
yeah
today
the
CI
file
right
choose
what
you
want
to
see
and
remove
items
from
your
view
right,
you
can
reorder.
For
example,
this
data
can
be
a
bunch
of
things
and
because
of
that
yeah,
it's
okay
to
have
things
filtered
here,
for
example,
they
have
different
steps.
A
Or
boy
like
this
is
a
really
great
view.
This
whole,
this
whole
value
stream
analytics
view
is
actionable.
It's
it's
the
ideal
analytics
platform,
so
whatever
we
would,
we
could
highly
consider
modeling
our
MVC
off
of
some
of
the
way
this
is
designed
and
some
of
the
interactions
that
are
exposed,
given
that
the
drop-down
pick
list
option
really
wouldn't
be
useful
for
a
persona
who's
working
across
multiple
projects
without
context
into
those
projects.
B
A
B
You
get
your
anything,
no,
that
what
you
expect,
you
for
hand,
pipelines,
etc,
but
then
again,
I
agree
with
you.
This
gives
so
much
feeling
of
like
dashboarding
write
the
report
in
the
person
analytics
and
then
I
think
next.
Steps
for
me
is
need
to
collect
honest
feedback
and
then
see
what
components
or
what
could
we
potentially?
Is
this
because
the
next
things
like
this
one.
B
This
one
is
the
parts
for
me:
prototypes
are
really,
and
also
from
the
description
of
the
issue,
this
parts
rights,
the
insights
from
pipelines
and
this
insights
on
the
releases.
They
look
like
just
static
data,
and
do
you
see
users
taking
somewhere
from
pipelines,
are
acting
like
how
they
would
act?
On
top
of
this
information,
the.
A
B
B
Is
of
course,
where
disty
is
going
to
lead
right
right
now,
I
think
in
the
description
we
talked
about,
having
like
in
the
group
overview
and
then
HEVC,
ICD
dashboards.
But
again
we
have
analytics
here
and
also
we
have,
while
this
doesn't
really
matter,
because
it's
at
the
instance
level,
the
other
dashboards
I.
A
Could
see
it
replacing
like
you
know
how
we
have
the
environments
dashboard
up
top
I
could
see
this
replacing
the
environments
dashboard
view,
and
then
we
tab.
It's
from
releases
to
environments
to
you
know
like
I
could
see
this
being
at
the
highest
level
rather
than
invest
it
inside
the
group,
but.
B
I
think
this
is
I.
Put
this
as
a
note
here
somewhere.
This
is
one
of
the
things
I
would
like
to
invalidate.
Maybe
we
can
do
two
prototyping
yeah
in
a
way
we
can
move
this
thing
around
inside
the
products,
but
it
feels
like
it's
such
a
unimportant
thing.
The
workflow
for
these
prior
is
that
if
you
have
to
go
to
the
grip
level,
today,
click
a
menu
and
see
that
awesome
yeah
just.