►
From YouTube: Manage::Import UX Office Hours 2021-2-09
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
ux
import
office
hours
and
we
are
gonna,
go
right
through
the
agenda
that
I
have
prepared.
So
first,
I'm
just
gonna
talk
about
the.
A
Let
me
share
my
screen
actually
just
run
through
the
status.
Real,
quick,
so
show
the
most
recent
data
from
the
source
project.
I
have
to
basically
start
from
fresh,
so
I'm
in
the
process
of,
or
will
start
soon,
rather
going
through
this
and
double
checking
that
it's
acting
the
way
it
is
and
that
in
fact
it's
a
bug.
Next
is
the
breadcrumb
link.
A
Am
I
sharing
the
right
screen?
Do
you
guys
see
the
agenda?
Yes,
okay,
okay,
good,
breadcrumb
link,
that's
ready
for
dev
update,
drop
down
component
for
project
and
imports.
What
was
this
is
this?
The
table.
A
Yeah
yeah
and
then
next
is
the
change.
The
ux
after
project
is
deleted.
I
kind
of
wanted
to
talk
through
this
really
quickly
based
off
of
cassio's
response,
and
so
just
in
a
nutshell.
This
is,
after
a
project
is
deleted.
It
you
come
back
to
the
not
project
page,
but
the
project
import
page,
and
you
still
see
oh
wait.
This
is
the
land
on
the
404..
B
Basically,
it's
when
you
delete
the
project
after
import,
it's
still
shown
as
imported
in
the
list
and
when
you
click
to
it,
it
brings
you
the
dead
link.
That's.
A
Right,
yes,
thank
you.
So
what
cassio
is
suggesting
is.
A
Is
perhaps
if
a
project
was
deleted
from
the
source,
it
wouldn't
appear
on
this
page
at
all,.
B
Well,
it
is
well
not
not
exactly
well
written,
but
I
understand
what
cassio
means
I
mean
it
is
not
just
about
disappearing,
it
will
do
exactly
what
you're
requesting
and
it
means
that
the
project
will
act
exactly
as
it
was
never
imported.
So
you
still
have
the
same
ux
as
if
the
project
the
project
was
never
imported.
So
no
change
right
now
you
have
like
a
dead
link,
which
is
definitely
wrong,
and
this
will
just
tune
it
like
okay
yeah.
It
seems
you
are
starting
from
fresh.
B
A
C
So
you
have
a
question:
yes,
we
talked
about
re-import
and
how
that
affects
this
before
we
make
changes.
B
This
does
not
affect
re-import
at
all.
I
believe
because.
Well
I
assume
that
if
I
imported
something
and
deleted
the
result
of
import
reports
exists
as
starting
from
fresh
is
the
correct
behavior,
at
least
from
from
my
point
of
view,
when.
C
So
so
I
know
I'm
I'm
asking
so
I
know
if
I
have
a
full
opinion
yet,
but
I'm
asking
should
it
say
re-import
because
it
was
imported
before
like
this
project
in
github
was
has
been
imported
before
and
if
you
allow
for
re-import,
it
will
have
the
same
effect.
In
the
end
there
will
be
a
green
button.
The
button
will
just
say
re-import
as
opposed
to
import,
but
it
will
give
somebody
a
clue
that
this
has
been
imported
before
the
fact
that
it
got
deleted
or
renamed
or
whatever
else
we
do
to
it.
Notwithstanding.
B
What
sorry,
what
I
could
figure
like,
I
see
no
further
action.
Okay,
let's
assume!
I
see
that
okay,
this
reimport
button,
but
I
have
no
way
to
guess
how
project
was
renamed
where
it
was
moved
and
it
looks
like
a
dead
end
to
me.
So
that
seems
a
bit
confusing.
Okay,.
C
B
Yeah,
I
look
like
I
see.
Okay,
I
see
the
list
of
the
projects
and
one
of
the
projects
says
re-import,
but
it
looks
exactly
the
same
and
like
that's
interesting,
that
means
that
this
project
was
ever
imported
again
and
what
like?
I
have
no
idea
to
figure
out
if
it
was
deleted,
if
it
was
moved
somewhere.
If
something
else
happened
to
each
other.
C
You
don't
have
to
happen
to
it,
but
we
give
you
a
clue
that
something
happened
to
it,
because
if
you
have
a
list
of,
if
you
have
a
list
of
so
once
we
get
to
re-import,
this
will
look
different.
The
go
to
project
link
will
be
reimport
button
for
each
one
of
these,
and
only
the
bottom.
One
right
now
would
say
import.
C
But
let's
say
you
you
come
here
and
everything
is
fresh
and
everything
is
import,
and
now
I
import
one
and
that
changes
to
re-import
I
import
another
one.
That's
successful
that
will
change
to
reimport
right,
that's
how
our
import
will
work
when
we
get
to
then
let's
say
we
import
all
of
them
and
they
all
have
re-import
on
them
or
or
the
other
way
around.
I
like
some
are
important.
Some
are
not
some
say
re-import,
some,
don't.
C
Is
it
more
useful
to
to
give
a
clue
to
the
user
that
this
has
been
imported
before
like?
Is
it?
Would
someone
be
be
hurt
by
it
like
confused
by
it
like?
What's
the
downside
of
giving
it.
B
Well,
I
will
be
confused
if
I
see
free
like
if
I
see
three
different
states
in
the
system.
It
might
from
my
point
of
view,
it
might
probably
confuse
me
even
more.
I
mean
what
we
speak
about.
Three
different
state
of
the
system,
like
first
state
project,
was
never
imported.
In
that
case,
I
will
have
like
exactly
the
ux,
which
is
shown
on
the
bottom
side
like
on
this
one.
Second
state
project
was
imported
but
deleted
somewhere.
B
In
some
way
it
will
be
exactly
as
the
bottom
one
plus
the
button.
The
button
will
say,
re-import
instead
of
import
and
the
third
one
project
was
already
imported
somewhere
and
we
will
somehow
communicate,
I
believe,
the
last
import
target.
Yes,
I
I
assume
that
we
allow
user
to
see
way.
It
was
imported
last
time.
Currently
it
will
be
shown
in
this
ux
on
the.
B
I
believe
amanda
proposed
to
show
it
just
as
a
link
on
the
second
column
to
gitlab,
yes,
and
but
I
don't
know
how
we
will
mix
the
link
on
this
column,
plus
the
drop
down
allowing
you
to
change
the
target
of
import,
which
is
another
point
of
discussion,
but
like
this
is
three
different
states
and
free
is
for
me
a
bit
worse
than
two
okay.
I.
C
I'll
buy
that,
may
I
suggest
that
we
apply
this
issue
to
the
future
state
of
where
we
import
re-import
is
already
happening
so
that
we
can
discuss
that
because
we
wouldn't,
I,
I
think
they
do
touch
each
other
and
you
could
decide
one
way
or
the
other,
and
maybe
we
should
play
this
after
re-import
is
done
so
that
we
have
a
feel
for
what
makes.
B
Well,
from
the
backing
change,
the
backing
change,
which
will
be
required
will
be
required
in
any
way,
and
it's
pretty
minor.
I
mean
that
it
will
not
lose
value
when
the
every
import
will
be
introduced.
B
C
B
Like
it
is,
it
works
a
bit
as
a
way
right
now,
when
I'm
requesting
the
result
of
we
called
it
a
real
time
changes
endpoint,
which
is
which
is
sounds
like
hey.
What
is
the
status
of
the
all?
Import
of
reports
are
currently
in
progress,
but
actually
it
returns
the
status
of
all
imports
ever
done,
and
this
is
what
is
now
the
issue
like
right
now.
It
reports
hey
this
import
is
finish
it
and
that's.
Why
I
draw
ui
for
like
go
to
project
which
is
wrong.
B
What
will
be
done?
It
will
be
just
we
will
simply
filter
on
back
end
their
projects
when
we're
retrieving
these
status.
The
projects
which
are
deleted.
Backend
already
has
this
data,
it's
just
one
filter
query
and
that
simply
will
change
your
ux.
So
I
I
will
simply
do
not
see
this
project
as
ever
imported,
at
least
for
now,
till
reimport
was
introduced.
C
C
Okay
and
then
maybe
when
we
get
to
re-import,
then
we
can
just
you
know
once
everything
is
settled,
we
can
revisit
this
again
and
say:
well,
you
know,
does
it
make
sense
to
give
any
kind
of
a
clue?
Does
the
third
state
make
sense,
or
is
the
third
state
too
much,
but
we
can
decide
that
when
we
have
once
we
have
both
these
issues
implemented.
B
B
Yeah,
I
will
elaborate
on
this
discussion
because,
like
casa
is
a
bit
too
strict
and
about
the
project
will
never
appear
because
from
his
words
it
sounds
like
once
you
delete
it,
you
will
not
be
able
to
reimport
again,
but
I
understand
what
he
understands,
what
he
means
originally.
A
Next
would
be
allow
groups
to
be
migrated
as
new
top
level
groups,
so
we
have
the
mvc
down.
Perhaps
let
me
just
open
the
issue.
C
And
I
have
renamed
this
twice,
but
I
I
just
want
to
like
say
what
this
is
about,
one
more
time,
just
to
make
sure
that
it
everybody's
on
the
same
page
as
far
as
the
title,
because
I'm
trying
to
be
as
unambiguous
as
possible,
but
I
feel
like,
whichever
way,
whichever
way
I
say
it,
it
takes
a
paragraph
to
describe
so
this
is
about
allowing
groups
to
be
migrated
that
will
then
become
a
new
top-level
group,
so
they
will
have
no
parent.
C
Once
the
migration
is
completed,
they
will
become
a
parent
or
a
top
level
group.
Is
that
does
that?
Does
this
title
actually
say
that
to
you?
Are
we
on
the
same
page
there,
because
I'm
not
quite
sure
if,
like
the
way
I
read
it,
does
it
read
it
for
everybody
else?.
A
See
I
would
and
I'll
show
you
area
and
the
designs
I
started,
I
would
say,
promoted,
promote
your
subgroup
to
top
level
group
like
new
top
level
groups.
C
C
And
now,
let's
yeah,
let's
take
a
look
at
that.
C
And
I
I've
asked
amanda
to
separate
the
discussion
of
potential
other
features
that
we
might
find
there,
such
as
creation
and
some
of
the
other
interactions
or
apply
to
all
into
separate
issues,
because
I
know
that
you
wanted
this
in
1390
when
we
planned
this.
C
B
Yes,
I've
already
put
some
weights
there,
but
I
will
check
I
was
finishing
other
stuff.
I
will
today
check
if
this
needs
additional
back-end
job.
In
that
case,
it
will
be
a
small,
quite
small,
like
I
assume,
wait
one
task
for
back-end,
because
from
what
I
saw,
it
should
be
already
supported
on
back-end,
but
I
need
to
obviously
to
double
check.
I've
didn't
touch
it
like
in
a
month
or
so
probably
we
might
broke
something,
but
in
general,
I've
already
put
weight
there
and
yeah.
A
So
yeah,
oh
yes,
okay
and
I
don't
necessarily
have
to
go
into
concepts
for
the
future.
Iteration
I'll,
create
issues
like
harris
said
and
break
it
out
into
various.
A
Various
concepts
and
then
we're
also
going
to
be
user
testing
some
of
this
and
harris.
I
don't
know
if
you
saw
what
I
tagged
you
in
on
slack,
but
there
is
something
that's
like
rapid
user
testing
that
we
just
have
asked
a
few
questions
and
we
get
pretty
feedback
fairly
quickly.
So.
A
A
You
know
three
people
that
are
in
charge
of
migrating
their
entire
organization.
Let's
say
the
first
person,
migrates
600
or
whatever
groups
successfully
the
next
person
that
comes
in
to
migrate,
their
you
know
own
group
of
groups.
They
because
everything
is
ordered
out
alphabetically
when
the
second
person
comes
in
to
migrate
their
groups,
all
of
the
sudden,
their
groups
are
split
into.
You
know
alphabetical
order
with
the
the
user
or
the
first
user
that
came
in
to
migrate
their
group.
A
So
my
suggestion
is
to
create
a
or
add
a
latest
activity
column
and
have
that
be
sortable,
I
would
say
by
default,
that
should
be
the
sort.
But
anyway,
what
are
your
thoughts
on
adding
that?
Or
do
you
think
it's
even
worth
it.
C
So
I
like
the
the
problem,
we're
solving.
We
could
probably
still
validate
it,
but
the
problem
we're
solving,
which
is
help
multiple
people
migrate.
You
know
a
lot
of
projects
each,
so
I
think
we
probably
need
to
think
about
the
solution
and
see
if
there
are
more
targeted
solutions
because
last
updated
like.
C
If
I
change
something
about
the
group,
it
will
also
do
a
last
update,
but
that
will
then
interfere
with
the
fact
that,
like
if
we're
saying
that
the
last
updated
means
that
they
will
be
able
to
tell
which
groups
were
migrated
and
which
groups
were
not,
but
then
some
other
change
can
also
change
the
last
updated
that
will
then
break
their
ability
to
do
this.
C
So
maybe
a
more
targeted
solution
would
be
to
have
a
column
that
says,
migrated
yes
or
no,
or
something
like
that
and
be
able
to
filter
for
that
and
find
that
so
a
more
targeted
solution
to
the
problem
that
that
they're,
having
might
be
something
to
explore.
A
Yeah-
and
I
think
that
having
the
you
know,
the
tabs
that
we
have
been
talking
about
and
introducing
like
that
would
be,
I
think,
extremely
efficient
and
help
solve
like
a
lot
of
these
kind
of
weird
ux
problems
if
we
separate
them
out,
but
you
know,
I
don't
know
where
that
falls
on
the
timeline.
B
I
know
this
is
a
bit
of
topic
of
ux
office
hours,
but
since
harris
mentioned
that
speaking
about
helping
people
to
migrate
like
big
things,
I
would
like
to
share
share
the
very
recent
experience
of
using
group
import.
What
I'm
doing
is
yeah
one.
Second,
I
will
need
to
show
it.
B
B
So
what
we
have
is
a
very,
very
deeply
nested
structure
of
the
group
groups
in
gitlab
use
it
for
our
education,
it's
a
very,
very
deep
nested
thing
and
what
we
are
trying
right
now
utilizing
the
import
feature,
even
without
api
being
available,
is
to
pull
it
to
our
test,
gitlab
local
one,
to
play
something
like
to
mimic
the
group
structure
and
what
we
figured
that
it
was
extremely
confused
and
I've
spent
like
couple
hours
to
debug
it
like
the
import
was
done
not
by
me,
but
by
another
user,
which
made
which
has
not
complete
permissions.
B
I
mean
for
group
active
courses,
he
has
access
to
the
group,
a
group
b,
but
not
to
the
group
c
and
from
his
point
of
view,
the
active
courses
group
was
fully
imported
and
I
originally
assumed
also
this
one
so
like
when
we
have
a
deeply
nested
structure,
the
groups
and
the
person
has
zero
permissions
to
some
of
them.
This
might
be
a
tricky
one
like
from
point
of
view
of
one
person.
B
The
group
here
are,
he
is
fully
imported
but
from
other
point
of
view
we
do
not
imported
entire
group
here
or
here
for
one
top
level
group.
So
the
problem
is
that
if
we
have
somewhere
missing
permission
on
some
group
deep
in
the
tree,
it
could
be
very
confusing
and
hard
to
track
what
we
are
really
missing.
C
So
I
have
created
an
issue:
that's
called
a
pre-import
check
report
of
some
sorts,
so
this
may
be
something
to
add
there
and
also
in
the
post
import
report,
which
is
where
we
summarize
and
tell
you
hey.
We
have
imported
this
many
groups,
this
many
epics,
also
errors
like
things
that
didn't
import
partially
import
like
this
got
partially
imported.
This
data
was
missing.
This
broke
this
timed
out,
like
you
know,
a
report
of
what
happened,
but
also
a
report
of
what
will
happen
in
there.
We
can
include
fact
that
there
may
be.
B
We
can't
no,
we
can't,
because
we
are
communicating
to
remote
git
lab
via
api
and
via
api.
We
can't
verify
if
there
is
a
group
there,
we
do
not
have
access
or
there
is
simply
no
group
there.
This
intentional
security
feature,
so
you
can't
differentiate-
and
you
can't
reveal
this
even
on
local
gitlab.
B
C
Yeah
but
even
pre
like,
if
you
have
ability
to
to
show
this
to
someone
and
say,
hey,
I'm
gonna
import
and
it
looks
like
I'm
going
to
import.
You
know
20
groups
and
he's
like
what
do
you
mean
20
groups,
there's
100
groups
there
yeah,
oh,
I
think
either
report
will
have
a
positive
will
have
a
positive
message
in
there,
which
is.
These
are
the
things
that
will
import
and
then
afterwards
these
are
things
that
have
imported
and
then
you
will
have
to
like
deduce
from
there.
C
If
there
is
a
something
missing
like
we
can't
tell
you
if
there's
something
missing
but
we'll
tell
you
what
is
there
and
then
you
can
figure
out
if
something
is
missing,
so
I
think
both
of
those
would
help
catch
that,
but
there's
not
much.
We
can
do.
Apparently,
if
we
can't
tell
anyone
there's
something
there.
I.
A
C
B
Yeah,
I'm
actually
making
a
note
to
backhand,
I'm
just
not
sure
where
to
put
it
so
it
will
not
be
lost.
At
least
it
is
in
in
my
to-do
list
that
we
could
not
in
the
future.
When
we
allow
importing
re-importing
groups
or
importing
non-top-level
groups,
we
can't
trust
the
import
status
if
it
was
done
by
other
users.
I
mean
if
something
reports
like
hey
this
top
level
group
was
completely
imported.
It
does
not
mean
that
we
automatically
should
play
put
like
okay.
This
was
important
sign
on
any
bottom
level
groups
under
this
one.
B
C
B
Well-
and
I
will
believe
we
will
have
this
issue
on
all
levels-
I
mean,
I
don't
remember
if
we
have
private
epics,
but
for
example,
this
will
be
the
same
if
you
do
not
have
access
to
the
epic
and
you
will
already
miss
it
from
the
import,
I'm
not
need
to
check
if
I'm
not
sure
if
you
have
a
private
epics.
C
You
know
there
may
be
objects
on
the
other
instance
that
you
don't
have
access
that
just
will
not
be
imported,
so
you
know
some
some
message
to
the
effect
of
hey.
There
could
be
things
out
there.
You
should
probably
check
if
this
is
all.
C
Yeah,
it's
good
it's
good
catch
because
I
think
we
actually
did
discuss
like
I
in
some
way.
One
of
the
issues
I
did
write,
something
like
I'm
actually,
okay
with
people
seeing
you
know
someone
seeing
that
somebody
else
has
imports
like
the
fact
that
someone
has
imported
it.
C
Even
if
you
don't
know
if
you
don't
have
access
to
the
project
that
get
imported
to
so
yeah,
so
that's
the
other
way
around
like
if
on
the
destination,
you
wouldn't
have
access
to
it,
and
you
also
can't
even
know
who
the
person
is,
but
you
have
access
on
the
source.
We
can
tell
you
this
was
imported.
We
just
can't
tell
you
where
or
when,
or
you
know
like
any
data,
but
we
can
tell
you
that
this
was
imported,
so
that
is,
I
think,
important
for
a
github
importer
as
well.
C
I
think
that's
where
we
had
the
discussion
in
one
of
the
issues,
because
the
github
permissions
may
be
different
from
your
gitlab
permissions,
so
you
can
see
something
on
github
and
we
should
be
able
to
tell
you
that
yep
someone
somewhere
imported
this.
We
just
can't
tell
you
anything
about
the
gitlab
side
of
things,
but
we
can
tell
you
that
you
know
this
github
thing
got
imported
into
the
instance
and.
C
That,
like
I,
was
okay
with
that
security.
You
know
it's
not
a
whole
but
just
kind
of
a
security
question.
C
I
don't
think
there's
a
legitimate-
or
I
haven't
heard
of
legitimate
reason
to
like
hide
the
fact
that
something
you
have
access
to
was
they
appointed
by
someone?
You
just
don't
know
where
or
how.