►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Alright
thanks
Jackie,
alright,
so
my
name
is
Leroy
Vance
I'm,
a
senior
product
designer
on
the
ecosystem
team.
So
just
a
quick
reminder
of
what
the
ecosystem
team
is
all
about.
So
our
vision
is
to
support
the
seamless
integration
between
gitlab
and
third-party
products
and
services,
so
expanding
get
labs
and
market
opportunities
by
empowering
developers
to
contribute
so
for
today's
ux
show
so
alright
do
you
did
everyone
see
the
screen?
Change?
A
Ok,
great,
alright!
So
for
today's
UX
showcase
I
want
to
be
talking
about
the
epic
that
we've
been
working
on
for
a
while,
which
is
called
the
mass
integration
at
a
Rubin
instance
level.
So
I
have
a
link
here
to
the
epic,
so
I
won't
go
through
that
epic
just
yet.
But
so
let
me
start
telling
you
all
about.
You
know
what
this
is
all
about
and
why
it's
important
so
I'm
going
to
start
with
a
story.
So
just
imagine
that
you're
Devin
you're
a
DevOps
engineer
and
you're.
A
Your
organization
has
like
around
a
thousand
JIRA
projects,
and
so
your
job
is
to
make
sure
that
every
gitlab
project
owner
is
using
the
organization's
custom.
Web
URL,
for
example.
So
they
have
to
make
sure
that
that's
consistent
across
all
of
the
projects,
but
you
still
want
the
you
know
all
the
project
owners
to
still
use
their
own
username
and
password,
for
example.
A
So
today
you
know,
Devin
has
a
couple
options
on
how
to
enforce
that.
Url
consistency.
You
know
they
could
either
do
it
all
manually.
You
know
go
through
each
project,
one
by
one.
You
know
maybe
send
out
an
email
to
all
project
owners.
But
again
you
don't
know
you
know
one.
That's
actually
all
going
to
happen,
but
we
also
have
this
feature
called
service
templates
right
now.
A
That
is
that's
the
possibility
to
use,
but
the
service
templates
feature
does
have
some
limitations,
so,
for
example,
like
so
service
templates
only
allow
for
new
projects
to
inherit
values
of
the
template
settings
so
and
then,
once
these
set
values
it
might
be
get
overridden.
So,
for
example,
if
a
project
project
owner
overrides
that
web
URL,
like
I
mentioned,
you
know,
there's
no
way
for
that
owner
to
one
see
what
settings
have
been
see,
that
it's
been
overwritten
and
two
there's
no
way
for
that
admin
to
kind
of
force.
A
Inheritance
down
again,
so
that's
where
this
actually
before
I
go
there.
If
we
also
take
a
look
at
the
data,
we'll
see,
you
could
see
that
a
lot
of
our
users,
you
know,
have
well
over
a
thousand
JIRA
active
here
at
projects.
So
that's
a
huge
problem.
If
you
know,
if
there's
a
manual
process
involved
there
too,
in
order
to
update
each
one
of
those
projects.
So
that's
where
our
this
mass
integration
at
a
group
and
instance,
level
is,
can
be
very
helpful.
A
A
So
we're
going
to
do
this
by
basically
bringing
integrations
that
you
currently
see
at
the
project
level
to
the
group
level
and
to
the
instance
level.
So
here's
just
a
little
quick
chart
and
a
fun
little
fun.
Little
fact
that
I
learned
recently
from
Arturo
that
you
could
actually
create
these
kinds
of
diagrams
with
in
markdown
in
in
an
issue.
So,
there's
a
little
learn
more
link
here,
if
you're
interested
so
now
to
kind
of
go
into
some
of
the
current
work.
A
That's
in
progress,
so
I
have
an
issue
here
which
I'll
just
bring
up
so
in
this
issue.
This
is
our
single
source
of
truth
for
all
the
designs
and
kind
of
showing
the
ideal
state
of
this
new
update.
So
we
went
back
and
forth
a
little
bit
on
how
to
communicate
these
designs
just
because
there's
so
many
designs
in
so
many
different
states.
A
So
what
I
ended
up
doing
is
I
broke
the
designs
down
by
our
user
stories
that
we
want
to
solve
for
and
I
have
a
Sigma
link
that
kind
of
ties
to
each
one,
these
user
stores
and
sometimes
a
figment
prototype
addresses
you
know
more
than
one
user
story.
So
if
I
click
on
one
of
these,
for
example,
I'll
just
give
everyone
in
just
a
quick
preview
of
this.
A
This
is
a
figma
one
of
the
figma
user
stories,
that's
available
to
anyone
to
kind
of
come
in
and
look
at
and
I
found
this
a
little
bit
easier
to
navigate
and
follow
than
than
just
looking
at
single
static
screens
without
context
of
the
actual
flow
that
you
might
want
to
go
down.
So
this
is
I
won't
go
down
the
full
flow,
but
this
is
a
quick
example
of
what
the
integrations
of
JIRA
integration
might
look
like
at
the
instance
level.
A
A
A
So
in
order
to
break
this
down,
I
broke
it
down
kind
of
we
created
many
issues,
other
issues
and
then
it's
kind
of
broken
down
into
kind
of
these
three
sections,
which
is
new
functionality.
Ui
polish,
which
is
a
lot
of
that,
involves
just
kind
of
making
sure
that
the
UI
components
that
we're
using
are
now
updated
are
using
the
latest
from
ru
pajamas.
You
like
it
and
then
there's
another
kind
of
section,
that's
more
involved
with
about
getting
feedback
and
then
just
validation,
a
solution,
validation.
A
So
in
this
breakdown
for
the
new
functionality,
there's
a
lot
of
back
and
issues
that
have
been
created.
There's
a
some
more
design
related
issues
that
kind
of
have
some
of
the
more
low
fidelity,
wireframes
and
prototypes.
That
I
mentioned
here
in
the
undead
mock-up
issue
and
there's
also
an
issue
that
we
created,
which
is
called
just
NBC
issue,
which
is
discussing
with
the
developers
how
we're
going
to
break
this
down
into
the
smallest
possible
useful
update
that
we
could
that
we
could
deliver.
A
So
that's
still
in
progress
and
then,
like
I
mentioned,
for
the
UI
polish.
This
has
been
broken
down
at
a
lot
of
smaller
issues.
So
if
I
go
back
to
just
showing
the
design,
so
you'll
see
that,
for
example,
the
labels
the
forms
instead
of
being
on
the
left,
they
should
be
on
above
the
form
field
or
the
input
field
like
we
like.
We
have
in
pyjamas.
A
So
there's
a
lot
of
little
updates
like
that
that
that
we
just
need
to
update
the
UI
and
just
bring
it
bring
it
make
it
consistent
with
what
we
have
in
pyjamas.
So
those
are
other
smaller
issues
that
can
be
worked
on
all
in
in
parallel,
independently
of
this
actual
update,
and
then
we
also
have
this
feedback
and
validation
so
as
I
was
working
through
this
through
these
prototypes
in
this
end
end
mock-up
issue.
A
There
is
some
there's
some
interactions
and
there
may
be
some
UI
components
that
I
wasn't
sure
that
we
should
be
that
it
could
be
leveraging
or
should
be
using
or
maybe
I
was
also
questioning,
whether
there's
a
way
to
do
certain
things.
So
I
created
this
validation
I'm.
Sorry,
this
more
of
a
feedback
issue
that
just
specifically
describes
some
of
the
interactions
that
that
I
was
questioning.
So
here's
an
issue
just
for
a
UI
exploration
for
what
it
would
look
like
if
you're,
inheriting
it
versus
overriding
four
fields
at
the
project
level.
A
So
so
there's
some
discussion
here
again
and
again
a
lot
of
these
issues.
It's
nice
to
be
able
to
break
them
down,
so
you
could
work
on
them
independently
from
from
the
from
the
bigger
update
and
then
so
once
we
come
to
kind
of
some
agreement
or
some
conclusion
on
some
of
these
exploration
issues.
I'll
then
go
back
and
update
our
single
source
of
truth
with
and
all
the
prototypes
yeah
and
then
so,
as
also
as
a
follow-up
issues.
A
So
once
we're
fairly
confident
more
than
80%
I
would
say
that
this
update
is
something
that
everyone's
been
waiting
for
for
a
while
and
that
and
that
we
know
it's
going
to
provide
value.
But
we
still
this
follow-up
issue
that
I
created
just
to
validate
the
solution.
So
once
we
do
our
first
release,
you
know
it's
going
to
be
good
to
actually
speak
with
someone.
A
That's
currently
using
the
service
template
features
heavily
and
seeing
how
they're
either
transitioning
to
this
new
way
of
doing
the
integrations
that
the
instance,
the
group
level
or
and
they're
just
getting
overall
feedback
on.
You
know
seeing
how
they're,
how
they're,
how
they're
adopting
it
so
that's
I,
think
that's
it
yeah.
So
that's
it.
A
What
I
have
for
for
this
UX
showcase
I
want
to
thank
everyone
on
the
ecosystem
team
for
all
their
great
feedback
and
thoughtful
comments,
and
also
I
want
to
thank
Tori
and
Jeremy
for
helping
me
explore
some
of
those
UI
patterns
or,
and
one
other
thing,
if
you're
more
in,
if
you're
interested
in
ecosystem
group
I
recommend
you
read
up
on
our
stage
group
page
and
our
stage
stage.
Direction
page
they've
recently
been
updated
and
our
team
has
grown
so,
which
is
very
exciting
anyways.