►
From YouTube: UX Showcase Iterating on Import MVCs
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
So
our
goal
is
to
build
importers
that
are
customers
find
valuables
so
offering
importers
for
the
main
competitors
are
crucial
and
having
those
experience
on
point
is
important,
reliable,
so
our
importers
don't
always
succeed
and
when
they
fail
there's
little
guidance
for
the
user
on
steps
they
can
take
to
remedy
the
failure.
A
A
A
So
from
what
I
mentioned
in
the
previous
manage
ux
showcase
presentation,
we
did
user
testing
and
received
positive
feedback
from
users
on
the
new
experience
and
we're
excited
to
launch
this
in
the
upcoming
milestone
and
we
have
wrapped
up
the
av
experience
experiment
and
unfortunately,
it
didn't
go
as
well
as
we
had
hoped,
because
we
couldn't
accurately
measure
the
user
interactions
with
both
environments
current
and
new
experience.
A
So
basically
it
was
set
up
to
compare
apples
to
oranges
as
opposed
to
apples
to
apples
and
what's
cool
is
philip
gave
us
a
positive
review.
Tweet
had
a
nice
tweet
for
us.
A
Next
is
iterating
on
the
project
import
nbc,
so
first
up
is
canceling
project
imports,
we've
heard
from
our
users
that
they
would
like
the
ability
to
cancel
imports,
and
really
this
is
a
ux
necessity.
A
So
next
is
the
history
of
project
imports,
so
users
can
view
the
history
of
their
imports
from
all
collected
sources.
So
currently
the
user
is
able
to
view
project
import
history
of
a
single
source,
and
this
experience
is
limiting
if
a
user
wants
to
see
a
list
of
all
of
their
aggregated
important
projects.
So
in
this
instance,
it
requires
a
lot
of
switching
between
sources.
A
If
there
are
many
so
we're
creating
kind
of
a
one
place
for
a
user
to
go
in
to
see
again
all
of
the
projects
that
they've
imported
from
various
sources,
we
also
want
to
standardize
project
import
ux.
So
we
have
nine
import
sources
and
most
of
them
have
different
user
experiences.
A
I've
kind
of
pulled
out
some
drastic
ones
here
so
and
you
know,
while
our
main
focus
is
on
bitbucket
and
github,
as
those
are
the
most
used
import
sources,
we
still
need
to
consider
you
know
the
experience
for
the
remaining
importers.
So
once
we
nail
down
the
experience
for
github
and
bitbucket,
it
will
then
kind
of
trickle
down
to
the
remaining
importers.
A
A
A
So
to
the
right.
The
improvement
that
we've
made
we've
added
new
functionality
of
simply
copying
and
pasting
the
url
of
the
group
to
be
migrated
as
well
as
copy
and
pasted
the
personal
access
token,
making
it
much
more
easy,
much
more
convenient.
A
For
the
group
migration
nvc
experience,
I
have
laid
this
out
and
I'm
going
to
walk
you
through
it
through
the
experience
so
user
navigates
to
the
new
group
link
in
the
main
top
level
navigation
lands
on
the
new
group
creation
page,
and
they
learn
about
the
instructions
on
how
to
migrate
a
group,
and
then
they
have
to
go
to
settings
to
copy
their
personal
access
token,
and
then
perhaps
they
need
to
go
to
their
to
their
group.
A
Once
the
group
has
been
imported,
they
are
able
to
click
the
new
group
link
and
then
that
will
take
them
to
their
new
newly
created
group.
Page.
A
A
We
want
to
see
the
entire
tree
and
be
able
to
cherry
pick
what
you
want
to
import
so,
instead
of
just
importing
a
single
group
and
all
of
the
contents
we'd
like
to
you
know,
have
a
tree
that
they're
able
to
you
know,
select
and
again
cherry
pick
which,
what
which,
whichever
they
want
to
migrate
and
then
last,
is
migrate.
Only
the
epics
for
that
group
tree.
A
We
plan
on
mirroring
the
same
experience
as
project
imports,
so
you
know
tests
or
I'm
sorry,
cancel
group
imports,
view
history
of
imported
groups
and
just
to
create
a
similar
user
flow
to
project
imports.
So,
as
you
can
see
on
the
right,
we
have
import
projects
and
we're
using
kind
of
a
large
button
style
which
then
directs
you
to
the
particular
new
project
creation,
page
or
import
in
this
case
import
group.
A
So
we're
going
to
test
the
group
import
experience
with
end
users,
so
we're
going
to
conduct
user
testing
to
determine,
are
users
able
to
confidently
import
the
gitlab
groups
from
one
instance
to
another
without
having
any
trouble
and,
of
course,
we'll
know
if
we
need
to
do
a
deeper
dive
research
effort.
A
So
we
want
to
introduce
new
navigation
and
test
which
performs
best.
So
you
see
at
the
top.
We
have
our
current
navigation
in
the
plus
icon
to
hover
over
it.
You
get
the
new
tool
tip,
so
I'm
you
know
discoverability
is
a
little
difficult.
So
what
we're
introducing
is
adding
navigation
under
the
groups
and
projects
navigation
item
in
the
top
navigate
top
now
bar-
and
you
know
our
hypothesis
is
that
discoverability
of
the
project
and
group
in
creations
will
improve
so
and
really.
A
This
stems
from
some
users
that
we
tested
the
project
creation
flow
and
when
I
directed
them
to
you,
know
to
import
a
project,
some
of
their
their
initial
thought
was
to
go
up
to
the
project
drop
down
in
the
main
navigation,
and
then
they
realized
that
it
wasn't
once
they
realized
it.
Wasn't
there
that's
when
they
moved
over
to
the
plus
icon.
A
So,
just
to
recap,
where
the
new
functionality
we're
adding
the
ability
to
import
groups
using
a
url
as
well
as,
in
addition
to
the
current
experience
of
exporting
and
importing
a
file,
the
ability
to
cancel
imports
in
progress
and
the
ability
to
view
import
history.
So
those
are
big
ones.
A
We're
also
going
to
do
some
ui
polishes.
So
we've
created
separate
issues
under
the
import,
love,
epic,
and
these
issues
are
intentionally
small
and
are
planned
for
after
the
mbc
is
released
and
feedback
and
validation.