►
From YouTube: GitLab 13.0 Kickoff - Create:Ecosystem
Description
UX Showcase - Mass integrations: https://www.youtube.com/watch?v=IcOzDhbzlX8&feature=youtu.be
Ecosystem Board: https://gitlab.com/groups/gitlab-org/-/boards/1167634?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aecosystem
A
Hi
I'm
Patrick
Dooley
I'm,
the
senior
product
manager
for
get
labs
ecosystem
group-
and
this
is
our
thirteen,
oh
kick-off.
We're
going
to
talk
about
the
work
that
we'll
be
doing
over
the
next
month,
touching
on
our
continued
progress
on
mass
integrations,
some
changes
to
our
JIRA
integration
and
the
work
that
we're
doing
on
our
pajamas
design
system.
A
So
at
first
this
is
not
work
that
we're
doing
in
30.
No,
it's
work
that
we
just
completed
but
Lieb
or
just
did
a
UX
showcase,
where
our
UX
team
walks,
through
some
of
the
design,
work
that
they're
doing
and
he
was
walking
through
the
mass
integrations
design
that
was
recently
completed.
So
this
is
work
that
we're
starting
to
implement,
but
in
particular
we
wanted
to
highlight
it
because
this
is
stuff.
That's
been
our
topic
for
months
now
and
we
now
have
a
full
end-to-end
walkthrough
of
what
that
workflow
is
going
to
look
like.
A
So
that's
really
exciting,
and
this
is
also
going
to
be
the
basis
for
all
the
UI
work
that
we'll
be
doing
over
the
next
couple
of
milestones.
So
I'll
make
sure
to
link
that
in
the
description
for
anyone
who's
interested.
It's
also
on
our
get
lab
unfiltered
account,
so
you
can
also
find
it
there,
along
with
a
lot
of
other,
really
interesting,
UX
work
that
our
team
does
also
in
regards
to
the
mass
integration
work.
A
So
mass
integration
is
going
to
allow
you
to
integrate
at
an
instance
level,
which
historically
has
been
done
with
service
templates,
so
we'd
like
to
create
a
design
in
this
instance,
we're
gonna
be
doing
a
design
first
and
then
we'll
go,
build
it,
but
a
design
for
a
tool
that
allows
you
to
migrate
from
service
templates,
to
instance,
integrations.
So
what
that
would
look
like
is
something
that
takes
those
configured
values
deletes
the
service.
A
Template
creates
an
instance,
integration
temp
with
those
values
and
then
goes
and
removes
those
values
from
each
of
the
individual
individual
projects.
So
we
walk
through
the
use
case
here
and
the
proposed
design
in
this
issue.
I
think
this
is
gonna
be
really
valuable.
We
have
a
lot
of
customers
who
are
currently
using
service
templates
to
try
to
integrate
many
projects,
and
it's
not
a
great
experience
for
them
and
that's
the
reason
we've
been
working
on
integrations
for
a
while.
A
A
Additionally,
this
is
an
old
request
being
able
to
look
at
all
projects
that
have
a
specific
service.
That's
been
enabled
well,
that
was
a
little
more
complicated,
because
the
way
that
we
integrated
projects
or
integrated
services
was
on
a
project-by-project
basis.
So
again,
now
that
we
have
mass
integration,
this
idea
that
a
group
can
have
a
bunch
of
integrations
all
in
one
place.
This
becomes
more
and
more
relevant,
so
we're
gonna
revisit
this
in
30,
no,
with
with
more
design
work,
we're
also
working
on
making
JIRA
transition,
IDs
easier
to
configure
and
I
know.
A
We
talked
about
this
a
few
issue
a
few
milestones
ago
when
the
design
work
kicked
off.
For
it
and
the
problem,
just
to
recap,
is
when
you
configure
your
JIRA
integration,
it
looks
a
little
like
this
and
your
transition.
Id
is
this,
which
is
to
be
perfectly
honest,
inscrutable
right,
so
just
as
JIRA
issue
transition,
which,
by
the
way,
if
you've,
never
been
a
JIRA
admin,
you
almost
certainly
don't
know
what
a
transition
is,
let
alone
why
it's
a
right.
A
So
that's
really
confusing,
and
for
those
who
don't
know
a
transition
is
when
you
move
something
from
say
to
do
to
doing
right.
You've,
transitioned
the
state
so
to
do
doing
is
one
transition.
Doing
done
is
another
transition,
and
what
we're
expecting
here
is
for
you
to
put
that
ID
numbers
for
each
one
of
those
transitions
in
there
and
that's
a
terrible
experience.
So
we've
been
working
on
figuring
out.
What
that
could
look
like.
A
We've
got
some
mock-ups
here
where
we
look
at
all
of
the
different
transitions
that
could
be
there
and
create
an
offer,
a
UI
that
allows
you
easily
select,
which
ones
are
relevant
to
your
project,
so
that
wraps
it
up
for
the
work
we're
doing
in
integrations,
so
the
front-end
UX
foundations
category
also
owns
the
pajamas
design
system.
So
these
are
the
components
that
are
coming
in
30
now,
I
think
they're,
super
exciting
in
particular
forms
is
really
cool.
Now
I
was
a
designer
for
a
long
time.
A
Forms
are
where
the
bane
of
my
existence
for
many
years
I
expect
that
to
be
a
really
exciting
component,
that's
gonna
generate
a
lot
of
really
great
values
throughout
the
application.
It'll
be
a
really
widely
used
component,
so
I
think
that's
some
really
awesome
work
and
to
be
clear,
the
the
work
that's
being
done
here
is
spread
all
throughout
the
organization,
so
the
pajamas
design
system
is
used
by
front-end
engineers
and
UX
designers,
all
throughout
gitlab.
A
Now
the
front-end
UX
foundations
team
is
the
stewards
of
that
design
system,
but
the
work
actually
gets
done
all
over
the
place.
So
thank
you
to
all
the
people
who
are
contributing,
collaborating
in
all
of
these
different
issues,
making
these
components
and
then
going
and
implementing
them.
This
work
allows
the
gitlab
application
to
be
more
maintainable
more
accessible.
It
allows
us
to
be
more
modern
and
flexible
and
that's
really
important
work
going
forward.
So,
thanks
to
everybody
involved,
it's
awesome
that
everybody
is
getting
in
and
working
on
this
together.
So
that's
it!
A
That's
what
we're
working
on
in
1210
I'm!
Sorry
in
30!
No
excuse
me!
So
that's
what
working
on
in
30
now
we're
really
excited
to
start
closing
down
the
mass
integration
work
that
we're
doing.
We
can't
wait
to
ship
that
we're
hoping
we
can
make
Jiri
easier
for
everybody
and
we're
hoping
we
can
make
the
gate
lab
application
more
stylish
and
awesome
and
easier
to
use
and
accessible
for
everybody.
Thanks
a
lot
for
watching
and
have
a
great
one.