►
From YouTube: GitLab 13.6 Kickoff - Create:Ecosystem
Description
Atlassian Marketplace app: https://marketplace.atlassian.com/apps/1221011/gitlab-com-for-jira-cloud?tab=overview&hosting=cloud
Improve UX for initial setup (Epic): https://gitlab.com/groups/gitlab-org/-/epics/4354
Improve error messages when adding namespaces in Jira Connect App: https://gitlab.com/gitlab-org/gitlab/-/issues/13019
Add a more user-friendly way to select namespaces in Jira Connect App: https://gitlab.com/gitlab-org/gitlab/-/issues/13020
Sync existing merge request data when a namespace is added to Jira Connect App: https://gitlab.com/gitlab-org/gitlab/-/issues/13074
Add MAU data for Ecosystem Usage Ping: https://gitlab.com/gitlab-org/gitlab/-/issues/225678
A
A
So
the
first
issue
that
we're
talking
about
today
is
improving
the
ux
for
the
initial
setup
of
our
connect
application
in
the
atlanta
marketplace.
So
this
is
the
listing
page
gitlab.com
for
jira
cloud.
We
just
shipped
a
bunch
of
improvements
to
this
page,
trying
to
make
it
a
lot
more
clear
what
it
is,
how
to
use
it,
how
to
set
it
up.
A
But
there
are
some
problems
with
the
application
itself,
and
so
here's
an
epic
that
we
have
with
14
issues
in
it
to
work
on
this
initial
setup
experience,
but
specifically
in
13
6,
one
of
the
ones
that
we're
looking
at
adding
is
improving
the
error
message.
When
you
add
a
namespace,
so
you
can
see
a
demo
that
I
recorded
here
when
you
add
a
thing.
It
just
gives
you
this
kind
of
generic
invalid
namespace
error,
which
doesn't
tell
you
a
lot
or
how
to
use
it.
A
Additionally,
we
want
to
add
a
more
user-friendly
way
to
select
those
namespaces.
This
is
the
same
demo,
but
showing
a
user
a
list
instead
that
can
autocomplete
of
those
namespaces.
So
it's
clear
when
you're
adding
a
namespace
to
jira
what
namespaces
do
you
have
access
to?
That's
a
big
question,
especially
for
for
those
who
aren't
familiar
with
the
term.
That's
a
bit
of
a
jargon
term
right,
a
namespace
is
really
familiar
for
some
people,
but
for
many,
it's
kind
of
confusing
so
showing
what
namespaces
are
available
will
make
that
a
lot
better.
A
Additionally,
we
want
to
be
able
to
sync
existing
mr
data
when
a
namespace
is
added
to
the
jira
connect
app.
There
are
a
couple
of
pieces
here,
so
one
we
want
to
be
able
to
sync.
This
merge
request
data
in
general.
It
doesn't
do
a
good
job,
picking
up
all
of
that
existing
data.
So
we
need
the
ability
to
add
that
so
the
first
step
is
getting
that
synced
when
the
namespace
is
added
to
the
connect.
A
App
that'll
also
allow
us
to
do
other
things
like
allowing
a
manual
data
sync
as
well,
so
that
that
integration
will
allow
you
to
show
all
of
your
mr
data
inside
jira,
so
they
have
a
component
in
that
ui
called
the
developer
panel
and
in
the
developer
panel.
It
shows
you
a
number
of
different
pieces,
so
you
you
can
see
the
branch
data
like
the
commits
the
merge
requests,
we're
also
adding
build
information
and
feature
flag
information
and
deployment
information
over
the
next
few
milestones
so
being
able
to
sync
the
merge
request.
A
Data
in
would
be
awesome
and,
finally,
we're
also
adding
monthly
active
user
data
for
ecosystems
overall
usage
ping.
So
we
have
a
lot
of
different
pieces
in
the
usage
ping,
payload,
specifically
tracking,
all
of
the
different
installations
of
various
integrations.
Now
this
is
anonymized
data,
we're
just
seeing
a
count
of
the
number
of
integrations
that
are
active,
but
what
we
want
to
see
is
how
many
users
are
using.
Those
integrations
right
because
integrations
are
with
a
project.
A
So
knowing
how
many,
in
this
case,
jira
projects
have
been
or
jira
integrations
have
been
added
to
projects
is
awesome,
but
how
many
users
are
on
each
of
those
projects,
if
it's
only
one
user
per
project,
which
is
probably
not
the
case,
but
if
it's
only
one
user
per
project
versus
a
thousand
users
per
project
like
that
makes
a
really
big
difference
in
how
many
people
are
actually
using
these
things.
So
that's
it
for
thirteen.
Six
can't
wait
to
see
you
in
thirteen
seven
and
have
a
great
day.