►
From YouTube: Manage::Import UX Office Hours 2021-02-16
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
another
edition
of
manage
import
office
hours
and
we
are
going
to
go
through
the
agenda
for
today's
meeting.
I
can
share
my
screen
here.
It's
really
quick
or
maybe
not
really
quick,
but
fair
screen
all
right.
So
a
lot
to
talk
about.
A
A
You
know
the
new
layout,
the
ability
to
see
group
metadata
so
and
the
other
flow
I
have
going
is,
if
a
you
know,
the
empty
state,
essentially
so,
and
then
I'll
do
for
cancel,
of
course,
and
what
I've
started
to
write
out
is
a
list
of
kind
of
every
flow
that
we
should
document.
Some
of
these
obviously
can
be
confined
into
one
flow,
but
I
just
want
to
make
sure
I
capture
everything.
B
Let
me
just
see
through
the
list
a
little
bit
and
see.
B
A
B
Creating
a
top
level
group
this
is,
I
feel
like
that,
may
be
describing
a
creation.
I
would
just
you
know
migrating
top
level
group
or
something
like
that.
Yeah
migrating
group
that
becomes
a
top
level,
so
really
talk.
We're
talking
talking
about
top
level
groups
on
a
destination
in
destination
instance,
so
migrating
the
top
level
group-
and
I
know
what
I
mean-
we
know
what
it
is,
but
yeah
yeah,
because
I
we
should
not
be
just
creating
any
kind
of
blank
group
as
part
of
migration.
B
The
only
groups
that
get
created
are
the
ones
that
are
migrated
because
in
users
mind
I'm
just
moving
my
group
from
here
to
here.
B
So
when
talking
about,
like
you
know
from
user
perspective,
I
would
say
that
you
know
we're
not
creating
groups.
We
are
just
moving
your
groups
from
one
instance
to
another.
B
A
I
meant
promoting
and
the
fact
that
when
you
move
a
subgroup
to
a
top
level.
B
B
B
A
Did
you
see
my
wireframe
that
I
did
showing
exactly
what
you
just
explained.
A
B
A
Yeah
yeah
and
then
we
can
point
out.
The
inconsistencies,
which
is
another
point
on
my
list-
is
a
map
out
current
mvc
project
versus
group,
migration
and
document,
which
I
have
already
started.
A
I'll
link
that
too
a
scorecard.
A
B
A
B
We
have
to
find
some
single
actions
and
then
promote
them
to
bulk
actions
right.
That's
the
only
single
action
that
I
think
is
you
know
could
be
made
bulk.
A
Yeah
and
what
I
have
here,
which
is
an
agenda,
my
agenda
item,
the
idea
of
selecting
either
by
picking
per
row
or
select
all
and
then
have
a
drop
down
which
you
can.
A
I
don't
know
what
that
what
that
is
necessarily
but-
and
we
of
course
could
get
rid
of
this,
especially
for
the
time
being.
B
So
yeah
different
era
states.
A
B
B
B
So
around
the
bulk
action-
and
I
don't
know
if
this
is
something
that
needs
a
figma
flow
or
not-
is
really
a
decision
around
well.
What
is
the
default
parent
that
we
should
pick
like?
I
don't
know
that
that
I'm
happy
with
whatever
random
thing
we
have
right
now,
I
feel
like
we
should
maybe
ask
our
users
about
it
and
ask
what
is
the
what
should
be
the
default
parent
group
that
we
select
for
all?
B
So
when
you
come
fresh
to
the
screen,
you
know
the
there's
gonna
be
some
parent
group
selected
for
all
of
them
and
I
wonder
like
what
is
the
right
thing
for
different
users,
maybe
different
thing
for
us
to
have
there
and
I
think
that
sort
of
plays
into
the
apply
the
change
to
all,
because
am
I
am
I
saying
that
this
is
really
my
new
default
like?
Should
this
be
just
like
next
time
I
come.
Should
this
be
it
so?
B
Is
it
apply
change
to
all
right
now
or
is
it
make
default
in
a
way,
or
maybe
both
of
those
options
right
yeah,
and
I
really
don't
know
that
we
have
a
great.
So
I
think
exploring
that
would
be
really
good
to
understand
what
should
be
picked
as
a
default,
and
should
the
users
be
able
to
change
that
and
make
something
else
a
default,
and
then,
in
context
of
that
also
apply
that
change
to
all
the
selected.
A
A
So
here
that's
selected
and
if
you
check
out.
A
So
they
have
a
lazy
load
and
what
happens
when
you
see.
B
B
A
B
B
As
to
where
it
draws
the
line
like
how
much
it
loads,
it's
like
random,
so
yeah,
what's
the
chance
that
that's
the
exact
number
of
things
that
you
really
need
is
whatever
it.
A
Is
right
because
of
what
you
saw?
What
I
had
to
do
is
scroll
up
just
to
check
that
the
above
were
selected
as
well
right.
So
this
is
editing
a
issue
or
I'm
sorry,
issue
board
issues
and
what
you
can
see
here.
This
is
what
we
plan
or
we
are
doing,
which
is
the.
B
But
this
one
is
purely
per
page,
like
you
even
get
kicked
out
of
the
edit
mode
and
you
lose
the
checkboxes
if
you
navigate,
which
kind
of
is,
I
think,
better
than
leaving
the
checkboxes
there,
because
then
you're,
it's
clear
to
you
that
nothing
is
selected
like
you
were,
kicked
out
of
the
edit
mode.
Therefore,
there
is
nothing
selected
from
the
previous.
A
A
B
Would
too,
but
I
would
also
want
them
to
be
to
remember
what
I
already
checked,
like,
don't
just
uncheck
the
things
I
just
checked,
because
I
went
to
the
next
page.
B
Thing,
that's
worse
is
just
really
not
even
knowing.
A
Yeah,
let's
see
so
there's
two
options:
four
pages:
let's
see
where
was
that?
B
B
A
Yeah,
so
next
is,
I
have
kind
of
been
brainstorming,
different
layouts.
Well,
first,
I've
created
a
pixel,
perfect
or
sigma
file
to
start
from
that
way.
It's
like
you,
know
red
and
dry.
So
what
I
want
to
show
you
well
here,
let
me
go
back.
A
So
all
we're
showing
here
is
the
various
status
states,
as
well
as
here's,
which
I'll
show
this
in
an
actual
prototype.
But
then
we
have
column
sorting
in
the
header
and
then
here's
the
various
state
if
you're
re-importing,
and
we
can
certainly
change
this
I'll,
make
a
disclaimer
on
this
file
like
nothing's
set
in
stone,
but
here's
the
basics
we'll.
B
A
This
is
really
conceptual,
so
here's
the
idea
of
making
the
filter
field
a
little
bit
more
prominent,
and
this
could
be.
We
need
to
research
if
you're
likely
going
to
be
searching
for
a
particular
group,
or
what
else
would
you
do
so?
The
idea
here
is
that
you
can
select
what
you
would
like
to
filter
so
either
by
source
group
new
group
or
what
have
you,
if
there's
anything
else
to
sort
by
or
to
filter
by,
and
then
I've
added
this
bar
below
that's
similar
to
what
you
just
saw.
A
So
we
have
zero
selected,
you
can
select
your
entire
group
or
I'm
sorry
all
of
your
groups
and
perform
bulk
actions.
Of
course
that's
if
we
get
to
it
another
thing
I
added
so
hide
all
completed
to
me.
This
is
a
first
step
towards
using
the
tab
system
that
we've
talked
about,
and
basically
you
click
this
and
it
hides
all
the
complete
complete.
I.
A
B
You
know
exactly
what
it's
supposed
to
be:
it's
not
any
complicated.
It
needs
to
be.
A
B
So
one
one
one
piece
of
feedback
on
this
is:
we
should
be
cognizant
of
the
vertical
space
because
in
this
case
the
actual
content
versus
navigation
filters
and
other
things
seems
like
we
have.
Maybe
a
quarter
or
a
third
of
the
page
used
up
by
non-content
and
content
is.
B
B
You
know
maybe
having
a
small,
smaller
filter
that
pops
up,
if
it's
bigger
or
whatever
like
I
don't
know
what
what
the
things
are
that
we
could
do,
but
it
feels
like
we
have
like
one
two,
three
four
five:
six:
seven
lines:
seven:
bands
of
navigation
to
just
get
to
the
first
line
of
content.
A
I
don't
know
because
there
may
be
more
action,
so
I
hesitate
to
move
this
down
here
plus.
I
think
there
is
different
hierarchy
when
you
lay
this
out.
So
if
it's
kind
of,
if
the
user
wants
to
filter
by
a
specific
name
or
a
specific
word,
then
I
think
this
would
be
important
to
have
kind
of
prominent
but
I'll.
A
Well,
I
don't
I
hear
what
you're
saying,
but
I
don't
necessarily
agree
with
it
just
because
there
needs
to
be
some
level
of
hierarchy
and
if
you
start
putting
this
on
the
same
line
this,
what
happens
if
we
have
additional
actions,
so
this
is
the
most
flexible
in
my
opinion.
Well,.
B
I
can't
think
of
anything
other
than
the
selecting
the
new
group
like
the
selecting
the
parent
and
then
make
it
make
it
so
far.
Everything
on
this,
like
I,
don't
see
what
else
we
could
have
about
action
on.
Also
the
hide
all
complete,
I
think,
is
a
filtery
type
of
thing.
So
maybe
it
could,
like
you
know,
live
close
to
the
filter.
A
B
B
I
feel
like
that's
a
problem
for
me
in
a
lot
of
the
gitlab
ui,
like
the
fact
that
the
that
the
description
is
relegated
to
that
small
window
regardless
how
big
my
monitor
is-
and
my
descriptions
are
pages
and
pages
long
and
I
have
to
scroll
in
that
little
description
window
and
I
can't
make
it
bigger
or
anything.
A
B
Well,
if
you
just
go
to
your
issue
like
open,
any
issue
go
to
like
if
you
click
on
any
of
the
issues
and
look
at
the
description
and
just
well
yeah.
So
now,
if
you
edit,
the
description.
A
B
So
you
can't
make
it
bigger,
you
can
make
a
scroll,
you
can't
make
it
wider
longer,
and
I
think
we
do
have
like
even
your
patterns
that
are
out
there
outside
of
git
lab
are
all
about.
Well,
just
let
the
user
resize,
the
big
text,
edit
box
to
whatever
size,
makes
sense
for
them
as
opposed
to
fix
it.
So
I
feel,
like
I'm
bumping
against
that,
even
the
20
20
issues
per
page.
B
It
feels
very
constricting,
like
you.
A
A
B
Other
than
everywhere
else-
and
I
think
the
fact
that
we
remember
your
choice-
is
crucial
here,
so
I'm
okay,
if,
like
the
first
time
you
arrive
here,
it's
20
or
for
somebody
who
never
uses
this
like
it
really
doesn't
matter
what
it
is,
but
the
first
time
you
tell
us
that
you
would
like
to
see
50
next
time
and
we're
showing
you
50.
like
that
becomes
50.
B
B
I
think
she
did
say
there
was
no
particular
reason
for
that.
That
said,
it
is
that,
and
it
is
that
on
all
the
other.
So
if
we
change
it,
if
we
change
the
default,
then
it
probably
makes
sense
to
just
change
it
everywhere.
A
B
And
then
like
this,
like
this
experience
is
also
not
great,
so
hopefully
they
can
learn
something
from
things
that
we're
exploring,
which
is
ability
to
select
across
pages
and
also
have
a
selectable
page
size.
Maybe
they
would
move
away
from
the
this
infinite
load
scenario.
A
B
It
feels
a
little
out
of
space
to
be
on
the
title
line,
because
that
that's
I
would,
I
would
imagine
that
that
like
applies
to
like
this
table
like
like
a
closed
issue,
would
sit
there.
So
if
this
was
an
issue,
it
would
be
like
closed
issue,
so
it
would
be
like
close
this
table
or
something
that
would
just
change
the
table
itself,
not
the
not
some
of
the
items
in
the
table.
B
If
it
was
sitting
up
there
that
high,
I
think,
if
you
just
drop
it
down
to
the
next
line,
which
is
showing
1
out
of
20
and
163,
and
then
there
it
would
say
import.
20
selected
like
that
almost
reads
like
it's
on
the
same
level
like
reads
reads
as
a
sentence
like
well,
you
selected,
13
and
now
import
13.
That
feels
like,
even
if
it's
less
likely
more
appropriate.
B
But
we
I
mean
either
it
would
work
yeah
like
import
selected
and
then
somewhere
else.
You
say
how
many
selected
that
said,
maybe
we
would
want
to
show
those
two
things
close
to
each
other,
so
we
know
they're
related
like
something
over
here,
says
13
selected
and
then
kind
of
on
the
opposite
side
like
on
the
right
hand,
side.
It
says
import
selected,
but
I'm
visually
not
connecting
the
13
selected
and
imports
selected.
B
I
kind
of
have
to
look
left
to
right,
so
maybe
if
they
were
closer
to
each
other,
yeah
zero
selected,
then
after
that
or
select
yeah,
that
reads
better.
That
reads
like
okay:
13
are
selected
import,
these
selected
things
and
it's
not
like
all
the
way
on
the
other
side,
so
yeah,
okay,
I
like
it
much
better.
A
Another
thing
I'm
suggesting
is
our
grow
height
so
for
the
table,
so
this
is
53
pixels
tall,
which
is
a
smaller
version
of
our
table,
and
this
is
60
pixels
tall,
which
gives
like
a
little
bit
more
breathing
room
around.
All
of
that,
that's.
B
Personally,
I
do
like
the
more
condensed
version.
If
I
had
a
choice
of
like
you
know,
a
setting
for
the
table
that
says
show
me
condensed
table
was
just
showing
me
this
more
sparse
table.
I
would
select
the
condensed
because
it
doesn't
feel
cramped
at
all,
but
shows
me
two
more
things
which,
if
I'm
managing
a
lot
of
data,
I'm
all
about
data
density
and
just
showing
more
data
to
me.
A
Well,
let
me
let
me
review
the
visual
design
with
some
other
folks,
because
this
just
might
in
fact
be
too
tight
compared
to
what
pajamas
standards
are.
But
this
is
our
current
current
pixel
height
for
each
row.
I
I
don't
know
I'll
ask
around
and
then
this
is
just
oh,
okay,
here's
what
I
want
to
show
you.
A
So
in
this
case
I
have
separated
parent
and
subgroup
and
the
reason
why
potentially
is
for
filtering.
So
if
you
could
filter
by
a
subgroup
or
if
you
filter
by
a
parent
group
and
then
what
would
happen
potentially
we
could
have
the
reimport
button
there.
A
Another
thing
was
like
here:
we
go
like
how
does
one
get
to
this
next
group
so
right
now
I
just
have
subgroup
clickable.
Another
option
would
be
to
have
a
link
that
says
good.
I'm
gonna
have
to
space
space
this
out
a
bit
more,
but
then
we
could
have
an
overflow
menu
which,
like
you
know,
you
failed
you
whatever
we
want
to
put
them
in
because
right
now
it's
getting
super
cramped
and
I
didn't
even
put
in
the
projects
numbers.
A
I
can't
remember
what
those
icons
are
additional
metadata,
so
this
will
be
interesting
one
second,
but
I
just
thought
we
would
be
in
need
of
an
overflow
menu,
for
maybe
the
actions
that
are
secondary.
B
Well,
as
far
as
filtering
goes,
I
think
the
only
filter
that
we
have
heard
people
ask
for
was
the
from
source
group.
Like
that's
the
only
input
we've
got,
we
got
no
votes
for
any
other
filters,
well,
actually
status.
Sorry,
I
think
it
was
the
from
source
group
and
status.
The
parent
group
and
subgroup
are
destination,
they're
more
of
just
inputs,
so
they're,
my
inputs,
they're,
not
you're,
not
showing
me
data
that
exists
that
exists.
B
It's
the
data
that
I
want
to
input
to
make
something
happen,
so
sorting
by
my
input
is
not
as
interesting,
probably
as
sorting
by
like
the
data
that
is
intrinsically
there
like
this
group
is.
This
is
its
name.
This
is
where
it's
coming
from.
This
is
the
status.
Those
are
the
things
that
are
there
when
I
name
it.
I
can
just
change
that
all
the
time,
so
I
suspect
that
we
might
not
be
able-
or
we
might
not
need
to
implement
the
filter.
B
B
Yeah
filtering
by
one
thing:
for
now,
I
think
the
show
all
complete
is
a
nice
addition
to
that
filter,
because
that
way
I
can
just
hide
everything
or
hide
all
complete.
I
know
like
which
way
we
should
say
that,
but
yeah
so
be
able
to
hide
everything,
that's
completed
and
just
have
have
a
great
filter
there,
yeah,
because
I
think
if,
if
this
is
a
long-lived
thing,
it
may
get
really
like
a
lot
of
the
things
that
are
completed
and
only
a
few
that
are
left
to
be
done.
B
B
B
Well,
you
can
do
you
even
have
a
select
all
per
page
here
like
how
would
you
select
all
per
page?
Oh
there?
Okay,
I
missed
that
yeah.
I
I
mistook
that
for
one
of
the
line
items
okay.
So
now
there
selects
everything
on
this
page.
B
B
A
B
And
then
you
have
a
drop
down
that
says,
select
all
163
or
select
select
all
20
on
this
page
or
whatever
you
know
we
could
just
put
the
two
choices
there,
but
when
you
hit
the
select
hole
it
actually
has.
B
But
the
metaphor:
the
we're
talking
is
the
interaction
where
you
actually
have
a
drop
down
next
to
check
box.
So
the
check
box
actually
does
two
different
things
depending
on
which
way
the
drop
down
is
flipped,
and
I
wouldn't
hide
the
text.
I
would
put
the
text
there
like
potentially
have
a
check
box
that
says
right
next
to
it
select
all
163,
but
the
select
all
163
would
have
a
drop
down
next
to
it,
and
you
can
switch
it
to
20
on
this
page
as
opposed
to
all
63
all.
A
163.
is
it
the
fact
that
select
all
163
isn't
coupled
with
the
the
check
box,
the
select
all
checkpoints.
B
A
But
you're
you're
hiding
that
ability,
even
though
I
guess.
B
A
A
B
B
So
maybe
move
all
that
to
the
right
for
now
to
just
make
some
space
and
see
how
it
looks
so,
the
checkbox
would
have
the
words
next
to
it
that
used
to
be
in
the
button
so
to
the
right
of
the
checkbox.
You
could
have
text
similar
to
that
zero
selected.
That
just
says,
select
20
for
the
page
or
select
163.
B
Like
that
yeah
and
then
there
will
be
a
drop
down
next
to
that
text
to
the
right
of
the
text,
there
would
be
a
chevron
yeah,
and
you
know
you
could
engage
the
chevron
to
see
the.
B
B
B
B
I
just
won't
throw
it
out
there
see
if
it
sticks.
If
it
makes
sense,
because
then
we
would
combine
the
select
all
there
wouldn't
be
one
button
and
one
checkbox,
because
the
checkbox
also
didn't
tell
me
what
it
was
going
to
do,
whether
it
selects
all
or
not
like.
I
could
have
expected
by
selecting
the
check
box
that
all
the
pages
get
selected
yeah
that
one.
B
B
B
Reacting
to
things
I'm
saying
I'm
seeing
a
lot
of
good
stuff.
Do
you
wanna?
Did
I
notice
this
correctly?
Did
you
flip
the
words
on
the
check
box
that
is
show
all
complete
or
hide
all
complete.
B
I
would
say
that
you
come
in
and
everything
is
visible
and
then
you
want
to
filter
down
by
hiding
some
of
it.
So
I
like
this
yeah
that
makes
that
made
a
lot
of
sense
because
everything
is
visible
and
I
can
then
choose
to
hide
all
complete.
But
then,
if
I
was,
I
thought
that
if
I
selected
that
you
indicated
the
text
would
change
to
show,
meaning
that
you
know
that's
what
the
toggle
would
do.
B
B
B
I'm
I'm
kind
of
undecided
on
whether
to
separate
or
combine
the
two.
I
think
separating
does
introduce
one
thing,
and
that
is
now
we
have
them
to
name
these,
so
this
is
no
longer
a
destination.
B
A
B
B
A
B
Tell
us,
like
some
things
may
earn
their
way
in
by
users
telling
us
that's
what
they
want
right.
A
Right,
okay-
and
I
showed
you
so
I'll-
just
continue
to
work
through
that-
I
really
want
to
create
a
prototype
and,
at
the
very
least,
get
ready
for
user
testing.
All
you
know
if
we
even
come
up
with
more
concepts
between
now
and
then
great,
but
that
is
my
goal.
That's
my
top
goal.
I
think
this
this
milestone,
so
so
here's
the
interesting
user
interview
that
talks
about
project
and
group
import
specifically
github
integration.
So
if
you
just
want
to
watch
it's
just
like.
A
B
Oh,
oh,
okay,
so
it
looks
so
perfect
table
spec,
okay,
not
features
but
pixels
right,
yeah,
okay
got
it.
B
Remove
the
external
icon
yeah,
I
I
I
think
I
think
we
kind
of
talked
a
little
bit
about
it,
and
I've
convinced
myself
even
more
so
that
you
know
this
is
what
the
web
standards
are
and
also
what
our
figma
standards
are
yeah.
I
think
in
this
case
it
just
needs
to
be
an
external
icon,
because
this
is
an
external
system,
even
if
it's
under
instance,
of
git
lab
it's
it's
a
different
instance
of
git
lab.
Therefore,
it's
not
it's
not
internal.
Like
it's
different
login,
it's
a
it
may
look
different.
B
B
Not
not
to
not
to
well,
we
just
talked
about
it
in
planning
as
well.
Github
bitbucket,
all
the
other
importers,
are
also
going
to
have
this
external
icon
on
the
left
side.
So
if
we
want
to
be
consistent
and
not
make
it
confusing
for
the
users,
we
you
know
would
probably
follow
the
pattern.
For
that
reason,
too,.