►
From YouTube: Manage UX Weekly Design Review 2020-10-05
Description
Austin and Mike review types of CSV exports (https://gitlab.com/gitlab-org/gitlab/-/issues/257951#note_421217016)
A
B
Yeah,
I
think
I
think
my
the
hurdle
for
me
was
that
there
were
it,
looked
like
about
three
links
that
I
needed
to
click
into
yeah,
and
it
was
I
it
seemed.
I
was
like
oh
I'll
have
to
carve
out
a
bit
more
time
for
this
one.
So
I
can
you
know
kind
of
figure
out.
What's
going
on.
A
Yeah
I
get
that
the
most
important
one
was
the
comment
that
one
of
our
front-end
devs
robbed
left.
So
when
exporting
a
csv
from
get
lab,
it
seems
that
we
have
two
existing
patterns.
For
that
one
is
this
email
gets
generated
and
sent
to
you
once
gitlab
has
finished,
processing
this
bigger
file
and
then
the
other
one
is.
It
can
happen
within
gitlab
and
you
get
like
a
normal
prompt
to
like
save
the
file,
but
that's
usually
used
when
it's
much
smaller
and
it
can
happen
pretty
quickly.
A
The
struggle
then
becomes
like
what
do
you
do
when
you're
like
in
between
something
that's
not
going
to
take
like
10
minutes,
but
it's
also
not
going
to
take
like
30
seconds
and
the
back
and
front
team
were
kind
of
spiking
to
play
with
this
secondary
option
so
something
that
might
take
a
little
bit
longer
than
30
seconds.
But
you
might
not
leave
the
page
you're
willing
to
wait
for
the
download
link
to
appear
so
I
she's
one
of
our
back-end
developers.
A
She
put
together
this
quick
demonstration
of
like
how
this
might
actually
work.
So
when
you
go
to
hit
the
generate
report
button,
essentially
it's
building
it
for
you
and
then
eventually
it's
done
and
you
get
a
link
to
download
it,
which
she
just
shows
as
a
another
button
on
the
screen.
So
there's
still
time
to
like
refine
how
the
ux
itself
would
play
out.
But
it's
it's
a
newer
pattern
of
just
showing
like
getting
the
download
from
within
gitlab.
A
So
then
I
went
on
to
kind
of
play
with
it
a
little
bit
I
recorded
a
video
showing
how
it
would
look
potentially
cleaning
up
the
ux
bit.
So
I
tried
using
just
alerts
and
replacing
them
rob's
idea.
Yeah,
maybe
not
use
all
alerts
because
it
might
be
hard
to
do
it
with
front
end.
So
maybe
using
a
toast
notification
to
know
you.
So
you
know
that,
like
it's
generating
the
report
and
then
use
an
alert
to
tell
you
when
the
download
link
is
ready.
B
I
like
how
you've
placed
the
download
link
download
link
in
the
alert
banner.
That's
that's
that
was
kind
of
my
first
piece
of
feedback
from
the
previous
video
okay,
because
I
was
I
was
looking
at
it
and
it
felt
more
like
a
pattern,
for
you
know,
go
check
your
email
for
the
download
link
and
yeah.
That's
a
tough
one.
I
almost.
I
also
wonder
if
maybe
there's
an
option
where
the
download
link
is
visible
but
disabled
until
the
link
is
actually
ready.
A
A
B
B
A
So
the
functionality
is
already
there
like.
You
can
already
export
the
file,
and
it's
doing
this
quick,
pulling
persistent
you're
getting
just
a
css.
The
problem
is
we're
adding
in
new
columns.
I
believe
that
are
taking
longer
to
pull
back
from
the
database,
and
so
that's
taking
longer
to
generate
the
report.
A
So
the
job
design
hasn't
changed
like
the
essentially
the
compliance
manager
or
the
auditor
needs
to
extract
this
data.
It's
just
more
about
like
how
do
we
give
it
back
to
them,
and
so
we
were
going
well.
Do
we
change
the
whole
experience
to
go
back
to
the
email
thing
or
say:
hey,
you'll,
get
an
email,
and
who
knows
how
long
make
sure
you
check
that?
B
Another
option
could
be
to
open
a
new
window
or
slash
tab,
open
a
new
view
in
a
new
tab
or
window,
and
that
would
be
the
the
place
where
the
compliance
person
can
go
back
and
see
if
it's
ready
like
basically
the
page
would
be.
You
know,
preparing
your
file
page
and
then
they
could
have
that
page
open,
go
back
and
look
at
it
when
it's
ready,
the
link
will
be
visible
when
it's
not
ready.
B
A
Yeah,
I
could
share
that
as
an
option
and
see
what
the
back-end
phone
team
thinks
in
terms
of
complexity,
because
obviously
we're
trying
to
balance
the
well
it's
already.
There
is
there
and
it's
easier
to
implement
than
creating
something
new.
So
we're
just
pulling
that
tug-of-war.
A
I
couldn't
give
you
a
quantification
on
numbers,
but
what
I've
heard
from
users
is
the
csv
data
is
very
important
to
them,
for
sharing
with
external
auditors
or
for
manipulating
the
data
for
themselves.
So
it
seems
like
it's.
A
primary
action
of
people
related
to
compliance
as
they
want
to
get
hands-on
with
the
data
to
either
pull
it
into
their
systems,
share
it
with
somebody
else
or
dig
for
more
information.
A
A
B
Opens
other
possibilities
where
they
could
share
the
link
to
the
csv
rather
than
emailing
a
csv
all
around
too,
and
who
knows
maybe
in
the
future,
you
could
have
a
downloads
page
like
every
expert
you've
ever
requested.
You
know,
is
in
a
list,
but
that's
that's
like
future,
I'm
trying
to
think
of
other
ways
to
possibly
solve
this.
A
I've
done,
I
think
my
main
concern
was
just
like.
Is
it
reasonable
in
the
situation
to
consider
an
alternative
method
for
allowing
the
user
to
acquire
the
csv
so
going
against?
We
already
have
to
try
and
fit
the
middle
ground
because
we
don't
seem
to
have
a
middle
ground
option
when
it
comes
to
getting
files.
Okay,
it's
either
very
quick.
Here's,
your
csv
or
whatever
other
file
you
get
json
so
on
and
so
forth,
or
this
is
gonna.
Take
a
while
like
exporting
issues
and
you're.
B
Okay,
yeah
the
email
experience
isn't
very
good
right
because
it's
like
sending
a
request
into
a
black
hole
until
you
actually
get
something
back
and
email
just
adds
another
layer
of
complexity
too
yeah.
But.
A
A
A
Yeah
it's
hard
to
say
at
least
I
haven't
been
able
to
come
across
anything
just
yet
doing
this
level
stuff
partially,
because
I
don't
necessarily
have
like
admin
responsibilities
that
could
create
this
type
of
report
and
certainly
I'm
sure
some
of
it
is
tied
to
the
amount
of
data
as
well
so
yeah.
Just
creating
a
one-off
example.
Probably
would
keep
it
small
and
just
be
like
a
download
file,
but.
A
B
A
A
Okay,
so
this
was,
I
think
I
put
in
that
slack
message.
I
chose
outlining
the
different
types
of
export
functionalities
and
then
the
examples
for
when
they're
being
used-
and
this
was
the
proof
of
concept
we
were
talking
about,
but
from
that
one.
I
believe
it's
this
one
see
if
oh
just
links
to
the
docs.
A
A
B
A
Yeah
we
have
an
issue
open
to
investigate
how
these
compliance
makers
would
want
to
see
potentially
specific
data
within
the
dashboard
view
itself,
but
they
still
at
least
the
few
that
I've
talked
to
want
this
ability
to
pull
the
data
out
of
gitlab,
because
the
people
that
they
share
their
information
with
they
don't
want
to
give
access
to
unit
lab
because
you,
like
their
auditors,
it's
like
they
want
to
be
able
to
pull
out.
Merge
commits
the
authors.
The
merge
requests
are
associated
to
the
pipeline
group.
Project
is
associated
with
who
approved
it.
A
So
it
goes
to
this
like
chain
of
custody,
and
so
we're
saying
like
we
want
to
be
able
to
show
like
a
chain
of
custody
view
and
then
given
the
ability
to
extract
the
information
beyond
just
what's
in
the
ui
for
automating
purposes,
they
might
only
care
about
other
things
like
code
coverage
or
they
might
care
about
the
status
of
the
pipelines
for
understanding
what
might
need
their
attention.
But
their
auditors
want
to
see
this
like
history
of
what
actually
occurred
for
each
merch
request,
and
so
that's
what
that
report
is
doing.
A
Would
say
the
group
that
we're
trying
to
get
involved
with
using
the
dashboard
is
like
jeff,
bros
and
liz
coleman's
group?
Have
you
watched
how
they're
using
it
today
they're.
B
Using
okay,
yeah
they've,
never
they've
ever
had
the
need
to
export.
Do
an
export
basically
to
date.
B
It'd
be
interesting
to
watch
to
watch.
Somebody
use
it
who
actually
has
typically
has
a
need
to
use
it,
and
then
yeah
share
some
likes
prototype
or
solution
ideas
with
them
to
get
their
reaction.
A
Yeah
definitely
so
I've
been
trying
to
ask
them
for
feedback
when
we
propose
different
ideas
and
like
liz's
comment
like
oh,
we
can't
really
use
the
dashboard
today.
It's
like
that's
okay,
just
tell
me
based
off
of
this
issues.
Proposal
like
is
anything
here
helpful
to
you.
Why
or
why
not
or
like
what
can
we
do
to
entice
you
to
use
the
compliance
dashboard
like
what
is
it
that's
missing
for
you?
A
That
would
help
you
solve
the
job
that
you're
trying
to
accomplish
and
it
could
just
be
like.
Maybe
we're
at
get
lab,
not
the
exact
same
persona
that
we're
trying
to
solve
for
so
we
might
not
have
the
same
sort
of
regulation
pressure
that
maybe
other
teams
are
feeling
yeah,
so
that
could
be
part
of
it.
A
I
know
I
talked
to
like
one
individual
recently
and
they're
telling
me
like
they
spend
just
like
half
their
job.
Jumping
around
merge
requests,
checking
to
see
what
the
pipeline
did
checking
to
see
how
long
someone
spent
reviewing
the
merge
request,
making
sure
the
code
coverage
didn't
decrease
to
show
they're
compliant.
It's
like,
I
don't
think
we
have
people
doing
that,
but
those
are
the
people
we're
trying
to
solve
for.
A
You're
saying,
like
externally,
recruit
those
people
yeah
yeah.
I
got
something
that
I
would
love
to
investigate
further.
How
does
it
work
if
it's
someone
that,
like
we've
recruited
through
respondent,
can
we
like
reach
out
to
them
again
and
incentivize
them
again
to
do
something
with
us
or.
B
Sure
yeah,
of
course,
okay,
I
think
yeah
I
mean
the
only
thing
you'd
want
to
be
mindful
of
is
like
that:
they're
not
too,
that
their
framing
isn't
too
primed
right
that,
but
there's
you're
still
gonna
approach
them
with
like
a
a
relatively
fresh
idea,
rather
than
circling
back
to
the
same
thing,
but
if
like,
if
you've
iterated
on
it-
and
you
want
their
feedback
again
that
that's
also
totally
normal.
B
You
know
whether
whether
you
go
through
the
like
recruiting
channel
again,
the
research
recruiting
channel
is
kind
of
up
for
a
debate
I
think,
but
yeah.
I
think
it
depends
on
like
your
your
relationship
with
them,
your
connection
to
them
like,
if
you
feel
like
you,
could
reach
out
to
them
over
email,
and
they
would
immediately
like
know
who
you
are
and
understand
what
your
request
is.
Then
I
don't
see
any
problem
with
just
reaching
back
out
to
them.
Okay
still
want
to
report
it
and
put
it
in
dovetail
and
stuff,
but.
A
Yeah,
okay,
that
makes
sense
yeah.
I
just
done
a
couple
job
to
be
done.
Interviews
and
three
of
the
six
externally
were
good
cool
and
I
felt
like
oh,
these
people
would
be
great
to
talk
to
again
but
yeah
other
people
that
I've
heard
from
are
like
some
of
our
customers
themselves
and
it's
just
already
hard
to
get
time
with
them
yeah.
A
So
we've
kind
of
done
this
dance
with
them,
like
the
sales
people
to
try
and
get
time
on
some
of
their
calls
and
they've
been
kind
enough
to
give
us
a
little
bit
but
yeah.
We
did
a
little
bit
of
solution,
validation
on
friday,
no
thursday
yeah
it
was
thursday,
and
it
was
really
great
to
hear
some
of
their
feedback
and
they
validated
a
lot
of
assumptions.
They
also
invalidated
a
couple
that
we
had
as
well,
so
that
was
good
just
like
we
could
just
do
more
of
that.
A
It's
just
very
I've
really
come
to
learn
it's
very
hard
to
recruit
for
this
group,
as
evidenced
by
like
the
jobs
to
be
done,
effort
yeah.
B
Yeah
yeah,
I
think,
as
long
as
you're
maybe
like
how
you
are
working
with
recruit
research
recruiting.
So
we
can
make
sure
that
we're
not
kind
of
over
pinging
someone,
so
maybe
yeah,
maybe
going
through
them,
but
then
tell
them.
You
know
like
emily
or
whoever.
Whoever
we're
working
with
for
research
recruiting,
let
them
know
like
here
are
some
names
of
people
that
we've
talked
to
before
that
we'd
like
to
talk
to
again,
but
also
working
with
them,
so
that
we
could
uncover
new
people
too.
B
So
yeah.
I
guess
I
guess
I'm
talking
out
loud,
but
it
does
make
sense
to
go
back
through
research
recruiting
again,
even
though
we
know
some,
you
know
top
three
people
we'd
like
to
talk
to
just
to
make
sure
we're
tracking
like
how
often
are
we
requesting
people's
time
and
then
still
making
opportunity
to
find
to
find
new
folks.
A
B
B
You
bet
did
I
hope
you
got
the
feedback
you
needed.
Maybe
you
could
put
another.
You
know
like
bump
that
thread
back
up
if
you
need
more,
but
I
think
I
think
that
was
the
hurdle
for
me
was
just
that
there
was
like
three
paragraphs
and
each
one
had
a
link
that
I
had
to
click
into,
and
I.
A
A
Right
now
I
understand
yeah.
I
understand
I
tried
to
be
succinct
as
possible,
but
sometimes
I
think
this
may
be
a
good
example
of
like
it
was
just
easier
to
tell
through
words
and
were
able
to
come
to
an
idea
in
10
minutes,
whereas
it
probably
would
have
taken
you
30
to
dig
through
the
links
and
read
yeah,
but
I
was
okay
with
it
like
I.
I
posted
that
idea
sometime
last
week.
I
knew
like
if
I
didn't,
have
any
good
feedback
on
friday.