►
From YouTube: Manage:Import 14.3 planning
Description
This is the sync planning session for the 14.3 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17369
Notable issue mentioned:
Migrate Empty Projects - https://gitlab.com/gitlab-org/gitlab/-/issues/267948
A
A
A
A
A
So,,
when
we
later
review
the
kanban
board
I'll
kind
of
show
around
where
those
issues
are.
A
A
A
Customer
escalation
that
you
know
the
back-end
team
spent
a
lot
of
time
on.
A
A
We
normally
would,
and
you
can
tell
that
you
know
if
you
look
at
the
back
end
average.
A
A
B
I
mean
from
my
side
yeah
I
spend
a
lot
of
time.
You
know
on
the
github
importer.
A
A
People
being
pinned
by
different
people
yeah,
so
you
know
that's
the
one
thing
that
we
we
should
be.
A
A
A
Be
mainly
focused
on
directional
items
on
delivering
the
long-term
solutions
for.
A
A
To
share
with
you
the
the
roadmap
view
that
we
currently
are
gonna.
You
know
that
we're
gonna.
A
That
will
you
know
kind
of
solve
that
will
will
use
to
deliver
these
features.
A
And
I
have
laid
them
out
in
a
way
that
they
were
laid
out
in
the
proposed
roadmap
to
sort
of.
A
So
if
we,
for
whatever
reason,
spend
another
month
doing
something
other
than
what's
on
the.
A
A
A
A
We'll
keep
it
that
way,
so
I'm
just
wanna
bring
up
that.
There's
really
two
ways
to
manage
the
road.
A
My
point
is
to
keep
extending
until
we
fully
do
the
feature.
The
other
one
is
for
me
to
sort
of.
A
A
A
Do
what
we
can
each
one
of
these,
and
if
the
amount
of
work
is
bigger
than
what's
on
this.
A
A
Sort
of
fall
apart,
so
this
will
be
a
good
test
of
our
road
mapping
feature
and
I'll.
Try
to
also.
A
This
use
it
as
much
as
it's
useful
to
you,
but
I
just
wanna
kind
of
bring
up
the
fact
that.
A
To
see
sort
of
where
we
are
so,
where
are
we
right
now?
The
red
line
tells
us
that
we
are
actually.
A
Imported
by
reliability
improvements,
I
feel,
like
we've
done
a
lot.
A
few
are
getting
wrapped
up.
A
A
A
A
A
A
That
in
more
detail,
when
we
get
back
to
the
objectives
of
this
milestone,
but
I
expect
this
to.
A
A
A
Replacement
I've
split
them
into
two
just
to
sort
of
have
a
more
manageable.
A
A
little
bit
so
that
we
have
more
control
over
the
details,
but
in
theory
by
you
know,
14-6.
A
Done
with
the
spike,
but
we'll
as
we
wind
down
the
project,
migration,
we'll
then
take
a
look
at
the.
A
Just
kind
of
start
getting
things
done,
you
know
as
far
as
discovery
goes
as
well.
A
A
And
I
think
all
along
we'll
be
paying
attention
to
the
ux.
There
will
be.
A
A
The
gitlab
migration,
hopefully
and
switch
over
to
the
github
importer
for
the
for
the
next.
A
Five
months
or
so
to
to
get
that
completed,
so
that
is
the
roadmap.
From
this
viewpoint,.
A
So
thoughts
about
this,
does
it
sound
like
crazy,
unrealistic?
Maybe.
B
B
A
project
without
which
I
mean
there's,
there's
no
merge
requests,
there's
no.
B
Blocks
the
import
of
everything
else,
so
I
feel
like
this
should
be
done
prior
to
that.
B
Prior
to
the
projects,
you
know
like
issues,
merge,
requests,
etc
and
just
just
another.
B
Like
it,
it
says
they're,
zero
percent.
Does
that
mean
like
none
of
the
issues
that
are
in
there.
A
So
I'm
guessing
these
three
that
have
been
completed
did
not
have
weights
on
them.
B
Okay,
well,
I
don't
know
if
all
the
other
issues
in
this
epic
should
be
done
or
not
right,
we'll.
A
Github
importer
in
january
right,
so
this
is
sort
of
to
get
a
stable
at
this
point
as.
B
B
Like
well,
the
big
change
that
I'm
working
on
is
regarding
the
customer
migration.
Then
there's.
B
A
number
of
things
that
casio
is
doing
to
show
like
some
bug,
fixes
and
grafana.
I'm
just.
B
A
Estimation
completed
but
just
assign
some,
you
know
temporary
weights
to
maybe
give
us
an
idea
of.
A
Where
we
are,
but
really
I
do
want
to
manage
this
by
time
boxing,
because
you
can
always
improve.
A
A
This
is
all
we
wanna
do
and
that
kind
of
is
gonna
force
us
to
really
draw
a
line
at
some
point.
A
A
A
It's
spilling
to
143
we'll
take
those,
but
I
don't
think
we
should
take
any.
We
should
add
any.
B
Just
one
more
thing,
I
guess
in
terms
of
unexpected
engineering
allocation,
should.
B
A
Is
a
call
out
that
we've
been
doing
something
else,
so
those
would
be
the
flags
as
opposed
to.
A
A
A
By
two
months,
which
d
we
can
then
manage
by
maybe
adding
more
people
to
the
team
to
sort.
A
Of
catch
up
to
that,
but
I
feel
like
this
is
a
good
radiator
of
what's
happening.
Directionally,
okay,.
A
Going
to
attack
them,
but
for
now
just
kind
of
listing
the
things
that
we
are
going
to
be
working.
A
A
They're
not
completed,
then
you
know-
and
I
know
that
ilya
you
mentioned-
that
both
of
these
are.
A
A
A
So
that
may
be
a
good
one
to
mark
for
14.3
and
actually
get
delivered
in
143,
because
epics.
A
So
it'd
be
a
good
one
that
I
suggest
we
take
on
the
other
thing,
that's
still
in
progress.
A
Is
the
github
importer
testing
with
large
data
samples
so
that
one
is
in
verification
in.
A
A
So
just
want
to
list
it.
There
is
something
that
maybe
a
spill
over
andres
any
other
thoughts.
C
C
Testing
perspective
there's
one
last
thing
that
is
missing
for
our
automated
solution
is
that.
C
We
are
currently
limited
by
our,
like
runners
set
up
on
like
gitlab.com,
because
the
longest.
C
C
C
A
Discuss
that,
because
I
feel
like
that's
something
that
we
should
escalate
back
up
and
also,
if.
A
This
is
something
that
just
happens
with
our
you
know:
customers
using
on
gitlab.com.
You
know.
A
C
A
A
Yeah
yeah,
I
had
a
chat
with
the
engineering
productivity
team.
I
asked
on
the
slack
I
think.
A
B
Can
you
just
an
idea,
random
food
for
thought?
Maybe
what
if,
after
the
timeout,
you
know
the.
B
To
as
a
way
of
resetting
the
timeout,
I
don't
know
just
something
to
think
about,
it
would
be
a.
C
C
C
C
A
Okay,
so
now
we're
going
to
talk
about
the
engineering
allocation.
A
Like
how
that's
represented
here
and
I
have
combined
the
engineering
allocation
items,.
A
A
Yet
I've
also
pinged
the
engineers
on
the
planning
issue
for
security
items
to
sort
of.
A
A
A
That
I've
put
a
little
cherry
on,
so
those
are
the
ones
that
you
know
like
it's.
Okay
to
just
go.
A
A
To
to
to
security,
the
one
thing
that's
maybe
slightly
out
of
order
when
you
look
at
this.
A
Like
to
prioritize
this,
so
as
we
look
at
you
know
this
particular
backlog,
the
engineering.
A
A
A
A
A
Have
those
issues
kind
of
move
into
refinement?
You
know
by
the
time
we're
ready
to
pick
them
up.
A
In
14
30.,
so
this
is
really
the
only
directional
item.
That's
that's
being
planned
for
14.3.
A
And
that's
because,
even
though
the
engineering
allocation
is
50,
what
that
means
for
14
3
with.
A
Casio
being
out
for
two
weeks
is
that
you
know
we
still
need
to
allocate
one
full
engineer.
A
Couple
of
issues,
maybe
only
one
of
those
comes
across
and
if
multiple
come
across,
that's
fine
too.
A
But
that's
the
bandwidth
we
have
to
we.
We
have
that
we
can
use
against
the
directional
items.
A
To
be
spent
against
the
in
for
them
security
issues,
which
is
why
you
know
these
are
listed.
A
And
which
is
why
the
kanban
board
actually
lists
you
know,
has
all
of
that
lined
up
so.
A
Than
from
directional
for
this
particular
milestone,.
A
So
there's
two
ways
to
handle
this
one
would
be
for
each
one
of
the
back
end
engineers
to.
A
Better,
whatever
is
you
know,
I'm
thinking
less
overhead
or
less
context,
switching
or
whatever.
A
B
C
I
can
pull
it
up
yeah.
Well,
I'm
working
on
infra
dev
issue
already.
I
don't
know
if
it
makes
sense.
B
B
Order
to
address
that
I
mean
maybe
it's
worse,
giving
it
a
time
box
investigation
once
again.
B
But
yeah
anyway,
like
we'll
figure
it
out,
I
don't
think
we
should
well.
We
should
do
that.
B
Now
but
it's
a
good
point
that
you
know
as
we're
refining
this
if
there
isn't
a
clear
proposed.
A
Solution,
if
there's
any
clear
technical
approach,
then
we
just
need
to
time
box
this.
A
A
If
somebody
was
just
like
researching
this
for
a
month
and
not
not
got
anything
else
done
so.
A
The
interesting
one
is
is
one
that
I
put
sort
of.
It
is
backhand,
but.
A
It's
also
the
front-end
engineer,
who's
volunteered
to
pick
it
up.
A
A
A
A
A
A
All
the
things
lined
up
so
there's
plenty
of
work
there.
We
can
chat
about
that.
A
Now,
finally,
there
is
a
bug.
There
is
a
bug,
that's
also
in
refinement.
A
That
we'll
need
to
pick
up
it's
kind
of
mixed
in
with
the
security
and
other
things,
but.
A
What
we
have
so
I
know
that,
oh
you
have
assigned
it
to
42..
Well,
let's
find
them
cool.
A
Okay,
cool
so
yeah,
that's
good
and
then
then
you
can
switch
back
to
wrapping.
A
What
are
the
next
big
things
for
frontline
that
we
can
line
up
for
you
to
work
on.
D
Yeah
sorry
for
late
delivery
of
reimport,
it
was
pretty
unexpected
for
me
too,
because.
A
So
finally,
how
do
we
feel
about
like
what's
listed
here?
So
let's
say
you
know
we
have
this.
A
One
that's
kind
of
in
progress,
but
it's
being
led
by
someone
else
and
I
feel
like
it
may
require.
A
And
calling
this
done
so
that's
kind
of
this
is
a
long
story
and
it
could
be
hairy
to.
A
Then
there's
this
thing:
that's
a
time
box
and
then
there's
at
least
two
security
issues.
A
Srf
and
two
different
importers,
and
then
there
is
this
directional
thing
that
needs
to
happen
at.
A
A
Or
maybe,
since
this
is
just
gonna,
be
like
things
in
order,
how
about
this
migration.
A
Elephants
in
the
room-
no,
I
just
want
to
say
thanks
for
putting
concrete
items
on
the.
B
B
As
proposed
objectives,
which
felt
a
bit
overwhelming
every
time
you
look
at
it.
B
And
you
know
kind
of
having
a
sense
of
underachieving
every
time.
So
no
it's,
I
think.
B
It's
great
to
to
have
like
a
a
list
of
specific
things
that
we
are
trying
to
implement
as
part.