►
From YouTube: Manage:Import 13.12 planning
Description
This is the sync planning session for the 13.12 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17325
Notable epics mentioned:
Complete Epic migration - https://gitlab.com/groups/gitlab-org/-/epics/5189
A
Hello
welcome
to
1312
planning
for
imports.
When
we
planned
1311.
Last
month
we
didn't
know
there
was
going
to
be
1312,
but
here
we
are
except
for
imports.
These
numbers,
don't
don't
have
meaning
as
much.
A
So
I'm
gonna
go
ahead
and
shift
my
screen
and
just
kind
of
walk
through
the
plan
for
the.
A
Meeting
so
the
planning
issue
for
1312
looks
a
lot
like
1311,
so
that
may
be
something
to
keep
in
mind
as
we
talk
about
things.
A
Team
velocity
has
been
updated.
The
objectives
have
left
the
same
because
I
feel
like
we
really
haven't
accomplished
much
of
the
objective
from
the
last
planning,
so
maybe
we'll
just
start
an
order
and
talk
about
the
pto
and
see
if
there's
anything
that
we
should
consider
as
we
talk
about
what
we're
going
to
do
next.
B
C
C
We
have
a
friends
and
family
day
coming
up.
Yes,
I
think
it's
mid-april,
I
don't
remember
the
exact
date.
A
Okay,
so
I'm
really
not
a
lot
there.
The
velocity,
if
you
look
at
this
velocity
by
milestone,
ignoring
1311,
which
is
in
progress,
because
we
can
never
have
anything.
It's
always
at
the
end
of
that
that
we
bank
it
looks
like
we
have
worked
on
a
similar
number
of
issues
between
13
9
and
13
10,
but
the
weight
has
dropped
so
either
they've,
gotten
smaller
or
we've
gotten
several
issues
in
there
that
didn't
have
a
weight
like
community
contributions
or
just
like
emergencies
that
we
didn't
estimate.
A
So
that
does
seem
like
a
little
bit
of
a
notable
thing
there.
But
then,
what's
really
notable
to
me
is
that
the
velocity
for
the
last
30
days
and
I've
just
for
reference
left
the
last
month,
the
last
disorder
to
see
where
we
are
so
it
seems
like
there
was
a
big
drop
in
what
we
were
able
to
bank
in
the
next
in
the
last
30
days.
E
Well,
I
can,
I
can
speak
from
my
side
is
there
has
been
a
lot
of
back
and
forth
with
the
implementation,
with
the
challenges
that
we
discussed
yesterday.
Essentially,
there
has
been
spikes
over
spikes
discussions
between
me
and
cassio
on
how
to
approach
this
paginations.
There
are
challenges
with
less
pagination,
sorry
nested
associations
within
the
group
and
that
attributed
to
a
lot
of
time
spent
trying
to
figure
out
what
to
do
next
and
yeah.
No,
I
would
say:
that's
that's
mainly
the
reason.
Okay,
so.
A
A
D
D
So,
although
it's
just
one
issue
but
that
issue
kind
of
blocked
me
for
a
long
time,
because
it
required
a
lot
of
polishing
on
the
marriage
request
and
a
lot
of
back
and
forth
on
how
to
implement
the
fuel
configuration
stuff
on
that
matter
as
well.
So,
besides
everything
that
george
mentioned,
there
is
a
concurrent
model,
that's
taking
longer
than
imagine,
and
besides
that
I'm
also
kind
of.
D
Trying
to
manage
my
time
between
those
things
and
the
import
from
storage,
which
is
a
big
feature
and
george
helped
me
with
that.
But
this
will
also
take
much
of
my
time,
starting
last
week,
end
of
last
week
and
this
week.
So
it's
a
few
contributors
on
on
the
matter
and
the
size
of
the
team
being
only
two
it's
hard
when
work,
bios
piles
should
be
done.
A
D
A
So
is
it
fair
to
say
that
once
we
get
past
the
deep
nesting,
so
once
we
figure
out
what
the
pattern
is
there,
then
you
know
we
should
be
able
to
go
back
to
you,
know
normal
programming,
or
will
there
be
potentially
more
spikes
and
things
that
need
to
be
figured
out.
D
I
think
we
should
be
able
to
get
back
to
normal
programming,
but
besides
that,
the
number
of
other
features
supporting
issues
it's
piling
up
so
from
time
to
time
we
have
to
fix
those
things
which
impact
as
well.
The
change
of
context
mainly
impacts
on
the
velocity,
as
I
mentioned.
D
I
think
a
piece
of
that
is
because
of
the
size
of
the
team
that
we
try
to
keep
the
same
velocity
that
we
had
when
we
were
three
but
it's
starting
to
pay
its
price.
A
Please
feel
free
to
just
say
that
and
if
there's
anything
that
can
be
done
we'll
see
because
there
could
be
some
other
things,
there
may
be
lesser
priority:
we're
paying
attention
to
somewhere
else,
and
we
can,
you
know,
talk
about
it
on
the
pm
side
potentially
and
say:
okay!
Well,
you
know
yeah.
E
E
I
think
well
on
the
board.
You
can
probably
see
the
trail
of
comments
and
the
issues
that
have
been
created
throughout
this
whole
process.
I
think
it
all
started
with
me
working
on
migrating
notes,
epic
notes
it
kind
of
highlight
it
and
and
then
follow
up.
It
highlighted
the
problem
and
I
left
a
few
comments.
Then
we
started
discussing
viscasio
this
problem
and
then
we
created
that
issue
that
we
reviewed
yesterday
right
but
yeah.
E
B
C
A
And,
as
you
said,
you
have
no
plan
time
off,
so
you
should
be
able
to
yeah
okay,
so
that
makes
sense
so
the
objectives
I'll
just
go
over
them
so
that
we
are
kind
of
all
on
the
same
page,
but
it
is
really
just
trying
to
get
to
this
parity
with
the
old
group
export
import
so
that
we
can
use
the
migration
instead
of
group.
Export
import
is
kind
of.
A
A
What's
really
working
on
this
milestone
is
just
completing
the
epics
migration,
and
so
do
we
feel
like
this
might
actually
be
completed
past
these
spikes.
Or
is
this
still
going
to
take.
D
D
We
have
yet
to
break
down
what
we
learned
from
those
spikes
and
that
issue
where
I
mentioned
other
engineers,
I'm
kind
of
holding
a
little
bit
to
transform
that
in
an
epic
just
because
there
are
some
engineers
who
input
some
stuff
from
yesterday
today,
I'm
giving
some
questions
so
until
we
really
decided
for
that
approach,
I
wouldn't
do
any
promises
just
to
be
safe,
but
my
feeling
my
gut
may
seems
to
be
that
in
this
release
we
would
be
able
to
deliver
the
the
epics,
and
since
we
are
going
to
migrate,
the
whole
epics
with
the
file
should
be
done
in
one
go,
but
I
might
be
missing
something
here.
D
E
Yeah,
I
think
that
the
work
that
needs
to
be
done
is
affecting
all
of
the
relations
of
group
and
project
like
the
export
side
will
basically
be
universal.
It's
not
only
epics.
It's
going
to
be
all
the
all
the
relations
which
is
beneficial
moving
forward,
which
will
allow
us
moving
stuff
over
faster
right,
but
yeah,
I
would
say
so.
It
all
depends
on
how
we
break
it
down
and
how
fast
is
the
review
process
is
because
it
can
get
quite
back
and
forthy.
To
be
honest.
E
Well,
like
I
still
mentioned
three
weeks
from
one
more
request
to
be
reviewed,
I
mean
these
things
can
can
impact.
I'm
not
saying
that's
the
only
thing,
but
I'm
just
saying
that
yeah,
I'm
feeling
confident,
but
anything
can
happen.
D
I
I
just
want
to
highlight
that
the
feeling
is
mutual
and
it
summarizes
very
well
the
situation.
I
think
we
are
confident,
but
there
is
some
might
have
some
unseen
stuff
yet
so
I
wouldn't
put
all
my
coins
in
the
same.
A
Make
sense
so
on
the
ux
improvements
for
1311
this
is
for
last
month.
What
we
put
in
here
was
this-
and
I
just
kind
of
left
these
here,
because
they
will
continue.
They
haven't
really,
you
know,
probably
gone
down
in
priority.
A
A
You
know
the
technical
debt
not
sure
if
there
is
bandwidth
or
desire
to
do
anything
here
in
this
milestone,
or
will
we
just
complete
the
the
spikes
and
then
move
on
with
some
future
work
before
we
come
back
to
this,
and
this
must
my
suspicion
so
maybe
not
as
much
of
this
but
definitely
cleaning
some
of
this
up
the
front
end
backlog.
A
Finally,
you
know
security
and
bugs,
as
they
come
up,
things
are
coming
up
like
we
have
been
focused
on
future
work
and
seeing
as
soon
as
you
have
focused
for
some
time,
people
start
just
tapping
on
the
shoulder.
A
So
there
are
a
few
things
just
coming
up
like
someone's
already.
I
think
one
is
already
in
development,
as
I
mentioned,
and
there
may
be
others,
so
this
is
just
going
to
be
probably
a
small
string
of
distractions
throughout
the
time.
Yeah.
D
A
Milestone
sorry.
D
We
should
add
the
import
from
object,
storage
as
well,
because
that
feature
is
a
little
bit
big
and
we
don't
have
any
structural
code
for
that
yet,
and
although
it's
at
least
at
the
moment,
just
one
issue,
I'm
planning
to
break
it
and
deliver
in
a
more
directive
way
to
avoid
large
mesh
request
with
large
time
to
do
and
all
those
things
and
do
the
size
of
the
team.
I
think
it's
important
to
make
it
explicit
in
the
planning.
A
So
this
is
only
for
the
request
right.
This
is
part
of
that
big.
Let's
just
all
do
this
now,
so
we
have
the
issue
that
is
I'll,
find
the
issue
number,
but
I.
C
A
So
yeah
it's
good
to
call
out
the
you
know
now,
with
our
plans
just
having
moved
a
little
bit
more
into
the
future.
I
don't
think
we're
going
to
be
doing
any
kind
of
deprecation
of
anything
group
export
import
related
in
14
0,
but
we'll
be
on
the
lookout
for
when
we're
able
to
at
least
deprecate
the
first
part
of
it,
which
is
the
group
export.
A
So
we
should
keep
this
in
the
back
of
our
minds
and
it
doesn't
have
to
necessarily
be
a
15-0
when
we
do
that,
we
can
start
up
anything
sooner.
The
deprecation
of
json
in
favor
of
nd
json
is
that
something
that
we
feel
comfortable
with.
D
E
D
B
A
A
I
was
just
putting
this
here
in
case
that
during
13-12
we
do
any
work,
but
I
don't
think
that
we
should
do
that
like
the
fact
that
it
still
just
sort
of
works
and
we're
just
saying
it's
not
supported,
I'm
not
offended
by
that.
A
Okay,
so
with
that
in
mind,
I
think
we
can
take
a
look
at
the
board,
so
the
board
itself.
A
I
have
not
put
any
more
things
into
refinement
because
I
felt
like
you
know
we
haven't
really
moved
much
out
of
it
and
even
like
the
p1
item-
that's
that's
in
it.
It's
been
sitting
there
for
a
couple
of
weeks
now,
so
I
didn't
want
to
just
add
anything
on
top
of
this
until
we
figure
out
a
way
to
move
this
work
forward.
A
A
A
So
with
that
in
mind,
this
border
looks
very
much
the
same
as
it
did
a
month
ago
when
we
looked
at
it
with
some
things
having
moved
forward,
but
the
things
that
were
in
in
these
columns
are
still
going
to
be
there
just
again,
if
you
would
consider
looking
at
this
p1.
That
would
be
great
other
than
that,
I
would
say
just
work
on
the
priorities,
as
we
lay
them
out.
D
Can
you
expand
the
blocked
column?
Please?
Yes,
I
think
it's
related
to
that
b1,
the
north
star
metric
thing.
There
is
a
important
matrix
needs
of
need
optimization
between
there.
D
So
adding
more
indexes
in
there
seems
unpractical
and
database
team
mentioned.
That
would
be
nice
to
avoid
that-
and
I
agree,
that's
why
I
proposed
in
there
extracting
the
data
that
we
need
to
do
those
calculations
to
another
table.
This
way,
having
a
smaller
set
of
data
to
to
run
the
metrics,
though
this
seems
to
be
a
good
solution,
it's
a
large
implementation
to
be
done
not
in
the
size
of
the
code
itself,
but
in
the
management
of
the
change,
because
it's
a
migration
from
the
biggest
tables
of
our
database.
D
I
would
like
to
work
on
that,
but
since
the
import
from
story
seems
to
be
a
little
bit
more
important,
I'm
focused
on
that
one
first,
and
there
is
also
the
migration
tool
that
we're
doing
so
with
all
those
things.
I
never
got
the
time
to
work
on
this,
and
this
is
a
little
bit
generic,
although
it's
grouping
parts
main
focus,
but
it's
a
data
structure
thing.
So
I
mentioned
all
that
to
share
and
see
if
you
can't
find
any
other
groups
that
can
help
us
with
that.
D
If
you
could
would
be
nice,
there
is
a
little
bulk
in
there
on
how
the
extraction
could
be
done
because
with
the
size
of
our
team,
it
seems
impractical
to
to
do
this.
A
That's
a
good
point,
so,
thanks
for
bringing
that
up,
I
will
start
talking
to
william
first
and
see
see
what
might
be
our
next
steps
on
on
that.
That
said,
you
know,
I
wonder
if
there
is
a
smaller
step
like
maybe
there
is
an
index
we
can
put
in
just
one
more
before.
We
then
go
and
do
this
because
it
may
be
a
long
time
before
we're
able
to
take
the
large
step.
A
E
D
Iteration
mode
and
trying
to
do
a
smaller
step.
First,
I
even
propose
that
in
there
and
mention
some
database
and
product
intelligence
people
to
see
if
they
could
come
with
some
other
solution,
since
no
one
replied
directly
and
mikhail,
I
actually
replied
that
this
seems
to
be
the
better
plan.
The
best
plan.
D
A
A
So
if
there's
a
way
for
us
to
proceed
with
this
and
then
if
we
need
to
go
back
and
fix
up
two
spots
in
the
end,
it'd
be
fine
with
me.
This
is
really
a
you
know:
high
priority
for
the
pm
management
team
in
order
to
be
able
to
see
our
usages.
So
this
is
like
you
know
one
of
the
few
things
that
just
hasn't
been
done
where
we
are
unable
to
see
the.
A
A
B
Yeah,
basically,
it
was
about
that.
I
would
like
to
dedicate
if
you're,
okay
with
that,
we
do
not
have
too
many
on
front-end
table,
except
the
things
which
are
already
in
progress
to
an
issue
which
is
grouped
on
it,
which
is
unsigned
to
me
long
time,
but
recently
got
some
activity
requested
by
a
community.
B
I
believe
this
is
in
your
community
development
team,
so
but
basically,
nothing
more
to
add,
except
the
occasionally
mentioned
same
issue
twice
so
the
front
end.
Is
I'm
currently
working
finishing
that
four
issues
which
are
currently
in
depth
because
two
are
very
closely
connected.
This
is
a
clean
group,
experiment
and
ux
for
group
creation.
We
are
using
same
components
since
ux
is
similar.
B
One
is
quite
technical
and
one
is
on
the
very
finished
stage,
so
nothing
to
add
on
my
side,
except
that
refinement
seems
a
bit
empty
for
front-end
but,
as
I
mentioned
in
the
e
to
see
the
re-import
thing,
which
is
in
design
stage,
but
let's
see
how
it
happens,
because
previously
we
spoken
about
that.
This
is
a
pretty
high
priority
for
us.
A
A
This
not
owned
issue.
If
you
know
once
these
things
are
cleaned
out
that
we
planned
last
month,
we
have
not
put
a
lot
more
in
refinement,
amanda's
been
out
or
mostly
out.
You
know
for
the
last
couple
of
weeks,
so
we
haven't
really
moved
things
forward,
but
I
do
expect
things
to
land
in
refinement
as
well,
so
there
should
be
more
to
pick
from,
but
I
would
say,
let's
just
focus
on
cleaning
out
what's
here
now,
so
that
we
can
figure
out.
What's
next.
B
A
Attention,
okay,
so
I
think
that
might
be
all
that
I
have
prepared
for
this
show
so
open
the
four
for
more
comments,
questions
things
we
should
shouldn't
do,
then
it
should
be
very
quiet.
C
It's
not
much
to
say,
I
mean
you've
covered
all
the
goals
capacities
in
the
counter,
for
then
there's
a
lot
of
stuff
in
flight
that
we
need
to
get
finished
so
yeah.
I
have
nothing
to
add.