►
From YouTube: GitLab 13.10 Kickoff: Ecosystem
Description
Add Issue Detail view from Jira Issue List - https://gitlab.com/groups/gitlab-org/-/epics/5058
Document Usage of Jira Connect application with Self-hosted GitLab - https://gitlab.com/gitlab-org/gitlab/-/issues/268278
Expand Atlassian Connect App to function as a proxy for self-managed GitLab - https://gitlab.com/gitlab-org/gitlab/-/issues/321401
Investigate automatically installing Jira Connect App from GitLab - https://gitlab.com/gitlab-org/gitlab/-/issues/299482
A
Hey
there,
I'm
patrick
dooley,
I'm
the
senior
product
manager
for
gitlab's
ecosystem
group
and
we're
here
today
for
the
1310
kickoff.
So
let's
talk
about
the
work
that
we're
going
to
be
doing
over
the
next
month,
so
first
up
we're
going
to
continue
work
on
the
issue
detail
view.
That's
part
of
our
jira
issue
list.
It's
a
premium
feature
that
we
added
a
little
while
back
as
a
recap.
It's
this
view.
A
So
if
you
have
a
jira
integration
and
you're
a
premium
or
ultimate
user,
you
can
add
an
issue
list,
so
it
shows
those
issues
from
your
integrated
jira
project
inside
of
gitlab,
which
is
really
cool.
It
allows
you
to
spend
less
time
context
switching
between
those
two
tools
when
you're
using
them
together.
Now
the
problem
is
this:
just
sends
you
to
jira
today,
so
you
see
this
list
of
issues,
but
you
can't
do
much
with
them.
So
the
first
iteration
is
to
add
a
detailed
view.
A
Inside
of
gitlab,
the
idea,
here
being
that
we
want
developers
who
are
using
gitlab
for
the
majority
of
their
tasks
to
be
able
to
stay
in
gitlab
for
project
management
if
your
job
is
not
as
a
project
or
product
or
program
manager
and
your
job
is:
writing
code.
You're,
probably
better
served
staying
in
gitlab
than
having
to
go
mess
with
jira
for
the
majority
of
your
usage.
A
So
we
want
to
add
a
detailed
view
to
this
list
so
that
when
you
click
on
these
issues,
they
take
you
to
a
detailed
view.
You
can
still
go
view
it
in
jira,
but
you
should
be
able
to
keep
track
of
your
work.
See
the
details
of
an
issue
edit.
That
issue
comment
on
it:
change
the
status,
all
the
things
you
would
normally
do
as
a
developer
from
inside
a
gitlab.
A
A
We
also
want
to
work
on
the
jira
connect
application.
Some
more
we've
spent
a
ton
of
time.
Improving
that
experience
the
setup
process.
The
installation
process
is
much
much
much
better
is
night
and
day
different
from
where
it
was
nine
months
ago,
and
we
really
like
this
experience,
but
it
doesn't
work
out
of
the
box
with
self-managed
today.
So
we
have
a
couple
of
things
that
we
want
to
look
at
to
help
solve
that
one.
A
There
are
two
workarounds:
if
you're
using
self-managed,
gitlab
and
you're
using
jira
cloud,
you
are
able
to
go
into
either
developer
mode
or
you
can
publish
your
application
privately
on
the
atlassian
marketplace.
So
we
need
good
documentation
for
both
of
these
because
they
work.
Today
we
have
a
number
of
customers
who
have
found
these
on
their
own,
and
we
want
to
make
sure
that
it's
very
clear
how
you
can
do
that
if
you'd
like
to
additionally,
we
want
to
expand
the
connect
application
and
explore
playing
with
it
as
a
proxy.
A
A
That'll
connect
the
atlassian
marketplace
directly
with
your
self-managed
instance,
but
if
you're,
okay,
with
using
gitlab.com
as
a
proxy
and
that's
an
acceptable
solution
from
your
security
and
and
privacy
posture,
that's
awesome.
It
makes
it
even
easier
because
then
you
can
just
use.
What's
already
on
the
atlassian
marketplace,
store
and
it'll
be
a
one-click
install
to
get
you
set
up.
So
between
those
three
options.
We
think
that
should
cover
everyone
who's
on
both
gitlab.com
and
get
lab
self-managed,
who
is
using
jira
cloud?
A
The
other
piece
that
we
really
want
to
look
into
is
automatically
installing
the
jira
connect
application
from
gitlab.
So
right
now
there
are
two
halves
to
this
integration.
One
is
on
gitlab,
you
go
to
a
project,
you
go
to
the
settings
integrations
jira
page
and
you
can
set
up
an
integration
between
gitlab
and
jira.
The
other
way
around,
though,
is
also
really
valuable.
When
you
add
the
connect
application,
jira
watches
gitlab
for
changes
and
takes
those
and
populates
them
inside
of
the
jira
developer
panel.
A
So
on
an
issue,
you'll
see
a
developer
panel
on
the
right
hand,
side
that
shows
branch
data
commits
pipeline.
Sorry,
deployment
data
feature
flag
data,
like
all
of
those
pieces
of
data,
are
available
directly
inside
of
jira,
which
is
awesome,
but
you
have
to
set
up
two
separate
integrations
for
that
to
be
true.
So
what
we
would
love
to
see
is
when
you're
setting
up
your
gitlab
integration
with
jira
gitlab
can
reach
out
to
jira
and
have
the
integration
on
that
end
set
up
automatically.
A
So
we
want
to
look
into
this.
We
don't
actually
know
if
it
is,
is
feasible
if
it's
technically
possible,
so
we're
going
to
spike
into
this
and
start
playing
with
it
and
we'd
love
to
see.
If,
if
we
can
get
it
working
and
if
not,
then
we
can
send
some
feedback
to
atlassian
to
see
if
we
can
get
the
appropriate
api
set
up.
A
So
that's
it
for
1310.
We're
really
excited
to
add
the
detail
view
we're
excited
to
get
more
people
on
the
connect
application
and
we
think
that
we're
we're
getting
to
a
point
where
the
integration
between
gitlab
and
jira
can
really
start
to
go
exciting
places
and
can
be
great
for
for
the
developers
who
are
using
both
platforms.