►
From YouTube: Manage:Import 13.8 planning
Description
This is the sync planning session for the 13.8 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17299
A
A
C
E
A
B
D
D
B
B
A
All
right,
so
that's
that's
good!
That's
about
half
capacity
overall,
which
does
not
mean
that
we
can
do
half
as
many
things
that
are
directional,
because
there
is
some
fixed
cost
that
we
take
into
account.
So
I
probably
just
could
talk
lightly
about
what
we're
going
to
do
and
then
come
back
in
january
and
can
really
hit
some
of
these
things
harder.
A
Just
for
sake
of
talking
about
things.
Velocity
seems
to
well.
This
is
13
7,
which
is
in
progress.
I
really
can't
tell.
All
we
can
see
is
really
through
13
6
and
I
think
that's
the
time
that
we
actually
had
josie
as
well.
So
I
don't
think
we
see
that
impact
on
the
chart
yet
which
is
kind
of
reflected
in
these
somewhat.
C
That,
like
the
delay
at
velocity
from
front
end,
I
mean
in
terms
of
merge
requests
which
were
not
delivered
previous
milestone,
also
kind
of
effective
this
month,
one
and
will
affect
even
more
since
there
are
like
five
or
six
merger
quests
waiting
for
like
final
approval,
since
they
interdepend
one
on
each
other.
So,
yes,
I
believe
these
numbers
are
highly
unrepresentable
right
now,.
A
A
As
far
as
before
I
get
into
the
proposed
objectives,
I
do
want
to
review
kind
of
the
road
map
and
where
we
are
I'll
do
that
try
to
do
that
sometimes
more
sometimes
less
during
these
meetings.
But
I
do
want
to
get
into
a
little
bit
more
of
that
discussion
this
time
around,
because
I've
updated
some
of
the
directional
issues
and
up
iterated
on
some
of
the
things
we're
going
to
work
on.
A
So
I
just
want
to
kind
of
show
that
to
everybody
and
make
sure
that
we
are
still
on
the
same
page
on
what's
happening
next
and
why
so?
An
update
that
I
made
to
the
internationalization
direction
is
that
I've
stated
that
there
are
no
improvements
currently
being
prioritized
by
the
group
so
kind
of
as
a
result
of
losing
josie
and
the
velocity
she
was
bringing
to
the
group.
A
It's
just
that
this
thing
will
not
be
spending
a
lot
of
time
on
this
category,
similar
for
the
templates.
I've
updated
with
this
sentence
and
said
that
this
group
is
only
working
on.
You
know
critical,
bugs
and
security
fixes
for
the
templating
functionality,
not
committing
to
anything
other
than
that.
A
A
So
the
gitlab
importer
as
a
overall
feature,
is
what
I
call
the
sum
of
the
of
the
project
export
import,
which
I've
labeled
here
single
project
importer
and
the
group
export
import,
which
I've
labeled
single
group
importer
just
to
distinguish
them
from
this
feature
here
that
we're
working
on
which
should
be
able
to
import.
You
know
for
now
one
group
with
multiple
projects,
but
in
the
future
also,
maybe
you
should
be
able
to
multi-select
different
groups
that
you
want
to
move
across
at
the
same
time
and
and
kick
that
off.
D
A
I'm
still
like,
I
feel,
like
I'm
iterating,
on
this,
a
little
bit
so
first
making
sure
that
the
word
migration
sticks
and
then,
and
then
we'll
call
it.
You
know
gitlab
migration
or
project
migration
or
something
else
I
agree
with
you,
I'm
not
happy
with
the
words
but
yeah.
We
probably
need
to
sort
of
iterate
and
teach
people
what
I.
D
A
D
A
However,
we're
not
going
to
enhance
this
feature
anymore
instead
to
achieve
a
kind
of
a
complete
maturity
level
for
gitlab
migrations,
we're
going
to
focus
on
on
this
new
feature
here
and
kind
of
describing
that
feature
as
a
user-friendly
tool
to
that
lets.
You
kind
of
migrate,
a
number
of
groups
or
projects
with
a
single
click.
So
that's
where
we
are.
I
have
linked
this
over
to
the
epic
that
is
the
top
level
epic
for
the
gitlab
group
migration.
A
A
You
know
all
the
other
importers,
but
project
export
import
is
a
feature
at
this
level.
Group
export
import
is
a
feature
at
this
level,
and
now
we
have
a
gitlab
group
migration
as
a
feature
at
this
level,
so
just
trying
also
to
make
a
distinction
there
in
the
epic
structure,
so
I've
put
sort
of
where
we
are
and
where
we
want
to
go
and
what
the
plan
is
to
get
there
into
this
top
level
epic.
A
A
Does
the
group
export
import
feature
could
be
deprecated
or
we'll
see
what
happens
to
it,
but
it
definitely
is
you
know
it
should
not
be
a
priority
anymore,
and
then
this
becomes
a
priority.
This
is
where
we
kind
of
gain
the
momentum.
So
when
we
get
to
this
point,
I
feel
like
we're
gonna,
you
know
cross
that
threshold
to
where
this
is
the
momentum,
and
we
can
tell
everybody
else.
Oh
you
have
problems
with
your
project,
export
importer.
A
Why
don't
you
just
wait
two
months
instead
of
me
fixing
it
there
I'll
give
you
this
new
thing.
So
you
know,
hopefully,
that
that
causes
that,
and
so
some
of
the
steps
to
get
there
is
something
that
we
don't
have,
which
is
user
migration
and
then
the
project
migration.
I
sort
of
split
that
you
know
somewhat
arbitrarily,
but
maybe
not
at
least
into
two
large
epics
to
just
manage
it
easier.
A
So
we'll
see
what
those
are.
But
you
know
there
are
some
settings
and
some
things
so
you
know,
might
be
some
instant
set.
Things
like
who
knows
we'll
see
what
what's
including
here,
what
the
users
will
need
in
order
to
make
this
kind
of
really
lovable.
I
feel
like
by
the
time
we
get
here
that
you
know
tools
like
congregate,
that
professional
services
uses.
A
Will
you
know
their
usage
will
be
reduced
by
a
lot,
because
many
people
will
be
able
to
do
the
things
that
you
do.
There
will
be
still
specific
cases
that
professional
services
will.
You
know
just
have
to
engage
to
do
that,
but
this
will
do
a
lot
of
the
work
that
congregate
can
do
right
now.
Those
non-functional
requirements
that
I
had
well,
I
turns
out
some-
are
somewhat
functional.
A
I've
put
them
under
here
as
other
requirements,
because
they're
things
that
we
want
to
deliver
that
are
not
necessarily
related
to
these,
which
are
mainly
functional,
but
you
know
things
to
keep
in
mind
and
we'll
make
sure
to
weave
these
into
each
one
of
the
maturity
levels
into
each
one
of
the
steps,
and
you
know
so.
Finally,
these
epics
here
these
kind
of
large
delivery
epics,
are,
you
know,
put
here
in
order
as
well.
A
So
if
you
just
look
down
here,
this
is
the
nbc
we're
working
right
now
past,
that
is
our
viable
state,
which
is
the
parity
with
group
export
import,
we'll
work
on
users,
projects,
repos
world
class
class
experience.
I
have
two
other
buckets
here
that
I'm
putting
things
in
one
is
the
user
user
experience
improvements
or
ux
improvements
that
may
not
tie
into
these
functional
epics,
but
some
of
those
will
be
part
of
those
epics.
A
So
you
know,
as
we
get
to
parity
we're
also
going
to
have
to
solve
these
user
experience
issues
some
basic
ones
and
then,
as
we,
you
know,
progress
more
we'll
be
layering
in
some
more
of
these
similar
with
technical
improvements.
These
are
the
the
deck
that
or
the
the
follow-ups
that
we
had
after
the
nbc
they're
all
in
here,
so
some
will
actually
be
included
in
the
mvc.
A
A
Yeah
yeah,
these
are
buckets
that
are
not
so.
This
is
kind
of
the
order
of
things
to
get
you
know
to
get
from
here
to
there.
These
are
just
buckets
that
you
know
like
some
of
these
things
will
get
solved
and
you
know
137.
Some
of
these
things
will
get
solved
after
that.
So
we'll
be
pulling
things
from
here
and
from
the
technical
improvements
into
you
know
each
one
of
the
milestones,
because
these
will
also
run
multi-milestone
and
we
will.
We
may
break
this
down
into
further
smaller
deliverables
as
well.
A
So
while
this
sort
of
paints
a
picture
of
how
it
gets
delivered
and
a
larger
higher
level
picture,
yeah,
these
things
will
get
added
from
ux
improvements
into
each
one
of
these.
It's
just
that.
The
way
they
arrive
here
is
through
ux
discovery
or
through
us
deciding
not
to
do
something
right
now,
technically
or
ux
wise,
because
we
need
to
deliver
this
one
thing,
but
then
we'll
come
back
later
to
it.
This
is
the
come
back
later
bucket
and
it
doesn't
happen
at
the
end
of
all
of
this.
It
happens
throughout.
F
A
Well,
thank
you
for
listening,
and
you
know
please
comment
on
this.
Let
me
know
which
thing
and
if
there's
things
you
can
do
where
well,
where
I
would
really
request
your
feedback
is
when
we
get
to.
You
know
the
depth
of
some
of
these
just
making
sure
that
we're
not
forgetting
things
and
that
I'm
not
making
assumptions
that
are
incorrect.
So
for.
A
Here
I
have
sort
of
broken
this
into.
You
know
six
issues
and
I'm
sure
that
those
issues
will
get
broken
down
further.
There
will
be
more
than
six
in
the
end,
but
this
is
sort
of
at
the
level
that
I'm
thinking
at
so
these
are
kind
of
feature
level
thinking
by
the
time
we
get
to
the
issues
that
you
execute
in
the
milestones
a
bit
more
than
that.
A
So
you
know
just
look
at
some
of
the
details
and
I
think
this
is
the
most
important
one
to
look
at,
because
this
is
next
up
as
far
as
the
epics
go
and
we'll
probably
spend
months
on
this,
so
making
sure
that
we
account
for
everything
and
there's
no
assumption
here-
that
I've
made
that
that
would
make
no
sense
if
you
could
help
me
catch
that
and
make
sure
this
all
makes
sense.
That'd
be
great.
D
A
So
the
objectives
for
this
milestone,
given
the
given
the
capacity
and
you
know
just
general
holidays
and
generally
what's
been
going
on
with
supporting
and
things
in
progress.
I
did
not
expect
us
to
pick
up
anything
large
or
deliver
anything
big.
That
said,
we
I
have.
I
have
lined
up
things
for
us
to
work
sort
of
in
order,
and
you
know,
as
far
as
we
will
just
get
as
far
as
we
get
into
the
into
the
ready
for
development
column,
but
the
focus
will
continue
to
be
the
git
lab
migration.
A
A
What's
missing
from
there
is
some
of
the
relational
fields,
so
we
really
need
to
figure
out
how
we're
going
to
deliver
the
rest
of
the
epic.
So
when
the
epics
migrate
over
the
labels
are
assigned
correctly,
the
emojis
are
there
the
you
know,
the
parent
epics
are
linked
up,
so
the
whole
tree
is
linked
up
and
it's
not
just
a
flat
list
of
epics
on
the
other
side.
So
this
is
where
we're
gonna,
you
know,
spend
some
time
and
I
think
in
for
13.8
what
I
think
we're
gonna
deliver.
A
There
is,
you
know
a
good
refinement
of
this
issue
and
a
good
breakdown
into
what
the
sub
issues
are
and
sort
of
be
ready
for
january
to
really
attack
this.
I
think
that's
probably
realistic,
so
we'll
see
how
far
we
get
into
this.
So
this
is
the
one
that
we're
gonna
start
refining
so
that
we
can
in
january,
really
make
progress
against
it.
I
do
want
us
and
expect
us
to
circle
back
to
some
of
the
technical
and
ux
leftovers
from
the
mvc.
A
So
that's
something
that
we
talked
about
there
is
there.
Is
that
epic,
where
we
put
all
the
technical
improvements
and
I'm
going
to
need
the
backend
engineers
help
to
figure
out
which
things
we
need
to
do
now
and
which
things
we
can
do
later?
I
don't
want
to
spend
all
the
time
just
there,
because
we
could
be
stuck
for
for
a
couple
milestones,
so
we
need
to
kind
of
balance
delivery
of
new
things
with
paying
back
some
of
this,
but
things
that
are
important.
That
need
to
happen.
A
I
think
now
is
the
time
to
pick
up
a
few
of
those
and
whatever
whatever
is
critical
and
deliver
those
as
soon
as
possible.
I
do
have
the
two
ux
leftovers.
One
is
just
a
simple
warning
message,
because
right
now
this
is
work
in
progress
and
without
this
message,
users
would
assume
that
this
is
sort
of
just
as
baked
as
this
other
approach.
So
the
import
from
file
and
the
group
migration,
you
know,
are
kind
of
on
the
same
level
and
they're
not.
This
is
very
basic.
A
A
Let
us
know
what
you
want
to
see
next,
but
you
know
don't
expect
this
to
be
a
full
group
migration
at
this
point,
so
I
think
that
message
is
important
early
I
like
to
get
that
in
right
after
the
nbc,
so
that
we
don't
get
as
many
people
giving
us
feedback.
That's,
oh
yeah!
It
looks
good,
but
just
doesn't
do
anything
well,
we
need
that.
A
A
Are
these
the
only
five
groups
that
I
can
migrate?
Is
this
just
the
things
I
can
see?
Is
there
another
page
like
what
you
know
tell
me
a
little
bit
more
about
what
this
is,
so
we
would
like
to
show
a
message
such
as
this
one
here
that
sort
of
tells
you
a
little
bit
more
about
what
you're
seeing
and
why
you're
seeing
that-
and
it's
just
you
know
again
helping
the
user
and
the
user
experience.
A
A
There
is
a
circle
back
to
instrumentation
as
well
with
this
issue
here,
which
is
making
sure
that
we
have
a
good
gmail,
which
is
group
monthly,
active
users
count.
This
is
what
the
company
uses
to
sort
of
figure
out.
How
many
users
use
any
particular
feature,
and
we
can't
need
to
get
in
line
with
everybody
else
or
align
with
everybody
else,
and
then
show
this
number
on
the
dashboard,
and
I
know
we
have
a
quick
solution
that
we
might
be
able
to
get
to
to
sort
of
be
there
until
we
get
there.
A
Finally,
there
are,
you
know,
random
bugs
and
a
security
issue
or
two
in
the
backlog
as
well.
If
we
get
far
enough
in
the
backlog,
we
may
pick
those
up,
but
I
haven't
listed
them
because
I
don't
know
if
we're
gonna
get
there
or
not.
It
may
be
that
we
do
and
that's
fine.
So
as
you
work
through
it
the
way
to
really
work.
This
is
to
look
at
the
ready
for
dev
and
just
work
against.
What's
in
ready
for
that,
so
that's
kind
of
where
we
are.
A
A
A
A
So
does
it
feel
like
we
could
so
maybe
just
kind
of
looking
overall
at
the
objectives
and
keeping
in
mind
that
this
is
mostly
refinement
and
probably
no
delivery
in
13
7.?
Does
it
feel,
like
these
issues
here
is
fair
to
say,
would
be
delivered?
Can
I
talk
about
this
in
my
kickoff
for
thirteen
eight.
A
D
D
A
Okay
cool,
so
I
mean
the
ready
for
development
has
eight
issues
in
it.
I
am
okay
if
we
can
get
these,
so
these
are
the
four
that
we
talked
about.
You
know
this
one
probably
staying
in
refinement
and
creating
more
issues
out
of
that,
if
we
were
able
to
spin
off
some
first
step,
that
might
be
something
that
could
be
then
picked
up
too,
but
you
know
these
this.
A
A
Finally,
you
know
once
once
we're
once
we
have
sort
of
worked
on
these
four,
the
ready
for
development
is
still
valid,
like
it
would
be
good
to
keep
going
down
this
this
list
here.
So
there
is,
you
know
there
are
fronted
issues
here
as
well
as
backend
issues
here.
So
this
is
sort
of
you
know
we
kind
of
think
we're
going
to
deliver
these
four
issues,
but
then
it
would
be
good
to
clean
up
as
much
as
the
ready
for
dev
as
possible
after
that.