►
From YouTube: UX Showcase GitLab for Jira app
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Great
all
right,
hello,
everyone,
I'm
libor,
vance
senior
product
designer
from
the
ecosystem
group
and
today,
for
my
ux
showcase.
I
want
to
talk
about
that,
we're
doing
for
the
git
lab
for
jira
app,
so
this
app
currently
exists
in
the
atlassian
marketplace
and
when
it's
enabled
it
will
show
gitlab
activity
inside
of
jira
issues.
A
Excuse
me,
so
you
might
ask:
who
is
this
app
or
who's
using
this
app
or
who's
it
for
and
maybe
what
the
difference
is
between
this
app
and
our
existing
jira
integration
that
lives
inside
of
kit
lab?
A
So
to
answer
this,
I'm
going
to
do
a
quick
recap,
so
in
my
previous
yuck
showcase
I
showcased
the
work
that
we've
been
doing
to
extend
the
jira
integration
of
allowing
jira
issues
inside
of
gitlab,
so
the
persona
that
we
focused
on
for
that
was
sasha
the
software
developer,
whose
company
has
invested
in
it
last
year.
You
know
their
work
is
being
tracked
by
other
personas
like,
for
example,
project
managers
and
designers
inside
of
jira,
but
the
software
developers
still
wish
to.
You
know
work
in
gitlab
full-time.
A
So,
just
to
note
you
know
future
iterations
of
the
jira
integration
you
know,
may
expand
beyond
the
software
developer
persona,
but
for
now
it's
it's
primarily
focused
on
that
persona.
A
So
what
I've
also
done
here
on
this
slide
is
I've
converted
our
user
stories
into
a
job
story.
I
want
to
thank
marcel
for
for
pointing
that
out.
I
think
it's
a
little
bit
more
helpful
way
to
framing
the
story,
so
in
this
case
for
the
software
developer.
A
So
then,
on
the
image
on
the
right
here,
that's
what
what
what
the
jira
integration
looks
like
when
it's
enabled
and
when
the
viewing
of
the
jira
issues
is
enabled.
A
I
just
wanted
to
again
highlight
that
for
anyone
that
might
have
missed
that
from
the
last
showcase
so
now
moving
forward
with
the
gitlab
for
jira
app
in
atlassian's
marketplace,
we're
focusing
on
parker,
which
is
the
project
product
manager
persona,
so
pms
basically
want
to
understand
the
details
of
how
jira
issues
are
getting
resolved
without
having
to
leave
jira.
So
it's
kind
of
the
other
side
of
the
the
coin.
If
you
will
so
again,
pms
are
not
wanting
to
leave
jira
and
wanting
to
stay
and
do
their
work
there
and
still
understand.
A
What's
going
on
in
the
on
the
development
side
of
things
again,
the
job
story
for
the
project
manager
here
is
when
I'm,
when
I'm
trying
to
understand
the
status
of
an
issue,
I
want
to
see
all
the
relevant
information
in
one
place,
so
I
don't
have
to
spend
valuable
time
looking
in
multiple
places
and
again,
the
image
on
the
right
here
is
an
example
of
what
the
gitlab
for
jira
app
looks
like
when
it's
enabled
so
when
it's
enabled
inside
of
jira
project
manager,
we'll
see
this
little
development
panel
that
shows
up
that
will
show
the
the
relevant
get
lab
activity
so
right,
there
you'll
see
like
a
gitlab
branch
or
commits,
and
some
other
information.
A
Let's
see
so
I
want
to
go
into.
Why
are
we
improving
this
and
more
importantly-
and
this
is
something
I
maybe
should
have
brought
up
in
previous
ux
showcases-
is
you
might
ask
you
know?
Why
are
we
focusing
on
integrations
in
the
first
place,
if
gitlab
is
the
one
tool
for
the
entire
devops
lifecycle?
A
So
to
answer
that,
you
know,
imagine
that
a
large
organization,
you
know
that's
heavily
invested
in
jira
for
many
years.
They
have
multiple
departments
and
they're
using
upwards
of
you
know
tens
of
thousands
of
jira
issues
or
that
they've
created
tens
of
thousands
of
juror
issues.
You
know,
and
their
engineering
team
primarily
uses
gitlab.
A
A
A
So
moving
on,
you
know,
looking
at
the
business
impact,
you
know,
we've
been
seeing
more
and
more
larger
organizations
interested
in
using
gitlab
in
conjunction
with
their
existing
setups,
and
then
here's
just
a
quote
that
I
kind
of
reused
from
the
last
ux
showcase,
which
is
from
a
sales
representative,
gitlab.
A
Let's
see
so
now
going
back
so
now
that
I've
talked
about
the
value
of
of
even
having
integrations
in
the
first
place.
I
want
to
go
back
to
why
we
should
improve
the
get
lab
for
jira
app
and
or
why
it
needs
improvement.
A
So
currently,
there's
only
five
percent
of
users
that
have
tried
to
install
the
app
were
successful,
which
isn't
many
so
here
are
some
reviews
that
I've
just
taken
a
screenshot
from
for
the
marketplace,
which
also,
I
think
we
can
definitely
improve
upon
here.
A
Let's
see
so
and
in
order
for
me
to
understand
what
was
going
on
and
why
the
success
installation
success
rate
was
so
low,
I
first
set
up.
I
first
tried
to
set
it
up
myself.
I
created
a
video
walkthrough
that
you
could
see
in
the
issue
here.
That's
linked,
and
I've
also
reached
out
to
support
to
see
if
there's
any
related,
older
support
issues
with
this
application.
A
I
just
want
to
call
out
and
thank
cynthia
and
the
rest
of
the
support
team
here
for
helping
me
point
pointing
me
in
the
right
direction
and
helping
me
surface
some
of
these
related
zendesk
issues
that
are
linked
as
well,
and
I
later
spent
some
time
installing
other
third-party
applications
that
were
listed
in,
like
the
top
rated
category
in
the
atlassian
marketplace
to
understand.
A
You
know
how
we
differ
from
from
the
from
like
a
a
better
experience
there
all
right
moving
forward.
So
after
doing
this
exercise,
I
came
up
with
some
recommendations
for
this
presentation.
I'm
only
going
to
highlight
the
top
three
that
I've
identified
so
number
one
would
be
enforcing
authentication.
A
So
this
screen
that
you
see
here
is
what
you
see
as
a
user
setting
up
the
app
for
the
first
time.
If
I
clicked
on
the
get
started
button
from
the
listing
page,
you
know
I
see
this
screen
here,
which
is
which
this
view
doesn't
really
help
me
understand
like
what
to
do
next.
I
might
not
even
be
familiar
with
what
a
namespace
even
is
so
there's
a
lot
of
lacking
of
maybe
some
help
text
that
could
fix
this,
but
it
also
doesn't
actually
mention
anything
about
that.
A
I
need
to
be
signed
signed
into
gitlab
in
order
to
proceed
as
a
user,
which
is
an
issue
here.
So
if
I
tried
as
a
user,
if
I
try
to
start
adding
some
name
spaces
on
this
screen,
I
get
the
following
message:
if
I'm
not,
if
I
wasn't
logged
in
so
the
message
also
doesn't
really
isn't
really
helpful.
It
doesn't
suggest
what
what
I
need
to
sign
into
and
and
where
I
should
even
do
that
or
how
do
I?
A
How
do
I
resolve
this
error
message
so
and
even
in
the
ideal
case,
if
I,
what
if
I
was
signed
into
gitlab,
let's
say,
for
example,
in
another
tab,
I
could
potentially
be
signed
into
my
like
a
different
gitlab
account
like,
for
example,
my
personal
account,
and
then
I
would
be
maybe
trying
to
add
a
namespace
here
for
my
work
account
and
I'd
be
very
confused
at
why.
I
don't
have
permissions
to
add
those
namespaces.
A
A
So
there's
so
one
one
way
to
fix
this,
or
one
of
the
recommendations
here
is
to
just
prompt
the
user
to
authenticate
first
before
allowing
them
to
even
do
any
tasks
if
they
don't
have
access
to
those
tasks
so
right
away.
We
could
reduce
a
lot
of
error
messages
right
here,
just
by
adding
a
quick
login
screen
or
login
prompt
and
then
next
you
know
what
we
could
do
once
the
user.
Once
you
are
logged
in
into
gitlab,
you
know
we
could.
A
We
could
explicitly
call
out
here
who
they're
logged
in
as
and
give
them
the
option
to
sign
out
if
they
need
to
and
re-login
into
with
their
gitlab
account.
A
Okay
moving
forward
here.
So
another
thing
or
another
problem
on
this
screen-
is
that
this
view
or
ui
really
makes
the
user
guess
on
what
they
should
input
in
this
field.
A
So
this
guessing
game
can
cause
also
a
lot
of
frustration
and
it
forces
the
user
to
leave
the
installation
flow.
So
what
they'll
probably
do
next
is
try
to
start
searching
for
some
documentation
on
what
they
should
put
even
into
this
form
field,
or
if
they
do
know
what
to
put
in
here,
then
they
still
have
to
leave
to
go
to
gitlab
to
maybe
copy
and
paste
their
namespace
to
put
into
this
field.
A
So
instead,
what
we
could
do
here
is
offer
a
more
like
a
user-friendly
input.
So
if
we
already
know
that
they're
logged
in
we
could
surface
the
available
namespaces
for
them
and
make
it
simple,
simple
click
action
for
them
to
add
the
namespace
and
link
it
to
their
to
their
jira
again.
Here
I
want
to
call
out
heinrich
from
the
plan
team.
A
When
I
was
working
through
this
and
then
lastly,
we
could
do
do
some
easy
improvements
here
on
just
improving
the
messaging
on
the
listing
page
and
then
there's
also
some
issues
here
that
some
of
the
security
certificates
weren't
up
to
date
so
making
all
those
things
changes
should
make
the
just
make
it
more
approachable
to
to
a
larger
audience,
and
this
here
is
a
preview
of
the
proposed
updates.
A
So
we'll
be
adding.
You
know
more
more
screenshots
of
how
how
it
works
and
then
highlighting
more
of
the
benefits
and
actually
who
it's
for
and
then
here.
I
also
want
to
call
out
craig
and
cormac
and
thank
them
for
for
all
their
help
on
on
the
copy
here
I
know
craig
just
was
thrown
into
this
last
minute,
so
I
think
thanks
for
that
and
then
moving
forward
again
here,
so
the
recommendations
that
I've
just
mentioned.
A
You
know
we're
working
through
right
now,
they're
in
development
and
there's
still
some
changes
being
made
there,
but
there's
also
looking
forward.
A
We
want
to
simplify
the
overall
installation
flow
for
the
jr
integration,
so
the
current
problem
is:
there's
there's
currently
three
ways
that
you
can
integrate:
jira
with
git
lab,
so
there's
the
git
lab
project
integration
that
we
have
right
now
then,
there's
like
this
atlassian
connect
app,
which
is
the
git
lab
for
jira
that
I
just
mentioned
that
I
just
talked
about,
and
then
we
also
have
the
jira
dvs
connector.
A
So
in
an
ideal
world
you
know
you
could
just
connect
or
approach
this
from
one
of
the
entry
points
set
it
up
once
and
then,
ideally
you
know
you,
wouldn't
you
wouldn't
have
to
do
any
kind
of
additional
setup
work,
so
that'll
be
some
work
that
I'll
be
working
through
on
the
next
later
milestone.
So
right
now
it's
scheduled
for
13.7
see
yeah.
I
guess
that's
all
that
I
have
for
this
ux
showcase.
A
B
Thanks
leeward
that
looks
like
you're.
You
found
a
bunch
of
meaningful
areas
to
update.
I
would,
I
would
assume
those
stars
will
increase.
C
Yeah,
I
do.
I
agree.
These
are
good
changes.
I
was
aware
of
the
five
percent
success
rate
on
the
connect
app,
which
is
just
heartbreaking.
Do
you
have
a
goal,
a
usage
goal
or
a
successful
completion
goal
post.
A
Good
question
yeah
good
question
chris.
I
know
we
have
an
issue
to
follow
up
on
this.
I
have
to
I'll
have
to
follow
up
with
patrick
on
what
our
our
goal
or
a
successful
goal
is,
but
I
think
right
now
I
think
the
bar
is
set
pretty
low.
So
I
think
anything
is
anything
we
do
here
is
it
will
be
an
improvement
but
yeah
as
far
as
a
specific
metric
that
we
want
to
hit
or
target?
C
Okay,
yeah,
I
think
that
they're,
I
think
we
have
access
to
data
around
average,
successful
completion
rates
for
other
plug-ins.
A
C
A
Yeah
yeah,
thanks
for
bringing
that
up
I'll,
make
a
note
to
to
bring
that
up
next.