►
From YouTube: Manage:Import 14.1 planning
Description
This is the sync planning session for the 14.1 milestone for the Manage:Import group.
Planning issue shown:
https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17339
Notable epics mentioned:
Complete Epic migration - https://gitlab.com/groups/gitlab-org/-/epics/5189
A
A
Team
is
pretty
much
unchanged.
A
So
that's
good
news.
Always
there
is
some
pto
upcoming
two
that
will
actually
affect
engineering
work
done
and
one
that
doesn't
matter
that
much
so
away
for
a
week.
A
A
All
right,
that's
cool
all
right,
so
andres
is
away
for
a
week
as
well
quick
check
on
the
team
velocity.
We
have
fighting
out
somewhat
after
that,
the
jump
and
the
drop.
A
The
front
end
now
has
a
30-day
velocity,
so
that's
good
and
it's
looking
like
more
than
one
issue.
So
that's
good.
The
back-end
team
seems
to
have
also
stabilized
at
you
know
30
plus
three
month
average.
So
that's
good
as
well.
C
Well,
the
interjection
work
is
I
I
I
I'm
surprised
to
not
see
more
to
be
honest.
Well,
42
is
pretty
good
in
the
last
30
days,
because
there
was
a
lot
of
energies
and
stuff
done.
A
lot
of
videos
got
closed
there,
plus
some
of
the
security
stuff
got
close
as
well.
C
Yeah,
I
don't
know
the
directional.
The
directional
items
felt
good
yeah.
A
So
I
think
we
are
in
a
way,
so
the
reason
why
what
I
mentioned
earlier
was
the
fact
that
we
kind
of
have
the
same
direction
for
a
couple
milestones
trying
to
complete
the
epic
migration.
But
I
think
this
will
be
the
milestone.
Now
we're
set
up
with
all
the
work
that
was
done
in
djson.
A
C
Be
honest,
so
everything
in
epic's
epic
was
completed
except
yes,
you're
right,
except
for
the
user
mapping,
but
the
user
mapping.
The
way
like
it's
gonna
be
applicable
to
everything,
not
just
epics.
So
if
you
want,
you
can
move
this
elsewhere
and
close
this
epic
out
completely
but
yeah.
It
is
true
that
the
user
mapping
needs
to
be
completed,
but
it's
not
just
epics.
It's
gonna.
A
Okay,
so
is
this
going
to
be
more
than
one
issue
once
it's
refined,
or
is
this
really
just
an
issue?
C
Well,
I
would
say,
I
would
say,
probably
one
issue,
at
least
in
my
mind.
I
have
a
rough
idea
how
we
could
do
this.
Okay,.
A
So
if
that's
the
case,
then
let's
leave
it
here.
D
A
At
the
end
of
14
1,
there
are
things
that
we
break
out.
We
should
take
him
out
of
this
epic
yeah.
C
A
This
epic
make
the
announcement
that
you
know
describes
that
epics
work
minus
whatever
the
issue
seems
to
be
but
yeah
I'd
say
for
now:
let's
just
try
and
complete
this
and
then
call
this
done.
C
Yeah
also,
I
guess
it's
important
to
call
out
that
the
user
mapping
that
we're
going
to
be
doing
here
is
dependent
on
well,
the
the
we
first
fetch
the
user
members
using
the
graphql
right
and
that
exposes
the
public
email
only.
So
we
in
this
scenario,
we're
going
to
be
relying
just
on
that
that
if
you
have
your
public
email
set,
we're
going
to
use
that
to
do
the
mapping.
Otherwise
it's
going
to
be
mapped
to
the
person
who
was
importing
it.
A
You
would
think
that
that
would
be
an
acceptable
solution
in
in
a
lot
of
cases,
but
everybody
just
seems
to
bark
whenever
whenever
something
doesn't
get
mapped,
yeah
yeah,
especially
for
historical
things,.
A
For
sure,
that's
right!
So
if
that's
that
that's
one
way
to
iterate
yeah,
let's
just
you
know,
scope
down
the
issue
to
just
to
just
that
and
then
we'll
break
out
a
better
way
to
do
this,
that
we
may
roll
together
into
the
future.
Epic
of
of
users,
migration.
C
I
know
there's
a
big
discussion
around
this,
so
I
I'm
guessing
like
the
simplest
thing
that
we
can
do
right
now
is
just
map
map
by
the
public
email
and
that's
it.
And
then
we
can,
you
know,
figure
stuff
out.
Yeah.
A
So
you
know
so
I'm
personally
excited
about
it
may
have
sounded
negative.
A
I
was
trying
to
say
that
I'm
actually
excited
that
this
time
around,
I
feel
like
we'll
be
able
to
make
this
big
announcement
that
the
epics
migration
is
completed
and
I'm
curious
to
see
how
far
we're
able
to
get
into
this,
because
this
is
on
its
last
leg
too,
in
a
way
like
there's
a
one
or
two
milestones
left
in
here
in
the
entire,
like
group,
export
import,
getting
it
to
viable,
getting
it
to
what
the
the
group
export
import
used
to
do.
Getting
immigration
is
to
do
this.
A
It
seems
like
once
the
epics
are
completed,
which
is
that
one
issue
in
here
there's
not
that
many
issues
we're
pretty
close
to
being
able
to
say
that
we're
parity.
C
A
A
So
if
there
are
some
things
that
should
not
be
considered
parity,
I'm
okay
with
taking
that
out-
and
you
know
just
making
this
slimmer
if
that's
possible
at
the
same
time,
in
order
for
us
to
be
able
to
keep
the
the
the
backlog
pipeline
going,
we
do
need
to
start
spiking
the
next
big
thing,
which
is
the
user
migration.
A
So
this
has
to
do
with
you
know.
I've
created
a
spike
issue
that
I'd
like
to
potentially
pick
up
in
14
1,
and
I
would
say
that,
even
if
this
is
not
completed
so
even
if
we
don't
get
to
the
end
of
the
parody,
I
think
it's
important
to
start
spiking
this,
because
by
the
time
we
get
to
the
end
of
this.
A
If
we
then
start
spiking
and
trying
to
figure
out
the
details
of
the
of
the
users,
it
may
be
a
milestone
or
two
before
we're
able
to
actually
get
some
get
some
issues
going.
A
So
I
would
say
that
this
is
a
pretty
high
priority
to
get
into
this
spike.
This
particular
you
know
I've
sort
of
listed
the
thoughts
that
I
had
about
the
functionality
that
I
would
like
to
get
out
of
it,
and
what
questions
do
I
still
have
around
this
you're?
A
Welcome
to
you
know,
change
some
of
it
up,
maybe
add
another
question
that
needs
answering,
so
I'm
open
and
refinement
to
you
know
get
more
of
an
idea
of
what
other
things
we
should
look
into,
but
this
is
one
that
we
should
also
probably
time
box,
because
it
is
a
spike
and
just
try
to
get
as
much
of
an
answer
as
we
can
for
each
one
of
these
areas
in
a
in
a
time
box
manner.
A
So
really
it's
about
technical
approaches.
A
lot
of
it
will
be
around
security
allowably
a
lot
around
like
you
know
what
encryption?
What
kind
of
you
know
secret
handling
methods?
Can
we
use
to
get
this
to
get
the
sense
the
data
across
and
then
that
will
probably
inform
how
we
did
iterate
on
the
user
mapping
once
we
get
to
this?
A
I
mean
we'll
read
through
this
when
we
get
to
it,
but
in
general
there
are
some
ideas
about
like
how
to
scope
this
down
what
this
might
mean
for
self-managed
versus
sas
and
so
on.
So
anyway,
I
feel
like
this
is
going
to
be
an
important
part
of
us
being
ready
to
attack
the
user
migration
once
we're
done
with
group
with
groups.
A
B
It
is
well-
and
this
is
like
a
kind
of
universal
feeler-
I
mean
the
first
one,
and
I
mentioned
it-
build
up
sorry
in
the
comments
below.
So
basically,
this
one
is
pretty
low
priority,
because
it's
more
like
a
technical
side
of
the
things
which
obviously
has
not
too
much
business
value.
So
if
you
will
be
able
to
move
any
of
two
things,
I've
mentioned
to
the
stage
of
ready
for
development.
I
prefer
to
pick
them
because
they
deliver
way
more
higher
business
value
than
that
pretty
big.
Yet
technical
debt
issue.
A
I
will
agree
100
with
you.
Both
of
these
that
you
listed
here
are
more
valuable.
The
really
important
is
valuable
because
it's
something
I've
been
wanting
to
have,
and
then
we
kind
of
had
in
the
beginning,
and
then
we
locked
people
out
of
it.
So
getting
back
that
experience
is
going
to
be
really
important
and
I
would
say,
that's
probably
kind
of
right
there
at
the
top
of
what
we
should
be
working
on
and
yes,.
B
Especially
since
we
have
like
a
back
end
ready
for
that,
it's
just
a
matter
of
having
designs
suggested
there.
So.
A
And
the
other
issue
to
list
there
is
being
able
to
select
multiple
groups
for
bulk
imports,
so
having
check
boxes
and
just
select.
I
want
a
b
d
and
z
and
you
know
import
all
or
import
these.
A
I
believe
that
this
is
the
issue
where
we're
gonna
start
looking
into
creating
the
component
of
a
enterprise
table
like
with
enterprise
stable
functionality,
which
is
really
exciting.
So
while
we
may
implement
only
one
small
feature
into
it,
this
this
should
be
a
starting
point
for
us
to
be
able
to
get
a
more
useful
table
component
that
we
can
replace
a
lot
of
our
lists
with.
So
a
lot
of
our
lists
are
really
kind
of
tables,
but
then
you
typically
can't
sort
by
you
know
by
the
column.
A
You
can't
move
the
columns
around
configure
it
there's
a
lot
of
things
that
you
have
in
a
lot
of
these
high.
You
know
highly
functional
tables
that
we
don't
have,
so
it's
probably
time
for
us
to
start
looking
into
building
that
component.
A
So
I
understand
that
we
will
spend
more
time
on
this
than
we
would
if
we
were
to
just
kind
of
implement
the
checkboxes,
but
I
believe
that
the
investment
is
definitely
worth
it
and
what
we
really
need
to
do
is
just
engage
all
the
other
groups
that
have
these
needs,
because
I
know
that
there
are,
there
are
such
you
know,
needs
and
there's
a
lot
of
discussions
going.
B
A
B
A
Highlight
this
in
the
kickoff
as
well,
so
that
you
know
other
pms
will
hear
about
it
because
you
know
once
they
do
it.
They
just
kind
of
you
know
jog
their
thinking
a
little
bit
about
where
they
might
need
something
like
this
and
maybe
invite
them
collaborate.
Then.
A
So
that's
great!
That's
that's
great.
I
just
can't
believe
that
we
got
this
far
without
having
a
highly
functional
kind
of
price
level.
Functionality
table.
A
All
right
so
on
quality,
we'll
continue
where
we,
you
know,
with
the
two
to
track
to
track
approach.
Just
like
we
did
in
the
previous
milestone.
A
You
know
the
main
track
really
is
getting
the
gitlab
migration,
getting
our
test
automate
test
coverage
to
follow
the
gitlab
migrations,
so
that
we
end
up
with
a
great
set
of
automated
tests
for
that,
but
kind
of
prioritizing
the
scaled
github
over
that
a
little
bit
in
the
short
run
in
order
to
just
get
a
lot
of
quick
learning.
D
D
Yeah
because,
like
yeah
yeah,
because
it
required
refactoring
the
existing
tests,
so
it
kind
of
so.
D
To
to
also
like
test
with
the
larger
data
set,
so
that,
hopefully,
would
close
some
of
the
issues
that
were
open
about.
Like
previous
version
of
the
test
failures.
A
But
it
got
me
thinking
about
you
know:
can
we
potentially
take
a
pass
on
the
github
importer
bugs?
Let
me
see
I
lost
the
view
this
view
so
hopefully
you're
seeing
it
again.
I
was
wondering
if
we
could
once
we
have,
that
we
could
just
take
a
quick
pass
on
this
and
potentially
close
some
of
these
because
they're
no
longer
producible.
A
D
Yeah
definitely,
and
once
once
the
test
is
finished
there,
like,
unfortunately,
the
the
new
version
of
test
uncovered
some
other
types
of
failures.
A
Well,
product
failures
or
tesco.
D
Hard
to
tell
yet
I
would
most
likely
it's
just
like
the
environment,
like
stability,
timing
issues,
because,
like
a
test
became
a
little
bit
quicker,
I
would
say
so:
some
stuff
might
not
be
able
to
catch
up
so
either
need
to
handle
it
or
yeah,
but
yeah.
It's
still
in
in
progress
right.
A
Now
yeah,
but
I
mean,
if
we
do,
this
cover
could
have
important
failures,
then
that
that's
really
successful
for
the
test.
Yeah.
A
Right,
I
keep
this
here
just
in
case
that
there
are
things
that
make
sense
for
us
to
attack.
Now
I
know
we
did
some
other
factors
like
switching
to
ndjs
or
whatever
as
part
of
developing
new
features,
and
I
actually
do
prefer
to
take
on
technical
debt
as
we
revisit
particular
area
of
code,
so
not
just
out
of
blue,
but
maybe
you
know,
as
we
add
new
feature
to
an
area
if
that
area
has
technical
debt
where
we
need
to
go
in
and
do
some
work
I'd
like
for
you
to
consider.
A
You
know
taking
some
extra
time
during
the
development
of
that
feature,
to
also
pay
back
some
of
that.
That's
probably
my
preferred
way,
but
if
we
need
to
pick
up
an
issue
that
is
unrelated
to
anything
else,
we're
working
on
because
it's
important
and
it
needs
to
happen
now
prior
to
I
don't
know
something
else
that
happens
next
and
it's
important
to
get
it
done.
A
Prior
to
that,
then,
that's
fine,
too
I'll,
be
okay
with
picking
up
whatever
top
issue
is
in
here
that
one
there
are
no
security
issues
that
I've
found
that
bubble
up
to
the
top,
but
you
know
I
know:
we've
been
dealing
with
a
lot
of
bugs
that
are
related
to
migrations
of
large
customers,
and
I
suspect
that
14
1
is
gonna,
have
some
of
that
flavor
as
well,
hopefully
not
as
much,
but
I
know
that
there's
ongoing
issues
right
now
that
we're
going
to
roll
into
14
1..
A
So
that's
the
milestones
on
the
roadmap
side
of
things.
There
could
be
potential
changes
that
I'll
be
able
to
probably
discuss
more
by
the
time
we
meet
next,
even
in
our
weekly,
which
is
not
going
to
be
this
monday.
But
the
money
after
that
there
is
an
mr
to
sort
of
think
through
the
future
of
the
templates
category
as
part
of
imports.
Just
wanna,
let
you
know
that's
being
discussed
so
that
you're
not
like
completely
shocked.
A
If
that
goes
away,
or
something
happens
to
that,
because
I
know
that
it's
dear
to
everybody's
heart
here-
we're
all
think
about
temple
salon.
A
A
It
is
in
line
with
that,
and
I
you
know,
I'm
gonna
have
to
thank
or
eat
if
any
of
that
happens,
because
she's
been
really
helpful
and
driving
a
lot
of
that
so
we'll
see
in
a
couple
of
weeks,
but
that
may
be
some
change
in
the
overall
kind
of
direction
for
the
group.
A
Let's
see
what
else
I
think
at
this
point
we
can
take
a
look
at
the
kanban
board,
but,
given
that
we've
been
looking
at
it
weekly,
this
monthly
look
is
not
going
to
reveal
anything
new.
A
The
issues
that
are
listed
here
I
will
make
sure
on
one
more
pass.
Now
that
we've
talked
about
it,
I
will
label
whichever
ones
we
talked
about
with
14,
1
and
deliverable,
and
I
will
move
them
to
the
top
of
the
kanban
board.
So
after
this
meaning,
I
will
clean
out
the
I
will
clean
up
the
kanban
board
to
reflect
what
decisions
we've
just
made.
A
A
A
A
That's
it
yeah
all
right.
So
that's
all
folks!
Thank
you
very
much
awesome
seeing
your
faces
and
I'm
I'm
really
thankful
to
be
on
this
team.