►
From YouTube: Manage::Import UX Office Hours 2021-01-27
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,
we
are
starting
our
weekly
ux
office
hours
for
import,
and
I
have
an
agenda
to
go
off
of
so.
The
first
section
is:
let
me
share
my
screen.
A
Okay,
it's
not
highlighted
for
some
reason,
so
the
first
is
just
like
a
read-only
section:
yoyo
like
take
it
or
leave
it
just
reminding
you
or
you
know
just
for
reference.
I
guess
so.
What
I
want
to
chat
about
is,
let's
see,
creating
okay,
we're
gonna
skip
number
one
because
I
just
spoke
with
harris
and
it's
a
really
simple
change
but
in
my
mind
it
was
mega
complicated.
A
C
A
C
Believe
we
have
two
issues
which
looks
pretty
similar,
but
I
believe
we
are
addressing
a
bit
different
things
here.
Let
me
just
check
one
second.
B
Maybe
speak
to
the
two
approaches
approach
for
each
so.
C
B
C
C
New
group
and
it
will
serve
as
a
route,
so,
for
example,
when
we
are
doing
migration,
everything
will
be
added
under
that
group.
Well,
for
where
you
selected
that,
but
the
previous
issue
is
about
ability
to
use
root
as
a
root
instance,
sorry
for
duplicating
naming.
So,
for
example,
if
I
have
the
group
gitlab
org
on
one
instance,
I
should
be
able
to
import
it
as
slash
gitlab
or
under
another
instance
right
now.
This
is
impossible.
B
It
is
to
be
able
to
just
migrate
the
group
to
I'll
just
hang
off
a
route
to
to
not
have
a
parent
to
be
a
top
level
group.
The
difference
between
these
two
we
arrived
at
these
two
from
two
different
directions.
B
One
was
sort
of
we
wanted
to
be
able
to
do
this,
regardless
of
whether
there's
other
choices
or
not.
So
if
I
have
groups
to
select
from
there
is
a
there's
ability
for
me
to
say
no,
I
don't
want
any
of
these
to
be
parents.
I
want
the
one
I'm
migrating
to
become
a
top-level
group,
and
then
I
think
when
we
talked
you
said,
oh,
but
the
the
the
the
ui
is
even
broken
even
more
than
that.
B
So
then
I
thought
well,
let's
just
have
an
issue
to
just
play
that
and
just
fix
that
in
a
way,
because
that
is
more
critical
so
that
if
there
is
no
groups
whatsoever,
I
can
just
you
know.
I
somehow
can
move
this
group
from
one
place
to
another
and
it
just
becomes
a
group,
a
root
group.
It
becomes
a
top-level
group
and
I
feel
like
the
solution
to
both
of
those
issues
is
the
same,
which
is
adding
that
additional
choice
and
drop
down
that
says
you
know
this
will
be
a
root
like
I
am.
B
I
have
no
parent
in
the
drop
down,
so
the
solution
to
both
of
those
problems
will
be
the
same.
Whether
there
are
other
issues
to
pick
from,
and
this
is
just
an
inability
to
make
it
a
route
or
whether
there's
no
issues
to
to
pick
from
and
now
it's
a
bug,
because
we
just
can't
move
forward.
B
If
there's
no
other
groups
to
choose
from
and
there's
no
ability
to
pick
roots
and
now
it's
a
bomb,
so
one
was
being
treated
as
a
bug
that
needed
to
be
turned
on
very
quickly
and
the
other
one
could
have
waited.
But
in
the
end,
when
we
discussed
the
solution,
I
feel
like
we
arrived
at
the
same
solution
that
solves
both,
which
is
just
adding
that
one
choice:
that's
always
there
and
whether
there's
other
groups
underneath
that
or
not
it
really
doesn't
matter
anymore.
C
Yeah,
so,
regarding
this
one,
I
just
need
to
check.
C
C
I
as
usual,
our
our
security
model
is
a
bit
complex
and
I
can't
say,
with
100
sure
opportunity
when
this
happens,
but
this
actually
makes
a
perfect
sense
to
me.
Otherwise
I
mean
if
we
are
allowed
to
create
top
level
group.
Just
add
this
one,
but
I'm
still
not
sure
what
we
should
write
in
the
drop
down,
because
if
I
see
it
slash
a
new
top
level
group
slash
team
activity,
it
still
feels
a
bit
confusing
for
me
like
a
bit
unclear
what
will
happen?
C
B
Okay,
so
in
your
case
the
route
would
make
sense,
because
then
it
is
the
parent
and
it's
just
a
special
case.
We
could
put
it
in
like
less
than
greater
than
parentheses
and
just
says
root,
so
it
looks
like
a
special
case.
It's
always
at
the
top,
or
always
at
the
bottom
and
and
okay.
I
see
I
see
what
you
mean
like.
If
it
just
says
new
top
level
group,
then
it
kind
of
breaks.
B
The
pattern
of
everything
else
is
the
name
of
the
parent,
and
this
is
an
action
we
can
discuss
that
in
the
issue.
But
so
here's
my
question:
don't
you
always
have
the
ability
to
create
a
group
under
your
own
namespace,
like?
Isn't
your
namespace
always
able
to
create
you
for
no.
C
B
C
B
Okay,
so
that
that
would
mean,
then
that
we
do
have
a
possible
scenario
where
there
isn't
even
ability
to
do
a
route,
and
you
have
no
groups.
You
belong
to.
Therefore
we
should
have
a
special
handling
case.
So
maybe
the
first
issue
could
be
the
handling
of
the
special
case
where
there
is
no
route
available
and
the
second
issue
could
be
if
the
route
is
available
show
root.
C
Yeah
this
is
this
makes
sense,
and
actually
this
might
be
a
good
opportunity
it
might.
It
might
be
probably
a
good
opportunity
to
revisit
all
possible
empty
state
scenarios,
because
we
already
have
two
more
which
are
already
implemented,
and
probably
we
would
like
to
check
proper
wording
on
that.
C
This
is
when
there
are
no
groups
available
for
import
on
the
remote
side
and
also
when
you
do
filtering,
and
there
are
no
groups
on
remote
side
as
a
result
of
filter.
C
So
for
this
last
one
I've
just
copied
the
message.
Sorry,
your
filter
wait.
B
C
Not
filtering
on
the
page
yeah,
no,
no,
when,
when
you're
filtering
on
the
page,
one
second
just
doesn't.
B
B
Okay,
so
what
were
you
saying
then,
prior
to
this,
you
said
that
potentially
filtering
can
impact.
C
Yeah,
it's
it.
It
could
lead
to
the
result
when
your
filter
simply
doesn't
match
any
groups
on
the
source
side,
and
you
just.
We
just
need
a
proper
message.
There.
B
C
Yeah-
and
it
is
also
a
question-
should
we
communicate
them
differently
like
that,
as
the
first
minimal
iteration,
it
could
probably
make
sense
just
to
keep
them
all
the
same,
like
do
not
displaying
the
ux
and
just
saying,
oh
sorry,
it's
just
like
a
whole
screen
message
like
sorry,
you
can't
import
this
one
until
you
have
top
level
group
available
for
you.
C
Yeah,
okay,
so
one
second,
let
me
just
share
my
screen
for
this
moment.
Yes,
I
can
stop
your
screen
share.
So
oh
yeah
go
ahead.
C
One
second,
it's
och!
Sorry,
you.
A
A
C
Show
you
yeah,
I
have
ultra
white
screen,
sorry
for
that,
okay,
so,
for
example,
right
now
how
it
works.
I
just
started
the
local
instance
because
it's
currently
under
review,
so
it's
not
available
on
other,
so
instance.
So
when
you
do
a
filtering,
this
is
slow
here.
Sorry,
your
filter
produced
no
results,
and
probably
we
could,
as
a
very
first
start
just
add
another
message
like
sorry.
You
need
to
have
at
least
one
top
level
group
available
for
you
to
proceed.
C
Yeah
for
sure
we
have
like
just
I
mean
that
keeping
the
same
uax
not
displaying
available
source
groups,
so
yeah.
B
Let's
just
go
with
a
sentence
in
the
middle
and
then
we'll
you
know
maybe
amanda
can,
when
you
get
to
demand
that
when
you
have
time
to
maybe
produce
a
better
empty
yeah
empty
screen.
I
know
we
have.
C
Yeah
because
it's
you
are
pretty
correct
and
it
feels
a
bit
confusing,
because
this
is
acquired
two
different
empty
states.
One
because,
like
one
side
of
the
connection
and
one
because
of
another
side
of
connection-
and
we
could
might
want
to
communicate
that.
B
And
is
there
decide
which
one
is
top?
We
just
need
to
decide
which
one
to
express
this
like.
If
both
are
true,
I
I
would
believe
that
inability
to
create
group
takes
precedence,
so
you
should
like
it
doesn't
really
matter.
You
shouldn't
be
filtering
for
things.
B
A
Just
for
planning
for
the
future
we're
going
to
have
to
look
at
this
from
a
bulk
import
state.
So
we
can't
expect
the
user
to
go
down
each
row
and
make
changes.
So
how
soon
will
we
start
introducing
kind
of
the.
B
From
my
perspective,
I
feel,
like
that's
gonna,
be
a
milestone
at
least
or
two
yeah.
We
have.
We
have
lined
up
other
things
ahead.
B
C
Yeah,
I'm
working
on
that
just
starting
to
want
to
quickly
check
the
board.
What
do
we
have
on
on
my
table
for
before
that?
I
believe
the
import,
statuses,
update
and.
C
So
let
me
I'm
checking
just
the
board,
so
we
have
like
migration
list.
A
simple
pagination
done.
Filter
capacity,
I'm
done
I
mean
under
review-
shows
the
total
number
done.
A
thousand
showing
import
status,
which
is
will
make
this
milestone,
be,
and
I'm
just
checking
next
stop.
What
do
we
have.
A
A
C
C
C
Busy
one
yeah
yeah
makes
sense,
so
we
could
expect
this
next
milestone
and
to
in
any
case,
if
well,
no
matter
what.
B
I
think
I
would
like
to
prioritize
the
solution,
just
the
adding
to
the
drop
down,
if
possible,
higher
than
some
of
the
other
things
that
are
in
the
list,
because
that
is
all
this
is
almost
a
bug
like
you
get
yourself
in
a
state
that
you
can't
get
out
of.
C
B
B
Okay,
so
we'll
have
I'll
repurpose
the
two
issues.
I
will
clarify
that
in
the
description
one
will
be
about
just
adding
the
ability
to
have
roots
there
and
the
other
one
will
be.
C
And
one
another
one
we
could
probably
just
keep
for
now.
It
was
like
about
a
proper
pop-up
for
creating
new
top
level
group
and
so
on.
It
was
about
pop-up,
and
probably
we
decided
like
hey,
let's
just
go
with
just
adding
the
root
instance
to
drop
down.
Oh.
B
I
think
the
other
one
was,
if
you
don't
have
the
ability
to
create
root,
then
like
an
empty
state.
C
B
Okay,
so
I'll
reshuffle
the
issues
after
this
to
sort
of
line
them
up
and
I'll
ping,
even
them
and
I'll
put
them
in
the
right
spot
in
on
the
kanban
board,
so
that
they're
in
order
to
make.
B
Have
another
issue
to
make
prettier
empty
states.
B
I'm
sure
there's
some
kind
of
like
a
disconnected
cable
or
some
some
illustration.
We
have
elsewhere
in
empty
states
and
we
just.
C
A
So
let
me
share
my
screen.
I
know
we
have
two
minutes
left,
but
I
just
want
to
talk
through
a
couple
things.
A
Let's
see,
okay,
here
we
go
so
I
just
found
some
ui
like
bugs
for
lack
of
a
better
term,
but
what
I
can
do
with
those
is
just
create
an
issue
with
everything
I
don't
know.
Do
you
want
me
to
create
separate
issues
for
what
I
find
or
to
start
off
with?
Should
I
create
one
and
then
we
can
break
those
off.
B
C
C
C
A
Yeah
so
those
are
missing
and
then
I
just
randomly
found
this.
So
this
is
a
dummy
account,
obviously,
and
not
that
anyone
will
have
this
many
subgroups.
A
Or
they
might
but
like
something
funky
goes
on
here,
so
it'd
be
cool
if
we
could
put
figure
out
how
many
characters
fit
and
then
put
in
a
ellipse.
A
So
those
are
some
examples
that
we
can
do
and
I
think
that
we
can
reduce.
C
Yeah
well
so
probably
we,
let's
start
with
creating
one
issue,
describing
all
problems
you
would
like
to
address
and
we
can,
as
usual
slice
an
issue
each
an
issue
one
by
one,
to
like
target
separate
parts.
If
we
would
like,
I
would
like,
or
you
would
like
to
address
it
separately
for
any.
A
C
Yeah
because,
for
example,
the
resizing
drop
down.
This
is
like
the
issue
which
affects,
for
example,
the
project
importers
as
well.
So
it's
a
bit
wider
than
you
think
and
we
are
having
exactly
the
same
issue
and
it's
actually
like
not
feels
more
like
a
bug
but
still
closely
tied
to
your
ex,
and
we
still
will
need
to
think
how
we
will
handle
that.
Because
for.
C
A
So,
okay,
that's
cool
I'll!
Do
that
I'll,
create
an
issue
with
everything
in
it
table
sorting,
let's
hold
off
until
next
week,
because
I
don't
think,
that's
you
know
high
up
on
the
list
and
then
allow
users
to
reimport.
Let
me
mock
something
up
for
that,
at
least
so
we
can
talk
about
it,
but
I
think
we've
gotten
through
everything
in
my
agenda
for
the
agenda
rather
any
final
words.
A
Yeah,
all
the
time,
all
right,
you
have
a
good
night
ilya
and
then
harris
I'll
talk
to
you
after
this.
If
you
just
want
to
quickly
slap
me,
your
meeting
all
right,
y'all
I'll
see
you
later.