►
From YouTube: Manage:Import 14.7 planning
Description
This is the sync planning session for the 14.7 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17429
A
Also,
I
don't
know
if
anyone's
talked
to
any
like
internal
engineers,
but
we
should.
A
A
Optimize
and
import,
so
there
you
will
get
we'll
get
someone
who's
gonna
spend
those
two.
A
Week
and
a
half
or
is
it
two
weeks
I
think
it's
pretty
much
two
weeks
off
so
I'm
taking
like.
A
A
So
this
that's
going
to
be
really
the
the
important.
A
So
and
andrejs
is
still
doing
the.
A
Point
out
at
other
than
there's
definitely
a
bump
there
from
when
we
had
the
extra
people
on.
A
The
team
and
seems
like
some
of
the
like
the
front
end
issues
have
dragged
until
yesterday.
A
Really
I
want
to
talk
about
the
objectives
and
the
objectives
at
this
point.
A
There
so
committing
to
anything
of
a
size
would
not
make
any
sense.
A
A
A
The
nbc
for
project
migration,
I
have
renamed
that
epic
project
migration
mvc
to
sort
of.
A
New
experience
for
migrating
groups
and
projects
so
we'll
we'll
continue
to
make
progress
there.
A
Immediately
get
picked
up,
but
there
is
one
that
is
a
p2
that
has
a
dependency
on
italy.
A
And
whenever
goodly
takes
care
of
their
security
issue,
we'll
have
a
follow-up.
So
few.
A
A
The
extra
help
we're
gonna
try
to
wrap
up
the
most
important
ones
and.
A
And
then
for
front
end,
I
saw
earlier
that
you've
updated
with
the
item
that
you
were
able
to.
A
Close
since
yesterday
and
added
the
items
that
you
feel
like
you
could
be
working
on.
A
Sorry,
just
my
two
cents,
one
was
was
suggested
by
you.
It
is
actually
finishing.
B
B
B
With
my
new
knowledge
about
the
importers,
I
feel,
like
I'm
capable
doing
both
front
end
and
back.
A
B
Dropping
and
so
no,
I
I
I
feel,
like
your
ux,
your
instincts
are
on
on
the
spot,
though,.
A
So
so
not
that
I
want
to
keep
you
there
during
ux
work
only,
but
I
I
didn't
feel
like.
A
You
know
we
really
needed
somebody
to
reign
in
or
anything
like
that.
I
think
I
think
he
did
great.
A
A
A
Issues
that
we
should
pay
close
attention
next
milestone
or
so,
and
I
think
these
are.
A
A
A
It
should
be
pretty
much
clean
or
you
know
good
enough
for
us
to
to
to
do
the
planning.
I.
A
No
priority,
but
we
won't
get
there
anyway,
so,
given
that
we're
probably
not
gonna
get.
A
It
does
seem
like
we
have
still
a
lot
of
stuff
in
progress.
If
you
take
a
look.
A
I
think
yesterday
that
I
believe
that
the
in
review
was
11
out
of
10,
so
it
was.
A
And
19
refinement
the
priorities
are
correct,
so
I
would
say
one
thing
to
think
about
is.
A
Really,
this
needs
to
be
this.
This
needs
to
be
looked
at
kind
of
back
and
versus
front
end
to.
A
Really
see
what's
yeah,
this
was
exactly
which
I
wanted
to
mention
that
this
milestone.
I
will
pay.
A
Have
assigned
yourself
to
the
refinement
on
these?
So
if
you
do
need
like
once,
you
identify
which.
A
A
Features
so
that
we
can
line
it
up
for
backhand
for
the
next
milestone
yeah.
I
will
probably
start.
B
By
mentioning
calcium
george
on
them,
explaining
what
is
probably
the
question,
because
they,
I
can't.
B
They
will
have
a
better
option
so
to
understand
what
we
will
do
to
fulfill
this
issue
so
yeah.
I.
B
Will
do
that
somewhere
soon
because
of
at
least
two
of
these
ones,
which
are
sitting
in
refinement.
A
A
B
B
B
And
back
inside
in
technical
terms,
that's
a
that's
a
interesting
point.
Then
we
can
probably
keep.
A
Like
the
back
end
of
the
front,
end
tags
and
maybe
find
find
a
refinement
owner
on
the
backhand.
A
To
just
make
sure
that
you
know,
there's
a
discussion
going
on
in
the
refinement
thread
and.
B
I
will
probably
annoy
cassio
and
george
in
them
like
hey.
I
need
volunteer
for
one
specific.
C
Okay,
okay,
so
that
seems
to
be
all
good.
You
know
these
issues
that
are.
A
Ready
for
dev-
and
I
know
the
one
here
has
been
the
one-
that's
just
been
kind
of
sitting
there
and.
B
A
So
I'm
looking
at
the
back
end.
A
Combined,
it
cleaned
up
some,
but
still
a
combined
set
of
things.
A
So
I
would
kind
of
leave
it
up
to
you
to
to
make
calls,
and
you
know.
A
Feel
like
it
because
some
of
these
are
you
know
cleanups
and
follow-ups.
So
if
you
feel
like.
A
That
that
just
needs
to
be
done
anyway,
you're
welcome
to
push
that
across,
especially
if
it's.
A
Simpler
and
it's
and
something
that
could
get
done
versus
some
of
these,
that
could
be.
A
A
Ready
for
that
and
if
we
could
get
a
mix
of
p2s
and
p3s
moving
across
the
board.
A
A
Some
things
are
waiting
for
things,
I'm
unwilling
to
let
you
figure
out
what
is
the.
A
A
A
Be
really
things
that
got
escalated
or
that
would
trump
other
things.
We
still
have
this.
A
A
This
is
pretty
much
our.
You
know
things
that
we
need
to
get
done,
the
things
that
we
want
to
get.
A
Done
you'll
see
a
good
lot.
A
lot
of
the
p1's
here
in
refinement
are
going
to
be
the
mvc
for
the.
A
For
the
gitlab
migration,
so
they're
all
going
to
be
sitting
in
p2
here.
A
Welcome
to
just
start
keep
picking
up
those
and
moving
those
across
ignoring
everything.
A
A
Some
of
the
p3
errors
like
this
transient
and
so
on,
but
generally
the
p,
the
p2s
on.
A
Okay,
so
I
think
that's
pretty
much
the
what
I
had
to
say
and
what
I
had
to
show
so.
A
D
D
We
we
had
this
discussion
about
ready
for
development.
You
know
you,
you
just
said.
D
Think
it's
a
very
good
issue
to
to
pick
and
I
don't
think
it
should
be
our
priority
because.
D
A
A
D
D
Now
maybe
we
should
just
focus
on
priority
label
and
see
like
okay.
C
C
A
Yeah
and
it's
only
these
two
columns
that
really
kind
of
are
combined
as
far
as
like,
where
you.
D
D
So
that's
where
I'm
coming
from,
but
no
I
get
it
in
terms
of
priorities.
I
think
it.
A
I
think
we
could
just
say
between
these
two
columns.
You
know
pick
the
highest
priority.
D
A
A
C
A
A
A
Discussion
so
I
think
that's
all
we
have
unless
there's
anything
anyone
else
wants
to
bring
up.