►
From YouTube: Manage::Import UX Office Hours 2021-03-23
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
All
right
so
welcome
to
the
weekly
import
office
hours
meeting.
I
have
created
agenda
that
we
can
go
ahead
and
and
go
through.
I
just
would
like
to
have
y'all's
input
on
how
to
prioritize
the
ux
issues.
So
I
know
like
what's
most
important
like
some
of
these
are
have
been
started
as
in
issues
created
and
like
concepts
have
been
thrown
out
there,
but
it'll
help
me
prioritize
like
okay.
What
do
I
need
to
focus
on?
What
do
I
need
to
make
sure?
A
I
have
prioritize
user
testing
too,
because
there's
a
lot
of
stuff
that
needs
to
be
put
through
solution,
validation,
so
it'll
just
help
me
with
planning
and
perhaps
it'll
help
you
all.
So
these
are
just
a
handful
of
issues.
I
know
there's
more
and
I'll,
probably
look
at
the
kanban
board
to
see
what
else
I
can
add,
but
just
to
start
off,
I
know
a
big
one
is
the
able
multi-select
behavior.
A
A
So
that's
a
major
thing
on
my
to-do
list
that
I
actually
want
to
get
done
this
week,
and
maybe
I
don't
know
if
it,
if
not
having
harris
here
well,
we
can
see
where
we
go
with
this,
but
so
I
just
I
created
these
columns
and
we
can
totally
change
them
if
something
else
makes
better
sense,
but,
like
I
have
who
is
involved
they're
just
including
a
column
there,
what
is
still
needed,
for
instance,
I
put
for
the
table
select
on
the
multi-select
behavior
in
the
sticky
table
header,
which
I
understand
are
two
separate
issues.
A
So
maybe
I
should
break
those
out,
but
we
definitely
need
feedback
from
the
ux
team
with
the
potential
of
actually
asking
you
know
additional
gitlab
users
so
and
then
I
have
a
column
specific
to
you
know:
solution
validation
needed
I'm
assuming
most
every
column.
I'm
sorry
every
row
is
going
to
have
a
yes
there,
but
who
knows
so-
and
I
was
thinking
level
of
complexity
like
instead
of
like
assigning
a
number.
Perhaps
we
can.
A
I
don't
know
if
this
is
a
way
to
make
it
even
more
loose
but
like
for
ux,
I
put
high
to
medium
complexity,
just
because
I
you
know
there
could
be
high
to
medium.
I
mean
I
think
I
got
a
large
chunk
of
the
work
done,
but
again
until
I
start
socializing,
who
knows
how
many
holes
people
will
find
in
the
design?
So
that's
what
I
was
thinking
that
we
could
use
this
time
to
discuss.
B
A
D
Well,
I
still
looking
for
like
about
multi-select
behavior.
It
seems
well
pretty
seen
from
front-end
perspective.
Unfortunately,
we
will
need
to
either
create
or
that
from
scratch,
or
I
will
take
a
look
if
someone
else
in
gitlab
implemented
it,
because
I
don't
want
to
create
more
solutions
to
the
same
problems.
Currently,
I'm
not
aware
of
that
at
least
if
we
could
reuse
it
and
for
the
rest,
it
feels
okay
for
me,
I'm
right
now
working
on
other
stuff.
D
So
I
don't
to
too
deep
to
get
this
concrete
issues,
the
only
one
I
would
like
to
to
mention
that
for
cancel
group
migrations,
this
will
definitely
involve
back-end
work
because
we
currently
have
no
api
endpoint
to
cancel
that
once
okay,
so
yeah.
What
I'm
currently
working
on
is
a
new
group
creation,
ui
unified
with
project
ui
we've
created
long
long
ago,
and
I'm
just
doing
that
in
the
right
way:
cleaning,
the
experiment
and
so
on,
and
so
on.
A
Okay,
let's
see,
I
think
that
the
table
multi-select
behavior
will,
I
think,
we're
going
to
be
kind
of
pilot
for
this
interaction.
So
I
I'm
you
know
I
don't
wanna.
You
speak
on
behalf
of
yourself,
but
this
in
my
mind
this
could
be
a
potentially
huge
undertaking,
but
obviously
you
can
comment
on
on
that,
but
only
because
I
don't
know
oops,
I
have
found
other.
Let
me
see
like
let's
go
to
when
you
edit
issues,
what
I'm
let.
A
So
you
can
edit
issues
and
there
they
do
have
the
multi-select
functionality,
but
it's
a
different
direction.
We're
wanting
to
head
the
work
within
this
issue
specific
to
import
kind
of
stems
from
what
andy's
already
working
or
has
worked
on
in
regards
to
kind
of
the
enterprise
table
functionality.
A
So
he
has
started
designs
for
for
multi-select,
but
to
my
knowledge
they
haven't
been
implemented
anywhere.
Andy
did
say
that
he
began
for
security.
He
began
working
on
multi-select,
but
I
think
he's
going
to
defer
to
whatever
we
plan
on
implementing.
So
that's
as
much
backstory
to
that.
As
I
have.
D
Let's
see,
let's
see
how
it
goes,
but
in
general
this
is
not
like
the
task
of
extreme
complexities,
like
I
said
pretty
sane,
so
I
do
not
foresee
any
big
problems
there
in
terms
of
implementation.
A
Okay,
what
level
of
complexity
then,
would
you
rate
that,
from
high
to
low.
D
A
A
So
I
just
created
this
table
and
basically
threw
in
some
different
and
upcoming
issues.
Well,
these
are
all
fairly
current,
but
us
issues
and
I
just
kind
of
want
to
rank
them
in
order
of
priority
to
help
me
focus
on
okay.
What
do
we
need
to
user
test
first,
and
what
do
I
need
to
focus
on
so
from
you
know
I
have
who
is
involved
and
from
a
table
multi-select
behavior.
Is
it
just
ux
in
front
end?
Will
there
be
any
need
for
back
end?
You
think.
B
Sorry
sorry,
I
missed
that.
B
A
B
D
I
believe
we
will
not
need
to
back
in
here,
because
it's
basically
depending
on
on
what
elements
we
invoke
important
beckett,
have
full
support
of
involving
import
for
multiple
entities.
So
it's
I
didn't,
expect
any
back-end
involvement
here.
C
Even
if
we
do
do
require
that
we
remember
the
selections
across
pages
right,
because
I
think
that's
the
complexity
that
we're
looking
to
introduce.
That
may
not
be
on
the
page
that
we
just
saw
where
you
do.
The
issue
tag
thing.
A
Cool
all
right
and
we
can
figure
out-
you
know
the
rank
of
these
after
we
go
through
all
of
them
and
I'm
missing
some.
I'm
sure
from
this
so
feel
free
to
add
to
this.
If
you,
if
you
know
of
any
ux
issues
so
organize
the
data
within
tabs,
that
is.
A
This
concept,
so
I
know
we're
going
to
need
user
solution,
validation
for
this
particular
issue,
so
I
know
uxes
and
will
be
involved
in
all
of
these.
But
from
my
understanding
this
will
be
a
front
end.
D
Yeah
and
also
back-end,
I
believe,
because
we
do
not
have
an
ability
to
filter
by
specific
status
of
the
import,
so
the
back-end
also
will
be
there.
A
Okay,
all
right,
so,
let's
see.
A
So
I
said
suppose
ux
what
is
still
needed.
I
think
solution,
validation
and
then,
depending
on,
where
we're
at
that,
where
we
land
there,
I
think
we'll
have
a
better
understanding
of
what
is
still
needed
from
a
front-end
backup
and
back
in
perspective.
Would
you
all
agree.
D
Yeah,
probably,
I
think,
because
I
did
not
pay
too
much
attention
to
this
issue
yet
so
yeah,
but
in
general
it
feels
like
the
tabs
on
the
other
importer,
so
it
should
be
doable.
B
Okay,
yeah
yeah,
as
far
as
I
lift
it
as
well.
It's
basically
filtering
by
starters,
they're,
currently
what
we
already
have
where
they
can
so
shouldn't
be
too
complex
in
there.
A
Okay
and
then
level
of
complexity,
do
you
want
to
speak
on
that.
A
All
right
next,
I'm
not
sure
if
you
all
are
familiar
with
this,
but
it's
fairly
new.
But
what
we
want
to
test
is
whether
or
not
these
the
external
link
icons
can
be
removed,
if
possible,
to
reduce
the
clutter
to
be
replaced
with
a
modal.
A
Okay,
there
we
go
so
essentially
I
can't.
Oh
there
we
go
a
user
clicks
on
a
source
group
link
and
then
they
have
a
modal
saying.
This
link
will
open
in
a
new
tab.
I
don't
have
a
credit
wording,
but
don't
share
this
message
again,
so
I
think
we
need
to.
A
You
know
do
solution,
validation
on
this
issue,
so
that's
kind
of
what
we're
trying
to
do
with
the
external
link
versus
modal.
So
you
know
ux
and
front
end
are
involved.
I
wouldn't
assume
back
end
would
be
involved,
but
let
me
know.
A
And
then,
from
a
ux
perspective,
this
will
be
low
helio
from
a
front-end
perspective.
Would
that
just
be
loved?
Well.
D
D
I
will
probably
mention
that
in
the
tissue
that,
for
example,
such
pop-ups
are
usually
very
confusing
when
mix
it
with
a
normal
browser
behavior
like
opening
the
links
in
youtube
by
clicking
with
your
mouse
wheel
or
whatever
the
way
you
have
to
open
the
link
already
in
new
youtube
and
interaction
of
such
pop-ups
with
such
links
sometimes
is
extremely
confusing.
A
Fair
enough
that
makes
sense,
would
you
mind
adding
that
brilliant
comment
to
the
issue
there.
C
I
I
do
agree
there.
Yes,
I
would
like
to
see
if
there's
a
way
to
maybe
avoid
the
pop-up
like
if
we
can
clean
up
the
the
table,
but
not
introduce
a
pop-up,
because
models
are
just
in
my
mind,
they're
crutches
and
also
should
be
used.
Only
when,
like
it's
critical
and
there's
no
other
way
of
doing
things
and
things
are
critical.
D
A
Yeah
all
right,
this
is
good
zoom
out
again.
D
I
will
add
a
comment,
as
you
asked
yeah.
A
Yeah,
so
anything
else,
if
not
I'll
move
on
to
last
one,
which
is
cancel
group
migrations,
which
is
a
pretty
big
one.
Oh
you
know
what
else
is
in
here.
Re-Import
group
is
another
big
one.
Let
me
just
add
that,
so
I
don't
forget.
A
A
A
B
B
A
The
thing
with
cancel
migrations,
as
well
as
re-import
and
perhaps
other
functionality
all
to
me,
stems
with
wrapping
up
the
organized
states
of
the
group
migration
in
different
tabs,
just
because
I
think
the
ux
would
completely
change
if
we
have
the
table
with
and
without
tabs.
So
speaking
kind
of
around
priority,
I
to
me
this
seems
pretty
high,
at
least
from
a
ux
perspective.
A
A
Because
those
are
top
priority,
what
do
you
all
think
like
how?
Where
does
this
fall?
I'm
sorry,
I
don't
have
a
combined
board
open,
but
where
does
this
fall
within
kind
of
the
future
priorities
in
relation
to
you
know
the
ux
priority.
B
A
A
Okay,
then
external
link
versus
modal.
I
just
put
that
as
low.
That's,
like
the
last
low
priority,
cancel
group
migrations.
A
B
D
No,
we
do
not
have
reimport
now,
since
we
are
now
persisting
state
of
the
import,
so
in
ux
right
now
you
will
not
have
ability
to
import
again.
C
So
we
broke
re-import
right
like
we
had
re-import,
because
we
were
very
naive
in
the
beginning.
Right,
yes,
and
then
we
removed
it,
but
so
I
feel
like
adding
background.
Import
is
really
important.
People
are
going
to
ask
for
that
that
that
needs
to
be
the
top
priority
functionality,
wise
and
value-wise.
So
for
talking
about
people
about
user
value
and
about
what
the
users
are
going
to
scream
at
us
about.
D
Yeah-
and
this
is
basically
like
ux
side,
because
obviously
functionality
for
e
here
and
the
logic
confronted
is
also
already
here
so
like.
I
need
to
write
a
few
more
lines
of
code
and
a
couple
tests
and
that's
it
so
it's
more
like
ux
focus
at
how
we
want
to
communicate
the
ring
portability
to
end
user.
A
D
Well,
and
also,
I
would
prefer
to
have
like
a
clean
setup
of
functionality
before
ux
to
before
front
end.
Rework
so
I'm
okay
to
like,
like
I
would
like
to
make
this
tab
switch
as
late
as
possible
when
we
have
master
functionality
here.
So
if
you
have
ability
to
do
like
a
multi-select
before
that,
I
will
be
happier.
A
C
B
A
So
again,
we're
keeping
table
at
priority
one
and
then
for
re-import.
Where
does
that
change
rankings.
C
I
would
say:
re-import
needs
to
be
the
first
thing
we
think
through
because
we
broke
it
recently,
so
reimport
used
to
work,
and
now
it
doesn't
so
that's
why,
in
my
mind,
that
becomes
a
really
important
thing.
It
is
a
high
value
to
the
user
and
it
will
cause
support
calls
if
user
can't
execute
it
all.
The
other
things
will
not
like
all
the
other.
Things
are
add-on
features
that
are
really
nice,
but
this
one
has
really
a
potential
to
be
a
problem
for
us.
B
B
A
All
right
sweet
well.
This
helps
me
to
prioritize
what
to
be
working
on
and
because
I
will
be
setting
up
user
testing
this
week.
A
So
this
helps
quite
a
bit
so
we're
two
minutes
over
anything
else.
Anyone
wants
to
say.