►
From YouTube: GitLab 12.9 Kickoff - Enablement:Ecosystem
Description
Kicking off Ecosystem's 12.9 work!
View our work board here: https://gitlab.com/groups/gitlab-org/-/boards/1167634?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aecosystem
A
A
The
first
thing
I
want
to
talk
about
is
a
really
big
piece
of
work
that
if
you've
watched
the
last
couple
of
kickoff
videos,
we've
been
talking
about
for
a
while,
so
we're
working
on
a
big
piece
of
work,
that'll
bring
integrations
to
the
instance
and
group
level.
So
if
you
have
say
thousands
of
projects
right
now,
what
you
have
to
do
is
integrate
each
one
of
those
projects
individually.
So
let's
say
you
have
JIRA
you're
using
JIRA
for
your
project
management.
You're
gonna
have
to
set
up
that
integration.
A
Thousands
of
times
some
of
our
users
have
done
things
like
set
up
a
bunch
of
API
scripts
to
go
through
and
manage
that.
But
that's
just
not
the
right
way
to
do
things.
So
the
epic
that
we've
been
working
on
will
bring
this
integration
so
that
you
can
do
it
once
at
the
instance
level,
and
then
all
projects
on
that
instance
will
use
it
or
at
the
group
level.
So
this
particular
work
item
is
looking
at
the
admin
page
for
the
instance
level,
so
adding
that
right
now
we
have
it.
A
Then
we
also
have
a
piece
of
work
for
setting
up
inheritance
for
project
integrations
at
the
instance
level.
So
the
idea
being
that
instance
level
integration
works,
you've
installed
it
it's
going
now.
The
projects
themselves
need
to
inherit
those
configuration
settings.
So
this
is
the
work
item
for
that
and
we
have
a
group
level
integration
MVC.
So
right
now,
because
of
some
necessities
of
how
our
back-end
works,
we've
been
working
on
the
instance
level
integration.
A
This
is
the
MVC
for
the
group
level,
integration
so
taking
that
same
functionality,
those
same
features
and
in
the
same
code
base
and
then
working
in
to
also
work
at
the
group
level,
then
because
of
how
service
templates
historically
have
worked
and
as
a
really
brick
brief
recap.
Service
templates
live
at
the
instance
level,
which
means
they're
not
available
for
people
that
get
lab
comm,
but
for
an
admin
of
a
self-hosted
environment
you
can
create
service
templates
and
when
you
create
a
new
project,
that
project
will
have
the
settings
from
the
service
template
applied.
A
Now
what
happens
if
you
change
your
say
token,
for
your
integration,
you've
got
to
go
change
it
on
all
of
those
projects
and
then,
additionally,
existing
projects
don't
benefit
from
that.
So
the
plan
is
to
migrate
towards
integrations
like
these
inherited
values,
integrations
and
move
away
from
service
templates.
So
we
want
to
put
together
a
a
warning
on
the
service
template
page
warning
admins
that
this
feature
is
deprecated
or
being
deprecated.
Soon
we
don't
have
a
timeline
for
that.
We
don't
have
a
schedule
really.
A
We
want
to
put
this
on
there
to
give
people
as
much
awareness
as
possible
and
try
to
solicit
some
feedback
on
that.
And,
of
course,
if
you
have
any
feedback
reach
out,
leave
a
comment
get
in
touch
with
the
team
we'd
love
to
hear
more
about,
but
how
you're
using
service
templates
and
why
that
that's,
the
better
choice
for
you
and
finally,
some
more
backend
work.
We're
doing.
We
need
to
add
the
instance
attribute
to
the
service
model,
and
this
will
allow
us
to
do
some
more
of
the
work
that
is
required
for
getting
together.
A
Those
instance
level
integrations,
so
that's
kind
of
the
first
major
theme,
so
we're
working
through
a
number
of
issues
that
all
have
to
do
with
these
instance
level
integrations
and
we're
hoping
that
in
12:9
we
can
get
the
majority
of
the
instance
level
work
done
and
out
to
the
users
and
then
in
12
10
and
13
Oh
will
I
be
able
to
roll
that
out
at
the
group
level
as
well.
So
the
last
piece
of
it
is
some
data
collection.
We
need
to
add
telemetry
and
to
usage
ping,
for
instance,
level
integrations.
A
So
as
we
roll
all
that
work
out
we'll
be
able
to
capture
that
data
and
see
how
people
are
using
it
and
better
understand
where
we
can
focus
our
time.
So
that's
theme.
One
theme
two
is
of
course
JIRA
is
a
high
priority.
That's
what
kicked
off
all
of
this
group
level
work
in
the
first
place,
but
additionally,
we've
got
some
problems
so
about
a
month
ago.
A
A
We
wanted
to
try
to
solve
all
four
of
these
problems
with
a
single
design
solution,
so
a
lot
of
them
were
asking
for
customization
wanted
to
make
changes
to
what
the
the
template
for
comments
looked
like
in
JIRA
and
so
Lee
bore
our
UX
designer
has
done
a
great
job
and
of
thinking
through
those
and
working
through
a
single
solution
that
tries
to
fit
all
four
and
I.
Don't
know
if
it'll
work,
but
in
the
spirit
of
iteration.
A
A
It's
kind
of
a
tough
nut
to
crack,
but
we
think
we've
got
a
plan
to
go
forward,
so
in
12:9
we'll
be
trying
to
implement
that
first
version
of
that
and
the
idea
of
being
again
to
recap:
I
know:
we've
touched
on
this
in
a
couple
of
kickoffs
talking
about
transition
IDs,
but
the
problem
with
transition.
Ids
right
now
is
I.
Don't
think
I
have
a
screenshot
in
here.
I
do
so
right
now.
The
way
transition
IDs
are
configured
is
just
with
a
with
integer
right
and
that's
just
not
user-friendly.
A
It
doesn't
make
any
sense
if
you're
really
really
familiar
with
JIRA.
This
maybe
make
some
sense
to
you.
I
can
tell
you
I've
been
a
JIRA
admin
at
a
couple
of
different
jobs
for
a
number
of
years.
I
had
no
idea,
transitions
were
integers,
I
I
would
have
never
known
that
and
I
and
it
actually,
when
I,
when
I
first
moved
in
this
role
and
I
had
to
learn
about
the
the
job
I
was
supporting.
A
I
had
to
go,
read
about
this
in
the
JIRA
Docs
and
understand
what
exactly
that
even
was
so
that's
not
friendly.
So
we've
got
some
some
concept
designs
for
grabbing
the
transition
ideas
programmatically
through
the
API,
surfacing
them
air
them
in
there.
So
you
can
more
easily
select,
what's
appropriate
for
you
and
then
in
other
work.
We
have
a
couple
of
items
that
we'll
be
touching
on.
A
Over
the
last
few
releases,
we've
had
we've,
we've
worked
on
web
hook
limits
for
projects,
so
that
was
to
limit
possible
abuse
and
to
limit
or
to
better
support,
uptime
and
availability
of
the
application.
There
were
a
couple
of
instances
where
people
had
accidentally
added
thousands
of
web
hooks
for
their
project,
and
so
we
needed
to
be
able
to
have
some
controls
around
that.
So
this
work
continues
that
and
we're
gonna
add
web
hook
limits
for
groups
as
well,
and
in
this
thread
you
can
kind
of
see
some
of
the
detail
behind
it.