►
From YouTube: GitLab 12.5 Kickoff - Ecosystem
Description
Patrick Deuley (Product Manager, Ecosystem) talks through the work the Ecosystem group will be doing for the 12.5 release, and gives some background on the Group-level integrations with Jira project.
Leave your feedback on the Jira work here: https://gitlab.com/groups/gitlab-org/-/epics/2025
A
A
First,
we've
got
a
bread
crumb
that
is
broken
on
the
integrations
page,
so
in
an
individual
project,
if
you
have
an
integration,
enabled
you're
on
that
integrations
configuration
page.
If
you
click
on
the
link,
it's
going
to
the
wrong
thing
and
it
just
reloads
the
page
so
we'll
get
that
fixed
and
updated.
So
it
goes
to
the
right
link
so
that
you
can
navigate
appropriately
there's
also
a
500
error,
that's
getting
thrown
if
you've
got
matter,
the
matter
most
service
installed
and
your
self
hosted
instance.
A
A
We're.
Also
looking
at
adding
usage
ping
data
around
our
project
services.
So
we
use
usage
ping
data
to
better
understand
what
our
users
are
consuming,
what
features
matter
to
them,
how
those
things
are
working,
so
we
can
better
think
about
things
like
how
we
prioritize
or
how
things
need
to
scale.
So,
as
we
spend
more
time,
working
on
the
various
project
integrations
and
other
integrations,
we
need
to
know
more
about
how
our
customers
are
using
this.
A
So
we're
gonna,
add
a
new
category
inside
of
the
counts
part
of
the
payload
for
project
services,
and
there
will
list
the
number
of
projects
currently
using
each
project
service
so
for
those
are
curious
and
unfamiliar
with
the
usage
bring
in
your
get
lab
instance.
If
you
go
to
the
admin
area,
go
to
settings
metrics
and
profiling
under
usage
statistics.
A
A
Finally,
I
want
to
take
a
little
bit
talking
about
JIRA,
so
we're
currently
working
on
JIRA
group
level
integrations
and
part
of
the
12.5
process
for
us
is
to
start
breaking
ground
on
some
of
the
back-end
architecture.
For
it
to
learn
more
about
that,
we
can
look
at
this
epic,
so
I'll
even
link
to
this.
In
the
description,
we've
got
an
epic
that
we're
working
on
it's
an
MVC
for
creating
group
level,
integration
with
JIRA.
So
a
little
bit
of
background
JIRA
is
our
most
popular
integration.
A
A
lot
of
people
use
it,
and
some
of
those
people
have
pretty
large
installations.
So
we've
talked
to
people
with
hundreds
or
even
thousands
of
projects
and
when
they're,
using
JIRA
as
their
primary
task
tracking
system
they'll
have
to
integrate
that
200
times
right.
So
if
you've
got
200
projects
every
single
time,
you
want
to
integrate
JIRA,
you
have
to
go
and
add
that
integration
to
that
project.
So
you
can
solve
this,
partly
with
service
templates,
but
service
templates
only
apply
to
new
projects.
They
also
don't
change
over
time.
A
So
if
you
decide
to,
for
example,
rotate
the
password
as
crazy
as
that
may
sound,
you
would
have
to
rotate
that
password
200
times.
So
what
we'd
like
to
do
is
take
that
same
type
of
functionality
that
we
have
at
the
project
level
and
add
it
at
the
group
level.
By
doing
this,
if
you
have
200
projects
but
they're
all
in
one
group,
you
should
only
have
to
configure
that
integration
in
one
place.
So
there
are
a
couple
of
reasons
for
this
beyond
the
obvious
time
savings.
A
Additionally,
there's
some
work.
That's
been
done
looking
at
taking
this
to
the
service
template
level
or
the
instance
level
as
well.
But
again
this
is
a
great
place
to
start.
It's
a
great
MVC
that
takes
this
and
solves
a
large
chunk
of
pain
for
a
large
chunk
of
users
and
we
think
we'll
save
some
people
a
whole
lot
of
time.