►
From YouTube: Manage:Import 13.10 planning
Description
This is the sync planning session for the 13.10 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17311
Notable epics mentioned:
Complete Epic migration - https://gitlab.com/groups/gitlab-org/-/epics/5189
A
A
A
I
think
it
helped
that
we
really
broke
down
a
lot
of
the
issues
to
the
smallest
components,
which
means
that
you
know
this
is
a
good
number
for
for
for
two
potential
reasons
and
either
one
is
good
either
we
really
just
ship
more
than
usual
or
we
were
really
good
at
breaking
down
and
iterating,
and
you
know
having
smaller
issues
a
lot
of
smaller
issues
so
they're
both.
I
think
good
trends.
A
A
A
You
know
importing
those
in
like
a
single
click
being
able
to
see
more
things
being
able
to
see
good
status.
So
all
of
these
things,
there's
are
at
kind
of
various
stages,
from
importer
to
importer.
It
is
not
a
unified
experience
and
I
would
like
to
maybe
step
away
a
little
bit
from
looking
at
the
other
importers
in
this
aspect,
because
I
feel
like
we're
making
progress
in
slightly
different
direction,
each
one
of
the
importers
as
we
address
one
issue
at
a
time.
A
I
would
like
for
us
to
just
really
focus
on
this
experience
for
the
group
migration.
So
let's
just
focus
on
group
migration,
because
that
isn't
focus
of
off
the
team
right
now
and
get
that
experience
to
be
the
one
that
we
really
like.
So,
if
selectable
page
size
and
how
that
works
is
good,
then
we
should
make
it
work
here.
If
additional
information
like
oh
you're,
viewing
one
or
you
know
you
review
in
groups
20
to
40
out
of
100,
like
all
of
that
text,
the
ability
to
select
and
then
hit
import
all.
A
I
want
us
to
make
that
kind
of
as
perfect
as
possible
here
and
really
cook
and
bake
that
experience
in
the
group
migration
and
then
it
will
be,
I
think,
easier
to
then
go
and
say:
do
kind
of
a
cookie
cutter
translation
of
that
into
github
importer,
bitbucket
import,
other
importers.
So
I
feel
like
we
should
really
focus
on
this
one
and
make
it
all
work
together,
because
you
know
the
page
size
would
be
able
with
the
ability
to
select
and
then
hit
import
all
button.
A
C
Yeah
I
would
like
to
jump
in
because
I
believe
I
have
two
more
issues
to
bring
which
perfectly
aligns
with
your
vision,
and
I've
actually
mentioned
them
in
a
comment.
The
first
one
it
was
like
it
is
to
maintain
import
status
across
reloads.
It's
something.
We've
discussed
it
previously
that
right
now,
if
we
hit
refresh
or
user
just
leaves
the
page,
we
simply
do
not
have
an
ability
to
see
the
status
of
previous
group
imports
at
all.
So
it
is
a
quite
big.
Well,
not
too
big,
but
big
issue.
C
C
So
I
think
I
would
like
you
to
consider
these
three
issues
also
to
prioritize
before
the
list
you've
mentioned,
which
are
important
but
small
improvements
here
and
there,
but
I
feel
like
these
two
ones
ability
to
leave
page
and
at
least
to
see
what
happens
and
the
ability
to
properly
see
errors.
Will
be
definitely
quality
of
life
improvements.
A
In
the
list
here-
and
we
can
talk
about
priority-
I'm
like
between
these
I've
assigned
like
p1p2p3
priorities
on
these-
and
I
feel
like
those
general
buckets-
are
correct,
but
like
two
different
p2
priorities,
it
probably
is
anyone's
call
as
to
which
ones
we
should
work
on.
First,
if
you'd
like
to
prefer
to
work
on
these
two
in
you
know,
when
you
get
to
the
bucket
of
the
priorities
where
they
live,
then
that's
fine,
so
you
know
you
could
prioritize
these
on
top
of
all
the
other
b2s.
A
So
yeah,
so
that's,
that's
that's
good.
I
think
I
think
we're
all
kind
of
coalescing
around
that.
Having
talked
for
a
couple
of
weeks
about
all
the
things
that
we
want
to
do,
I
feel
like
talking
about
other
importers
is
a
distraction
and
you
know
it's
going
to
introduce
similar
but
not
exact,
same
solution
and
experience.
So
I'm.
B
Not
sure
if
it's
exactly
a
distraction,
just
something
to
be
to
keep
in
mind
right,
I
mean
just
to
circle
back
to
the
pagination
stuff,
you're
speaking
specifically,
to
like
make.
Let's
focus
on
these
improvements
to
pagination,
specifically
for
the
group
import
not
taking
into
account
its
effects,
perhaps
on
the
import,
ui
yeah.
B
A
Yeah
yeah!
Yes,
no
not
this
time,
so
I'm
saying
maybe
play
those
play
all
these
issues
out
against
each
other
because
they
do
build
on
on
each
other.
You
know
they
they
interact
with
each
other
and
build
on
top
of
each
other.
So
I
think,
by
the
time
we
implement
these
here,
we
will
know
sort
of
a
lot
more
about
what
the
experience
should
be,
because
we
might
experiment
we
might
try
things
out
and
not
like
it.
A
So
I
would
like
to
just
do
that
in
one
spot
and
it's
in
this
spot
and
then
once
we
have
that
then
go
back
and
update
github,
because
we
do
have
issues
against
github
as
well
to
implement
a
lot
of
the
same
things.
I
just
don't
want
to
work
on
them,
sort
of
in
in
parallel
or
slightly
in
different
directions.
C
B
B
C
Yeah
and
but
I
still
would
like
at
least
to
wait
at
least
for
one
milestone,
because
I
still
don't
have
a
100
opinion
how
much
code
we
should
be
definitely
able
to
share,
because
from
what
I
see
how
group
importers
grows,
it
might
grow
to
totally
another
direction
like
we
will.
Some
have
some
reports,
pre-import
post-import
and
I'm
not
sure
that
we
will
have
a
lot
of
such
functionality
in
a
group
in
a
project
imports.
B
Yeah-
and
I
don't
think
the
effort
specifically
has
to
do
with
the
code
itself
more
just
along
of
how
we
envision
the
experience
to
be
between
groups
and
projects
right.
So
if
we,
if
we
know
for
if
we
know
that
we
want
to
you,
know,
have
both
be
distinct,
different
experiences,
one
having
infinite
score
versus
others,
having
user
selectable
page
size
and
that's
that's
fine,
but
then
we
should.
B
C
What
I
feel
is
that,
as
soon
as
we
implement
this
quality
of
life
improvements
in
group
import-
and
we
feel
like
this-
okay,
this
works
for
us
and
we
are
really
happy
with
how
it
works
it.
I
don't
know
how
many
milestones
it
will
take.
It
would
be
at
that
precise
point
when
we
will
want
to
say:
hey,
let's
reconsider
how
and
how
many
of
this
functionality
should
be
ported
to
the
projects
is
that's
like
how
I
feel
right
now.
D
A
A
So
if-
and
you
know,
potentially
the
group
migration
importer
may
have
a
feature
of
a
pre-import
check
where
you
know
we
may
run
a
report
and
show
you
what
will
get
imported
and
some
other
employer
may
never
get
or
may
get
it
in
the
future.
So
there
may
be
features
that
will
not
be
available
in
other
importers,
but
as
much
as
there
is
commonality
there's
a
lot
of
commonality.
A
The
experience
should
be.
You
know,
hopefully
exactly
the
same,
so
you
know
how
it
looks
how
it
paginates
like
that,
should
not
be
different
between
the
importers.
You
know
the
alignment
the
table.
Do
we
have
sorting
columns
or
not
like
all
of
these
things
should
be
able
to
be
translated.
So
again,
there's
there's
depth
to
some
of
these
importers.
That
may
not
be
the
same
across,
but
the
experience
should
be
as
as
similar
as
possible,
because
you
don't
want
the
user
to
have
to
learn
a
slightly
different.
A
You
know
ui
flow
for
each
one
of
these,
so
that
is
the
goal
from
the
user
perspective.
If
that
means
that
we
should
try
to
like
have
a
base
importer
flow
that
everybody
inherits
from
like
you
know,
that's
really
a
technical
question:
how
you're
going
to
do
that,
but
I
would
I
do
want
to
end
up
in
a
position
where
it
feels
and
behaves
the
same
way
across
all
the
importers.
A
A
A
This
group,
migration
and
github
should
because
they
also
are
very
similar
importers,
they're
importers,
where
you
connect
to
a
remote
instance,
and
you
do
one
click,
and
then
it
just
pulls
things
over,
whereas
these
file-based
ones,
it's
just
different
experience.
You
have
like
upload
a
file,
download
file
and
do
things
so
it's
okay.
If
they
stay
on
the
island
technically,
so
that
they're
easier
to
deprecate
or
vice
versa,
yeah.
B
I
think
so
so
I
mean
let
me
I
can
also
just
state
my
intent
with
the
questions
is
that
you
know
if
we
experiment
with
quality
of
life
improvements
in
group
import,
then
I
would
imagine
in
a
milestone
or
two
as
we
see
how
these
things
progress
and
how
they
perform
in
production.
We
have
some
decision
or
information
to
reflect
on
on
whether
or
not
there
should
be
like
the
project
importers,
for
example
right.
I
just
want
us
to
to
be
very
aware
of
that,
so
that
we
don't
find
ourselves.
B
You
know
maybe
not
paying
as
much
attention
as
we
should
and
we
perhaps
have
more
than
two
different
versions
of
the
same
application
and
then,
when
we
want
to
roll
out
pages
user,
select
pagination,
we
have
to
do
it
two
three
four
times
right
because
to
the
user.
It
seems
like
a
consistent
experience
and
that's
what
we
want
to
deliver
with
them.
But
under
the
hood
we've
we
weren't
paying
attention
on
how
to
like
share
as
much
as
possible
since
we
do
want
to
share.
B
A
B
A
Good
and
finally,
we
have
a
bucket
of
kind
of
technical
technical
improvements.
We've
called
this
thing
a
few
different
things,
but
these
are
things
that
we're
kind
of
left
over
from
as
we
implement
as
we
implemented.
The
mvc-
and
I
know
the
three
that
we
have
discussed
is
the
network
rate
limits
working
around
those
being
able
to
distribute
the
migration
execution
and
one
we
talked
about
before,
which
is
clean
up
the
temp
data
from
complete
imports.
A
So
if
there's
something
else,
that's
more
important,
we
can
definitely
substitute
one
for
the
other,
but
that's
basically
the
flavor
of
what
1310
is
now
how
I
think
about
it
and
how
I
would
like
for
you
to
sort
of
put
all
this
in
context
of
the
bigger
thing:
we're
accomplishing
I'll,
just
walk
through
a
little
bit
of
a
direction
and
the
mission
for
for
the
group,
the
three
categories
that
we
have.
You
know
we
are
perfect.
A
You
know
on
purpose,
ignoring
templates
and
internationalization,
one
for
bandwidth,
issues
with
engineering
and
the
other
one
sort
of
as
a
way
to
focus
on
one
thing
at
a
time
and
then
do
a
lot
of
impact
in
one
area
as
opposed
to
spread
out
throughout,
so
really
we're
focusing
on
the
import
on
the
importers
and
then
on
the
importers,
we're
really
paying
attention
to
the
migration,
the
new
migration
effort,
and
if
you
just
kind
of
follow
through
you
can
you
can
get
to
this
yourself.
I
hope
that
you
know.
A
A
I
expect
most
users
would
be
just
like
testing
the
waters
and
checking
out
what
it
is,
because
it's
not
it
doesn't
have
enough
depth
to
to
get
some
real
traffic
or
to
be
a
viable
alternative
to
the
group
export
import
that
we
currently
have
so
really.
The
first
goal
is
to
get
to
the
parity
with
that.
A
So
I've
split
it
between
sort
of
the
metadata,
the
issues
and
comments
and
things
like
that
and
then
kind
of
the
code
migration.
So
these
are
the
two
different
areas,
but,
prior
to
that,
I
actually
want
to
pivot
after
reaching
the
parity
and
then
offer
something
that
doesn't
exist
in
group
export
import.
A
So
not
just
do
the
things
that
we
already
do
but
like.
Let's
do
something
that
we
don't
do,
but
people
have
asked
for,
and
I
think
this
will
actually
really
give
it-
give
it
a
lot
of
getting
to
users
migration,
so
I
don't
think
we're
there
yet
in
1310.
I
don't
think
we
should
start
looking
at
it
yet,
but
I
think
next
time
around
when
we
talk,
we
might
be
still
working
on
this
mainly,
but
this
may
be
something
for
us
to
start
refining
discussing
and
seeing
what
is
the
nbc
here?
A
A
It
is
something
I
want
to
do
all
along,
so
we've
been
definitely
putting
a
lot
of
effort
into
ux
all
along,
and
we
will
continue
to
do
that,
but
there
will
be
some
things
that
you
know
it's
not
going
to
make
sense
to
do
ahead
of
actually
having
functionality.
So
for
the
very
kind
of
end
of
this,
we
will
definitely
try
to
get
this
to
a
really
great
experience.
A
A
They
all
kind
of
belong
to
the
group
level,
so
group
labels
epics
boards,
you
know
badges
different
things
and
then
finally,
something
that
I've
added
recently
is
also
providing
an
api
so
that
the
professional
services
group
can
actually
start
utilizing
this
and
switching
from
the
file
based
export
import
to
to
the
group
migration
using
their
using
the
api.
We
are
going
to
add
to
it,
so
that
is
kind
of
the
overall
run
for
for
that
and
even
more
kind
of
granularly
we
are
here
now
we
are
doing
the
epics.
C
A
A
I
guess
I'll
just
keep
talking
yeah,
so
maybe
I'll
just
move
on
from
from
reviewing,
I
feel
like
we've
just
really
talked
about
everything.
That's
there.
If
you
go
look
at
the
epic
and
as
you
drill
down,
you
will
see
things
and
things
at
top
are
prioritized.
First,
I
mean
that
epic
really
tells
the
story
of
what
we're
trying
to
get
done
and
in
what
order
we're
trying
to
get
things
done
so
for
1310.
A
So
I
expect
us
to
maybe
get
one
or
two
additional
things.
I
do
expect
these
issues
to
also
get
broken
down
into
smaller
issues,
as
we
refine
them
just
the
same
way,
we've
done
with
epics,
it
seems
like
it.
You
know
we
end
up
with
several
issues
for
each
one
of
these,
so
that
probably
is
going
to
be
the
extent
of
how
far
we
get
through
the
parody.
A
Hopefully,
then,
the
next
milestone
will
talk
about
completing
the
parody.
So
I
feel
like
this
is
going
to
be
the
milestone
where
we
move
out
of
the
epics
and
into
all
of
the
other
little
things
we
need
to
get
done
and
then
past
that
we'll
hopefully
be
able
to
complete
it
in
13,
11,
ish
or
so,
and
then
really
start
talking
about
users
around
1311
and
planning,
then
refining
that,
while
we're
completing
the
parody,
let
me
see,
can
I
is
there
a
way
to
share
something
else.
A
A
I
see
that
now
a
few
things
have
moved
into
ready
for
development.
Probably
as
I
was
speaking
because
this
morning,
I
think
we
had
like
three
or
four
things
in
ready
for
development,
which
means
we
really
were
able
to
clear
that
out
for
13
thirteen
nine.
The
refinement
has
so
I've
filled
up
the
refinement
to
to
the
brim
in
in
order
to
sort
of
support
having
a
healthy,
healthy
backlog
for
things
to
move
into
ready
for
development.
A
So
it
looks
like
we
are
already
kind
of
picking
things
and
things
are
moving.
So
that's
good!
These
are
you
know,
and
these
are
in
the
right
order.
I
have
reviewed
the
refinement
column
this
morning,
just
to
make
sure
that
it
is
the
things
that
correspond
to
what
I
showed
so
what
I
showed
earlier
on
the
planning
issue.
A
You
will
find
those
issues
in
ready
for
refinement
already
for
development,
like
those
are
two
columns
where
you'll
find
everything
that
I
talked
about
this
morning.
In
addition
to
those,
there
are
a
few
small
randomness
things
here
that
we've
been
sort
of
dragging
around
and
I'm
I
I
moved
out
a
lot
of
the
things
that
I
felt
we
shouldn't
be
worried
about,
or
we
shouldn't
do.
I've
left
a
few
things
in
there
sort
of
because
they
just
need
to
happen.
A
I
mean
they
didn't
have
to
happen
in
a
particular
milestone,
but
they
just
need
to
need
to
happen
and
move
off.
So
in
addition
to
what
I've
talked
about
there,
there
are
a
few
random
things
here.
So
as
you
look
for
kind
of
little
breaks
between
the
big
things
or,
if
you're
looking
to
fill
your
time
with
something,
there
are
a
few.
A
If
you
scroll
down
to
like
the
p4
you're
going
to
find
things
that
are,
you
know
not
as
not
as
important,
but
they
just
need
to
at
some
point
get
done
and
one
of
them
I'll
just
call
out.
You
know
we
don't
do
internationalization
issues
as
far
as
we're
doing
any
new
internationalization
features,
but
we
do
still
have
to
kind
of
maintain
the
infrastructure
and
things
just
need
to
still
work.
A
So
I
feel,
like
that's
still
going
to
be
helpful
to
us
to
at
some
point,
do
that
so
things
like
that
are
going
to
hang
around
the
p4
area
and
I'm
okay
with
you
cherry-picking
from
here.
If
there's
something
that
you
feel
like
hey,
I
should
really
just
maybe
take
a
break
and
do
something
like
enforcing
the
dot
git
extension
in
the
url
when
importing
the
repos,
because
apparently,
if
we
don't
things
break
so
you
know
small
things.
A
I'm
gonna
leave
there,
but
the
majority
of
the
things,
especially
the
ones
prioritized
as
p1s
and
p2s,
are
going
to
be
tied
to
the
direction
and
then
in
the
p3s
you'll
find
some
of
these
kind
of
things
that
don't
have
to
happen
in
this
particular
release,
but
should
happen.
You
know
at
some
point
and
they're
not
necessarily
delivering
large
value
for
the
direction,
but
they
are
moving
us
in
the
direction
of
direction.
So
the
board
is
ready
to
go.
A
It's
a
good
time
to
have
those
discussions
like
dennis
and
thanks
for
bringing
up
the
questions
about
about
sort
of,
you
know
how
we're
gonna
structure,
our
importers
and
user
experience
and
all
because
you
know
sometimes
just
you
have
to
be
prompt
and
be
able
to
talk
back
and
forth
a
little
bit
to
to
get
to
the
bottom
of
some
of
these
things.
So
if
there's
anything
like
that
that
we
want
to
talk
about
it's
a
good
time,
if
not,
this
may
be
it.
A
So
I
do
have
a
final
question
for
the
team
and
that
is
kind
of
size-wise.
Does
it
make
sense
what
I
said,
which
is
you
know
we
should
be
able
to
complete
the
epics
migration
and
make
a
good
dent
on
the
rest
of
the
parity,
so
that
maybe
next
time
around,
we
might
be
able
to
get
to
the
end.
Of
that
I
mean
this
is
sort
of
what
that
looks
like
so
here's
the
epics,
which
is
mostly
13
nine,
like
two
issues,
are
going
to
spill
over,
but
then
these
are.
A
D
D
A
Yeah
so
I'll
be
speaking,
I
think
today
later
today
to
to
into
a
call
telling
everybody
what
what
we
think
we're
going
to
get
done
in
1310,
so
I'll
be
relaying
what
I
just
relate
to
you.
I
just
want
to
make
sure
that
you
call
me
out
if,
if
you
don't
feel
comfortable
me
saying
things
like
we're,
gonna
complete
the
epics
and
we're
gonna,
you
know
probably
get
through
another
good
chunk
of
this
epic
of
the
overall
parity,
epic.
In.