►
From YouTube: GitLab 13.9 Kickoff - Create:Ecosystem
Description
Create MAU tracking for Ecosystem integration usage
- https://gitlab.com/groups/gitlab-org/-/epics/5181
Add Issue Detail view from Jira Issue List - https://gitlab.com/groups/gitlab-org/-/epics/5058
Simplify Jira integration/installation flow - https://gitlab.com/gitlab-org/gitlab/-/issues/225803
A
Hello
and
happy
new
year,
I'm
patrick
dooley,
I'm
the
senior
product
manager
for
gitlab's
ecosystem
group
and
we're
here
for
our
13-9
kickoff.
Let's
talk
about
the
work
that
we're
going
to
do
over
the
next
month,
so,
first
off
for
months
now,
we've
been
trying
to
track
mao
data,
so
the
monthly
active
users
of
our
integrations.
We
have
about
30
integrations
today
and
we
really
want
to
know
how
many
individual
users
are
are
using
those
things
actively,
and
so
we've
had
about
four
different
attempts
to
try
to
get
this
out
of
the
database.
A
It
has
been
a
really
tough
road
thanks.
So
much
to
our
awesome
team
who've
been
working
very
hard
to
try
to
figure
this
out.
We've
had
two
other
teams
pitch
in
with
advice,
and
it
just
hasn't
hasn't
worked
out
so
far.
The
the
scope
of
it
is
so
large.
We
were
getting
timeouts
on
the
queries
and
it
and
it
didn't
work
very
well,
so
we're
changing
direction.
A
A
A
So
after
that
we're
breaking
ground
on
the
issue
detail
view
we've
talked
about
this
before
this
has
been
a
thing
that
we've
been
kicking
around
for
a
while.
We
did
an
mvc
about
six
months
ago,
where
we
created
the
jira
issue
list.
But
since
then
it's
just
been
a
static
list
of
those
issues.
When
you
click
on
them,
it
sends
you
to
jira.
So
we
want
to
start
expanding
that
we've
recently
closed
up
work
on
expanding
our
jira
connect
application.
A
So
with
that
done,
we
want
to
flip
back
over
to
gitlab
and
expand
the
functionality
here.
So
this
will
allow
you
to
see
the
details
of
a
jira
issue
when
you
click
on
it.
We're
going
to
start
with
read
only
so
we'll
just
grab
the
the
details
of
that
issue
and
display
them
in
a
read-only
way,
and
then
we
can
iterate
beyond
that
by
adding
interactivity,
so
the
ability
to
comment
the
ability
to
edit
the
description,
change,
labels,
etc.
A
So
the
first
goal
will
be
just
that
read-only
version.
I
love
the
screenshot
because
it
makes
it
really
more.
I
I
love
this.
This
cracks
me
up,
but
the
idea
being
this
would
this
issue
here
and
you
can
see
indicated
by
the
little
icon
next
to
that.
That
is,
that's
actually
being
pulled
from
jira,
but
it's
it's
living
inside
a
gitlab
and
you're
viewing
it
inside
gitlab
and
then
finally,
we
want
to
start
looking
at
the
the
integration
and
installation
flow
between
jira
and
gitlab.
A
So
if
you're
using
gitlab.com-
and
you
are
using
duracloud
you'll
want
to
use
the
project
integration,
so
that's
going
to
your
project
integrations
and
then
jira
and
you'll
set
that
up
and
then
you'll
also
want
to
use
the
connect
app.
So
the
project
integration
will
ship
activity
data
to
jira,
so
it
kind
of
installs
a
web
hook.
So
any
activity
that
happens-
that's
relevant.
It
sends
it
over
to
jira
so
that
jira
can
see
that
in
the
activity
feed
the
connect
application
does
the
opposite.
A
So
it
goes
and
grabs
branch
data,
deployment,
data,
merge,
requests,
feature
flags
and
commits
and
all
of
those
pieces
of
data
it
then
surfaces
in
the
developer
panel
so
to
really
get
the
best
experience.
You
want
to
use
both
of
these,
but
they
have
to
be
installed
and
configured
separately.
So
what
we'd
like
to
look
into
is
how
do
we
merge
those
processes?
A
So,
when
you're
setting
up
the
integration
on
the
gitlab
side,
how
do
we
trigger
the
appropriate
apis
or
whatever
is
needed
to
get
the
connect
app
installed
and
vice
versa,
when
you're
installing
the
connect
app?
How
is
there
a
way
that
we
can
have
it
automatically
configure
the
integration
on
the
gitlab
side?
This
will
make
for
a
much
better
user
for
our
for
these
much
better
user
experience
for
these
users.
Millions
of
projects
are
configured
with
jira,
so
they're
in
there
reaching
out
to
atlassian
to
get
our
usage
stats
for
the
connect
app.