►
Description
This is a walk-through of all the prototypes linked in the following issue:
https://gitlab.com/gitlab-org/gitlab/-/issues/208008
A
Okay,
alright,
so
basically
they
just
start
sharing
my
screen
to
hear
mostly
what
I
want
to
go
over
today.
Is
this
issue
right
here,
which
is
basically
all
the
end-to-end
mock-ups
for
the
mass
integration?
Epic
that
we've
been
working
on,
so
patrick
has
done
a
great
job
of
trying
to
put
down
all
the
different
states
that
we
needed
to
design
for
and
with
some
of
the
states.
A
A
So
basically,
what
we're
doing
is
we
are
we're,
basically
making
the
feature
of
service
templates,
better
I,
guess
and
what
we're
gonna
be
doing,
is
getting
rid
of
service
templates
and
we're
gonna
be
making
it
so
that
if
you're
an
admin
of
an
instance,
you
could
set
up
an
integration
for
JIRA
and
it
will
set
up
through
all
for
all
projects.
So
current,
the
current
limitation
of
service
templates
is,
if
you
set
up
that
service
templates
for
like
a
JIRA
configuration,
for
example.
A
Let's
say
the
new
projects
are
created,
only
the
new
projects
will
inherit
those
settings,
not
any
old
projects
and
then,
if
a
project,
if
the
project
owner
decides
to
change
those
settings,
they
can
there's
no
way,
for
you
know
a
service
template
to
be
smart
and
know
that.
Oh,
you
know
a
woman
one
of
my
projects
that
has
overridden
one
of
these
settings.
So
there's
certain
limitations
there.
So
the
idea
is
that
we're
going
to
get
rid
of
service
templates
or
deprecate
them,
and
we
are
gonna.
Have
this.
A
This
new
way
of
doing
integrations
and
we're
gonna
also
introduce
them
not
only
to
the
instance
level,
but
also
to
the
group
level,
where
we
don't
have
those
yet
so
any
questions
before
I
kind
of
dive
into
this
all
good,
all
right,
cool
and
then
also
if
we
have
a
little
bit
of
time,
I
think
I
wanted
to
go
over.
Some
of
the
we
were
discussing
like
on
how
we
were
gonna
actually
migrate
away
from
service
templates
to
this
noose.
A
New
new
way
of
doing
integrations
across
the
instance
level
in
group
level,
anyways,
first
of
all,
I'll
just
dive
into
the
prototypes
and
then
I'm
gonna
rearrange
this
issue
by
the
way.
But
if
you
don't
all
mind,
if
you
want
to
leave
feedback,
then
for
the
individual
flows,
I
think
it'll
be
better.
If
you
just
do
it
within
figma,
get
more
contextually
instead
of
I.
Put
a
comment
here
which
I'll
delete,
which
says
to
kind
of
put
the
comments
within
the
design
tab.
A
So
I'll
kind
of
look
at
what's
in
here
already
and
then
I
might
just
scrap
those
and
then
we'll
just
go
with
with
what's
in
figma
and
and
in
order
to
leave
comments
in
figma,
all
you
have
to
do
is
create
like
a
free
account
and
just
create
it
with
your
gitlab
account.
This
way,
I'll
know
who's
actually
leaving
that
feedback
all
right.
A
So
let
me
start
sharing
the
figma
file,
and
so
what
I'll
start
doing
is
I
will
work
through
what
it's
what
it
looks
like
when
settings
are
being
Heretic
at
the
project
level
and
then
what
it
looks
like
when
they're
being
inherited
at
the
group
level
and
then
what
it's
like
when
you're,
not
the
instance
level
to
basically
create
one
of
these
settings,
these
global
settings,
it's
gonna,
be
one
sec.
Let
me
find
my
figma
file
all
right,
all
right
so
at
the
project
level.
So
let
me
start
this
off
here.
A
You
all
see
in
the
figma
screen
by
the
way:
okay,
great,
okay,
let's
let
this
load
up
here
so
at
the
prod.
So
this
is
what
it
would
look
like
if
let's
say
I'm
a
older
owner
of
this
project
and
I've
created
this
project
called
help,
Docs
and
and
then
I
go
to
the
integration.
My
settings,
integration
and
I
see
that
a
JIRA
you
know
configurations
already
set
up
and
I.
A
Have
this
banner
here
saying
that
it's
already
managed
by
an
administrator
that
I
can
restore
the
settings
if
I
need
to
and
by
the
way,
I
just
wanted
to
note
that
I
still
want
it
once
I
kind
of
have
more
confidence
with
some
of
these
flows,
then
I'll
get
a
Russell
tech
writing
involved
into
this
because
I
know
a
lot
of
the
copy
that
you'll
see.
Here
is
a
lot
just
for
placement.
Only
so
anyway,
so
you'll
see
this
banner
and
then
I
have
the
option
as
this
project
owner
to
overwrite
some
of
these
settings.
A
So
let's
say
I
wanted
to
use
my
username
and
login
for
in
this
case,
for
my
cheerin,
so
I
would
start
editing
there
and,
let's
say
I
just
wanted
to
use
Bob
and
then
I
wanted
to
use.
You
know
my
own
password,
but
I
want
to
keep
the
URL
that
admins
assigned
and
that
I
maybe
want
to
also
have
merged
comments
on
merge
requests
happen.
So
what
you'll
see
happen
is
that
I
was
hoping
that
maybe
this
could
happen
on
focus
and
as
I'm
typing.
A
So
then
the
banner
would
change,
and
then
you
would
actually
see
the
fields
would
highlight
that
are
being
overridden
and
then
now
I
also
have
this
new
button
here
that
appears
that
says
to
restore
admin.
Settings
so
I
could
click
that
and
then
all
my
settings
are
restored
back
to
whatever
the
admins
settings
were
and
again,
I
would
just
override
that
and
let's
say
I
still
want
to
keep
those
settings.
A
I
would
just
hit
save
then,
and
then
we
should
use
like
we
should
actually
use
the
new
toast
pattern
and
that's
in
pajamas
I've
noticed
that
currently,
all
our
integrations
also
use
the
alert
to
kind
of
just
to
show
success
messages,
and
we
should
be
using
this
so
I'm.
Introducing
this
the
toast
pattern
to
show
the
success
messages
here
anyway.
So
that's
project
level.
Any
questions
here
before
I
go
on
before
I
go
on
up
the
group
to
the
group
level.
B
A
Yeah
I,
thank
you
for
bringing
that
up.
Lucas
I
did
forget.
I
was
gonna,
bring
that
up,
but
I
don't
have
that
state.
Yet
so,
basically,
when
I'm,
when
I'm
kind
of
visioning
here
is
a
similar
state
to
let's
say
this
one
here
and
I
need
to
add
that
screen.
So
I
will
add
this
a
similar
state
to
this
screen,
but
with
all
the
fields
disabled
it
maybe
with
an
an
extra
explanation
of
why
they're
disabled
here
or
where
there
would
be
masked.
A
So
we
have
a
there's,
an
issue
that
has
lists
all
the
user
stories
that
were
designing
for
and
those
are,
those
are
all
part
of
the
user
stories
and
then
there's
another
set
of
user
stories
that
we
have
for
like
for
more
future
releases.
Once
we
validate
you
know
this,
this
current
setup
and
in
some
of
those
user
stories
we
have
the
extra
the
extra
feature
to
be
able
to
kind
of
lock
only
certain
settings
versus
all
the
settings
or
to
be
able
to
mask
certain
settings
on
the
individual
fields.
Level.
A
A
Let's
let
this
load
so
I'm.
An
admin
of
this
group
called
Fernan
group
and
then
this
this
currently
doesn't
exist
right
now
and
within
the
group
level.
So
I
have
this
new
menu
item
that
says
integrations
and
I
will
go
to
my
integrations
and
I.
See
this
like
updated
layout
of
integrations
and
I,
see,
I,
have
no
active
ones
and
there's
my
list
of
all
the
potential
integrations
that
I
could
set
up
so
I'm
gonna
set
up
JIRA
for
my
group
and
again
I
see
this
manner.
A
That's
saying
that
this
feature
is
new
and
that
everything
everything
that
I
setup
here
will
apply
it.
Everything
within
that
group,
let's
see
so
all
right,
so
I'll
go
ahead
and
set
this
set
up
my
settings
and
then
also
see
this
table
down
here
that
I
could
see
that
which
projects
are
potentially
overriding.
A
So
this
is
editing
an
integration
that
already
has
inherited
some
values.
So
in
this
case
I'm
again,
the
the
owner
of
this
group
called
Fernand
group,
and
the
admin
of
this
instance
has
already
set
up
a
juror
integration
and
they
want
everyone
within
that
instance
to
inherit
settings
so
I
see
now.
If
I
go
to
this
integrations
menu,
I
see
that
there's
already
Juris
setup
so
I
go
there.
A
A
So
again,
like
slow
I
mean
at
the
group
level
here
and
I,
go
to
my
integrations
and
again
so
just
to
slow
down
a
little
bit
so
I'm,
not
I'm,
the
owner
of
the
group
and
I,
have
my
admin
settings
that
are
being
inherited
down,
but
then
also
at
this
group
level,
I
have
three
projects
that
have
been
already
overriding.
These
settings,
these
these
settings
within
my
group,
so
you
could
see
here
I'll
be
able
to
see
that
this
Django
API
is
dot
project
and
these
other
help.
Docs
projects
are
overriding.
A
My
group
settings
here
which
which
happen
to
be
trickled
down
from
the
instance
level
settings
so
again,
if
I
wanted
to
change
these
settings
and
I
want
to
have
these
settings
be
overridden.
I
could
do
that.
I
could
add
this
and
then
I
could
hit
save
and
then
now
I
have
the
option
within
my
heading.
A
So
in
this
case,
I'm
just
going
to
leave
them
and
hit
save,
and
then
I
could
see
that
I'm
overriding
the
admin
settings
or
the
instance
level
settings
but
I'm
still
keeping
my
settings
and
then
these
project
owners
are
still
keeping
their
settings
and
that's
also
okay.
So
this
is
a
little
bit
of
a
kind
of
a
interesting
scenario
where
you're
kind
of
overriding
the
admin
level
settings
and
I
can
also
have
the
child
project
overriding.
A
My
group
level
settings
and
they
could
be
overriding
the
instance
level
settings
so
yeah
I'd
love
that
everyone's
feedback
on
this
kind
of
I
feel
like
this.
This
is
the
screen
that
could
be
a
little
bit
confusing
the
most
at
this
group
level.
So
once
you're
going
through
the
figma
prototype
screen,
yeah
I'd
love
to
get
some
feedback
here.
A
D
Question
so
so,
in
this
stage
the
admin
has
some
settings
and
at
the
group
level,
you're
over
I
think
some
settings
right
yeah.
How
am
I
supposed
to
know
as
a
user
which
settings
have
I
overridden
like
is
this.
You
know
State
supposed
to
stayed
there
to
show
me
that
is.
It
appears
that
I've
changed
or
yes
yeah.
That's
great!
That.
D
B
A
Those
those
would
be
links
to
that
project
directly,
so
you
can
call
exactly
and
it
would
actually
link
exactly
to
the
same
settings
page
where
you
could
see.
Oh
okay,
this
is
what's
being
overridden
and
then
I
could
just
change
it
and
then
I
could
actually
hit
this
button
for
that
project
owner
than
it
would
restore
it.
Yeah,
okay,.
E
B
One
questions
sorry
probably
could
have
fasted
earlier.
It
doesn't
really
fit
to
just
this.
You
just
showed,
but
just
in
general
you're
talking
a
lot
about
JIRA
and
it's
maybe
more
for
the
engineers.
If
we
implement
this,
do
we
have
to
implement
it
for
every
integration
that
we
currently
have
or
is
to
basically
like
the
implementation,
wise,
a
quick
win
and
everything
that's
now,
as
so.
This
template
will
automatically
be
in
integration,
yeah.
D
D
B
This
was
just
a
general
question
because
we
were
always
talking
about
jiriz.
If
we
go
into
the
nitty-gritty
details-
and
I
could
imagine
that
some
certain
integration
it's
differently
because
reasons
but
I
just
had
to
feel
that
we
have
to
go
through
a
similar
work.
You
know
obviously
a
bit
easier,
but
if
you
have
to
go
and
implement
all
the
forms
for
every
integration
but
yeah
cool.
Thank.
D
For
the
front-end
itself
and
nine
percent
sure
like
how
complicated
this
kind
of
flow
will
be,
so
we
might
be
some
specific
changes
for
some
forms,
especially
if
you
want
to
have
like
the
whole
personality
of
like
you
know
like
keeping
in
our
same
page,
because,
right
now,
it's
all
Hamel
views,
which
means
like
you
need,
like
refreshes
on
every
kind
of
action,
Rema
shown
you're
safe
on
your
restore.
You
might
need
some
refreshes,
so
heats.
A
Not
adding
you
at
the
moment,
actually
thanks,
Justin
and
I
just
want
to
also
be
clear
that
this
is.
This
is
kind
of
my
second
pass
at
this,
so
the
more
I've
been
kind
of
doing
this
I
would
love
to
kind
of
get
some
other,
like
user
validation
on
this,
so
I
don't
want
anyone
to
feel
like
this
is
the
final
UI
for
this.
So
this
is
just.
A
This
is
just
one
way
of
kind
of
doing
this,
of
showing
the
user
that
which
settings
are
overridden
so
I
have
a
couple
ideas
of
other
variations
on
this
of
how
this
could
work.
So
I
wanted
to
kind
of
maybe
create
a
separate
issue
and
just
test
those
out
and
maybe
also
just
run,
those
with
run
those
designed
by
a
larger
UX
group
to
see
what
their
thoughts
are.
I'm,
just
kind
of
this
specific
pattern
of
how
you
know
settings
are
being
overwritten,
so
yeah
I'll,
let
everyone
know
once
there.
This
is
more
final.
B
Well,
one
of
the
things
that
that
popped,
in
my
mind,
is
if
I
think
not
necessarily
about
a
JIRA
integration
people,
for
example,
for
slick
integration.
One
thing
that
I
could
imagine
is
that
you
let's
say
you
have
different
select
channels.
You
want
to
send
something
to
that
on
a
group
level.
You
might
want
to
create
this
as
presets
right
I
had
these
five
presets
to
send
to
these
channels.
Maybe,
but
that
sounds
like
further
down
the
road.
C
It's
not
necessarily
true
of
all
integrations
rate
like
JIRA,
because
it
integrates
the
instance
level
is
not
that
white,
but
I
mean
one
of
the
things
that
had
been
discussed
was
possibly
allowing
the
the
instance
or
group
level
integration
to
be
saved,
as
not
active
and
with
fields
missing
right.
So
you
could
set
up
the
entire
slack
integration,
except
for
the
channel
and
then
not
set
it
as
active,
and
then
what
that
allows
is
all
of
those
other
pieces
of
information
can
flow
out
everywhere
and
then
they
can
set
up
the
channel
in
instantly.
C
B
A
All
good
yeah,
it's
always
good
a
tree.
A
skew
I
feel
like
everyone
will
learn
something
again
so
yeah.
That's
a
good
point!
Patrick
about
that
that
user
user
story
there
I
should
add
that
one
as
well
about
kind
of
like
because
what
we're
saying
here
is
a
lot
of
these
settings
from
the
administrator
they're
recommended
right.
So
in
some
case
some
cases
they're
mandatory
in
some
cases
that
recommend
it
so
so
yeah
I
should
I
can
make
a
user
flow.
D
Just
asked
one
more
question:
yeah
sure
just
try
to
complicate
this
even
more.
Are
we
going
to
support
like
subgroups,
so
you
have
like
admin
right,
I
mean
then
that
inherits
two
groups
really
have
accept
and
simply
push
have
something
like
I
know.
It
says
it'll
probably
have
to
say
you
had
things
from
admin
and
the
crew
yeah.
A
Exactly
just
that's
what
I
was
thinking.
I
was
hoping
that
this
pattern
would
scale
across
even
the
subgroups.
So
everything
should
be
the
same.
You
might
just
see
different
copy
somewhere
saying
like
this,
this
this
project
overrides
you
know
or
I'm.
Sorry
like
somewhere
here
I
said
I,
don't
know
where
it
was
but
yeah.
Maybe
we
would
just
change
the
copy
saying
like
what
the
scope
of
that
actual
state
state
you're
in
is.
A
You
know
like
if
it's
a
subgroup,
if
it's
inheriting
from
a
group
or
it's
going
to
be
changing
all
projects
under
this
subgroup,
for
example.
So,
ideally
that's
hoping
that
this
pattern
would
scale
across
those
I
haven't
done
a
mock-up
for
a
subgroup
yet
or
a
flow
through
that
just
to
see
if
I
was
right,
you
know
or
if
it
will
scale
so,
but
my
thoughts
are
that
it
I
think
it
scales
right
now
see
if.
D
D
A
A
All
right,
let
me
start
at
the
beginning
here
so
yeah,
again,
quick
context,
I'm
the
admin
of
the
instance
level
and
I
already
setup
JIRA
within
my
integrations
here
and
then
I
see
with
like
to
answer
your
question.
Justin
I
could
see
that
you
know
all
the
projects
again
that
are
being
overwritten
and
then
this
is
the
idea
of
the
kind
of
most
MVC
kind
of
version
of
this
table
is
just
listing
them
all
out
and
you
could
click
to
them.
A
Ideally,
maybe
we
have
like
a
way
to
like
filter
this
table
like
show
me
only
all
the
groups
that
are
overriding.
You
know
this
these
settings
or
something
like
that
or
other
ways
to
kind
of
parse
this
table
out,
but
right
now,
I'm,
just
using
this
convention,
where
you
have
like
the
slash
convention,
I
see
that
we
use
that
somewhere
else
within
the
app,
so
you
could
see
which
groups
are
being
overriding
or
which
projects
live
within
which
it
within
each
group
that
are
overriding
those
settings
and
I
can
see.
A
B
On,
on
the
other
hand,
like
the
in
the
previous
screen,
you
had
to
restore
to
admin
settings
button
right
and
if
you
are
on
a
deeper
hierarchy,
theoretically,
it
could
be
that
you
don't
want
to
restore
to
the
instance
level,
but
maybe
to
some
subgroup.
So
if
you're
actually
inheriting
from
multiple-
but
this
is
also
way
down
the
road.
If
you're,
inheriting
from
multiple
you
could
be
hey,
I,
don't
want
to
go
back
to
the
instance
data
or
to
get
them
all.
A
A
F
A
long
little
comment,
I
think
for
it
might
be
easier
for
the
first
iteration
to
to
not
enable
like
subgroup
inheritance
for
the
for
the
settings,
but
I'm
not
quite
sure,
but
maybe
this
is
something
we
could
do
to
to
make
smaller
iterations.
To
just
say,
kids
can
be
just
in
the
same
group
and
there's
next
step
at
the
next
parent
group.
Inheritance.
G
B
One
question:
let's
imagine
you
have
a
project,
you
know
get
lab
or
group
subgroup
being
front.
End
group
and
I
have
like,
let's
say,
good,
lab,
UI
or
pajamas
design
system
as
a
project.
If
I
now
have
settings
in
pyjamas
design
system,
what
you're
advocating
for
that?
It
just
can
inherit
from
the
front
end
group
for
now
or
from
the
top
level
I.
F
B
Won't
know
what
what's
the
more
interesting
use
case
for
companies,
though
right.
If
you
look
like
with
a
lot
of
subgroups
from
like
we
do
and
Hitler.
If
it's
more
interesting
to
you
to
say,
hey
I
want
to
set
settings
on
the
get
lab
level,
because
that's
basically
the
use
case,
probably
for
a
lot
of
people
using
get
left
common
because
companies,
you
know
they
don't
have
access
to
the
instance
lever
or
if
they
you
know,
because
if
you
now,
instead
of
managing
a
thousand
projects,
you
have
to
manage
a
hundred
groups.
C
Think
that's
totally
fair
as
far
as
I
am
in
full
support
of.
If
parent
groups
keeps
the
iteration
smaller
occurred,
you
know
top
level
groups
makes
the
iteration
smaller
right
off
the
bat
I
think
that
makes
total
sense
totally
fair,
all
I'm,
all
in
favor
of
small
aeration,
but
we
commonly
to
be
to
your
point:
I'd
be
get
lab.
Comm
customers,
you
have
one
parent
group
for
their
entire
organization,
sometimes
with
tens
of
thousands
of
projects
all
right
like
one
of
the
targets
for
this
particular
integration
has
I.
C
Think
five
thousand
projects
on
get
lab
comm
all
within
one
group,
and
then
they
have
I-
think
it's
eighteen
subgroups
inside
of
that
they
each
then
also
have
you
know,
that's
how
they
organize
everything
and
that
allows
if
everything
being
in
one
group
allows
them
tighter
control
around
compliance
and
security
concerns.
So,
yes,
I
think
subgroups
is
highly
important.
A
C
Thanks
I
think
it's
awesome.
I
am
yeah.
I
think
this
is
great.
Thank
you
for
putting
this
together.
I
think
my
my
overall
feedback
I
really
like
I
like
where
things
are
at
you
know
the
cues,
the
designer
I'm,
like
biggest
all
of
it.
There
overall
is
great
and
I,
think
that's
awesome,
I
think
they're
more
tactically
I
really
want
to
sit
down
with
you
and
kind
of
walk
through
these
on
a
one
by
one
and
really
dig
into
it.
C
That's
not
like
really
perfectly
tuned
and
I'm
afraid
of
confusing
people
so
other
than
that,
though,
I
feel
like
all
of
the
all
of
the
bones
are
here
right,
like
we've
got
all
of
the
the
big
moving
parts,
and
now
it's
down
to
things
like
IP,
had
a
very
point
right
like
been
making
the
table
not
huggable
and
like
making
sure
we
can
quickly
move
around
the
interface
things
like
that.
It's
really
you
know,
we've
got
you
know
the
8020
of
it.
Really
we've
got
the
80
down.
C
Let's
go
get
the
last
20%
and
really
get
all
of
these
things.
Buttoned
up
well
and
I.
Think
this
is
great.
This
is
gonna,
be
awesome,
so
I'm
gonna,
I'm
gonna
schedule
some
time
to
follow
up
with
you
too.
Let's
do
like
a
deep
dive
on
these
and
really
walk
through
each
one
side
by
side
we
can
try
I'm,
really
curious.
I
haven't
tried
out
the
figma
multiplayer
stuff.
Yet
so,
let's
try
out
like
pigma
and
like
let's
get
in
there
and
like
do
some.
Do
some
work
on
this,
but
I
think
this
is
awesome.
A
Yeah
sounds
good.
Yeah
I.
Definitely
think
that,
like
you
mentioned
better,
the
copy
is
super
important,
especially
like
you
know
what
I
was
doing
going
through
the
flow
over
the
migration.
That
could
be
very
scary,
like
you
know,
like
what's
gonna
happen
now,
so
getting
that
just
right
is
gonna,
be
very
important.
Yeah,
especially
there.
So
yeah.
C
But
yeah
and
I
think
like
the
especially
the
copy
I
mean
not
to
like
you
know,
pick
nits
right,
man
right
like
but
I.
Think
again,
that's
great,
but
it's
things
like
how
we're
talking
about
when
you
save
the
settings.
Do
they
apply
to
things
or
do
they?
You
know
reset
override
things
like
that,
like,
let's
make
sure
that
copy
is
really
explicit,
I
think
there
are
a
few
opportunities.
C
We
may
actually
want
more
descriptive
copy
right
like
on
that
particular
that
dialog
right,
like
to
better
explain
like
this,
is
why
I'm
asking
you
this
question
in
this
context,
and
this
is
why
you
need
to
respond
I,
think
things
like
that
are
gonna
be
important,
but
again
I.
Don't
think
any
of
that
stops.
Engineering,
like
all
of
this
stuff
is
gonna,
be
like
small
tweaks
to
the
UI,
not
not
like
functional
tweaks,
so
I
think
an
awesome,
great
work.
C
A
Great
yeah:
well
thanks
everyone
for
this.
For
sticking
through
this
and
after
this
call
I'm
gonna
update
the
end
end
issue
mock
up
and
I'll
just
ping,
everyone
in
the
in
the
ecosystem,
Channel,
when
it's
ready
or
just
ping.
You
in
the
issue
saying
if
you
want
to
leave
feedback,
I'll,
put
a
little
bit
more
instructions
on
how
to
leave
feedback
within
that
issue,
then
alright,
yeah,
thank
you
all
and
yeah
looking
forward
to
getting
this
one
released
into
the
wild
soon.