►
From YouTube: GitLab 15.5 Kickoff - Ecosystem:Integrations
Description
Planning Issue: https://gitlab.com/gitlab-org/ecosystem-stage/team-tasks/-/issues/167
Jira Integration Docs: https://docs.gitlab.com/ee/integration/jira/
GitLab for Jira App: https://marketplace.atlassian.com/apps/1221011/gitlab-com-for-jira-cloud?tab=overview&hosting=cloud
GitLab API Vision Working Group: https://about.gitlab.com/company/team/structure/working-groups/api-vision/
A
Our
first
theme
that
we're
looking
forward
to
in
15.5
is
focus
on
completing
the
jira
proxy
for
self-managed
users
of
the
git
lab
for
jira
app.
This
is
exciting,
as
we've
been
working
to
iterate
on
this
over
the
past
several
milestones,
and
while
we
have
discovered
a
few
remaining
issues
in
the
past
month,
we
have
high
confidence
that
we'll
finally
be
releasing
this
feature
in
15.5.
A
With
this
update,
when
enabling
the
gitlab
for
jira
app
you'll
see
a
toggle
option
to
choose
between
githlab.com
and
gitlab
to
self-managed
and
then
you'll
be
able
to
as
a
gitlab
self-managed
user
link
your
namespace
and
and
complete
the
configuration
of
the
app
as
a
result
of
enabling
this
app,
you
will
be
able
to
integrate
with
the
jira
development
panel
and
sync
commits
merge,
requests
and
branches,
and
you
can
transition
issues
from
a
commit
or
Mr,
and
you
can
update
jira
issues
with
commit
messages,
and
it's
worth
noting.
A
A
So
in
15.5.
What
we're
planning
on
doing
here
is
is
consolidating
our
node
or
notifications
integration
into
the
slack
app.
So
you
can
kind
of
get
an
example
here
of
what
the
configuration
page
might
look
like,
and
this
should
make
it
a
little
bit
simpler.
Rather
than
having
to
choose
between
Integrations,
you
can
get
all
the
power
of
our
slack
Integrations
Within,
the
single
integration,
we'll
note
that
this
would
start
with
support4.com
users,
but
we'll
be
exploring
in
the
future.
How
to
add
support
for
self-managed.
A
Moving
on
to
our
third
theme,
45.
we're
looking
at
how
to
improve
encryption
for
web
Hooks
and
General
Security
around
our
web
Hooks,
and
the
main
area
of
focus
here
will
be
around
how
to
mask
the
inputs
provided
for
web
callback.
Urls
a
URL
could
include
sensitive
information
like
passwords
or
headers.
That
should
not
really
be
shared
even
across
the
team
by
viewing
it
in
the
UI
or
the
settings
for
those
who
have
access
to
it.
That's
better
to
maintain
those
credentials
in
a
safe
place
and
password
manager
or
secure
credential
manager.
A
A
Great
and
the
last
theme
that
I
wanted
to
touch
on
for
15.5
is
automated
API
docs
generation.
Our
team
has
been
very
much
engaged
with
our
API
working
group,
which
is
focused
on
improving
the
quality
and
usability
of
gitlab
apis
for
our
customers,
Partners
contributors,
as
well
as
our
own
internal
product
teams,
so
automated
API
docs
generation,
it's
an
area
that
we
feel
we
can
make
a
really
significant
impact
with
small
iterations
and
in
15.5,
we'll
be
exploring
how
to
expose
our
apis
in
an
open,
API
spec
in
an
automated
fashion.
A
This
will
provide
automated
or
programmatic
access
to
apis,
and
it
will
help
to
improve
consistency
across
our
apis,
so
yeah
we're
looking
forward
to
all
these
improvements.
Hope
that
you
are
as
well.
I'll
share
some
links
that
to
some
of
the
things
I've
discussed
today
in
the
description
and
as
always,
we
look
forward
to
hearing
feedback
in
our
issues
so
feel
free
to
reach
out.