►
From YouTube: GitLab 13.11 Kickoff - Manage
Description
Groups included:
- Manage:Import
- Manage:Optimize
A
A
So
we
were
working
on
this
epic
to
migrate
epics
as
part
of
the
group
migration,
and
we
have
completed
several
of
the
large
chunks
since
last
time,
since
1310,
we
were
able
to
add
epic
events
and
also
do
a
lot
of
refactoring
that
will
help
us
migrate,
the
more
complex
objects
and
the
more
nested
objects.
So
we
can
have
to
pause
on
delivering
some
of
the
functionality
in
order
to
refactor
and
be
technically
ready
to
now
complete
this
epic.
A
A
A
So
once
the
epics
are
being
migrated,
we
have
several
several
issues
that
we
need
to
get
through
in
order
to
complete
this,
so
this
will
pretty
much
be
the
flavor
of
what
group
import
is
going
to
work
on
for
the
next
several
milestones,
so
that's
pretty
much
the
large
chunks,
of
course.
In
addition
to
this,
we
do
get
a
lot
of
support.
Things
take
care
of
some
bugs
and
security
issues
as
needed,
but
this
is
the
feature
work
we'll
be
working
on
hope.
This
makes
sense.
A
B
Thanks
harris,
I
did
have
one
question
that
I
didn't
get
a
chance
to
write
in
the
doc,
but
first
of
all,
it's
really
nice
to
see
some
of
those
red
crosses.
Turning
into
check
green
check
marks-
and
I
was
curious
with
the
migrating
comments
on
epics
and
their
emojis
is
that
is
that
for
migrating
from
a
self-managed
gitlab
instance
to
dot-com
or
to
some
of
the
other
systems
that
we
are
importing
from
have
emojis
on
comments
similar
to
gitlab.
Does.
A
Epic
comment
emojis
and
it
gets
really-
you
know
it
gets.
It
gets
to
to
be
sometimes
four
or
five
different
nested
levels
of
things
that
we
have
to
migrate,
and
that
means
serialize
it
on
one
end
send
across
the
wire
then
deserialize
it
and
recreate
that
group
on
the
other
side,
and
then
there's
really
no
other
way
to
do
that.
Other
than
just
kind
of
this
tedious
way
of
just
making
sure
every
little
thing
makes
the
cross
and
every
small
step
it
does
become
an
issue.
A
We
will
migrate
issues,
projects,
repos
milestones
and
some
of
the
other,
some
of
the
other
objects
from
github,
big
bucket
and
others,
but
none
of
them
actually,
we
use
none
of
them
will
give
us
epics.
So
most
of
them
really
don't
have
epic
or
have
their
rudimentary
support
through
those.
So
epics
are
really
something
that
you
know.
We
have
that's
better
than
some
of
the
other
places
and-
and
this
is
just
really
related
to
gitlab-
to
get
back.
A
B
B
B
We're
also
picking
up
some
back
end
work
to
add
a
an
average
time
in
stage
column
here
so
right
now,
this
time
column
is
based
on
the
median
and
a
lot
of
other
areas
within
value
stream
actually
use
the
average
time
that
things
are
in
a
stage.
So
we're
going
to
be
adding
the
average
time
as
well.
Here,
that'll
be
a
few
more
releases
off
for
the
front
end,
probably
but
we're
doing
the
back
end
work
and
then
another
thing
coming
up
in
1311
is
alongside
the
stage
in
the
value
stream.
B
B
B
So
then
the
main
highlights
for
value
stream
analytics
and
then
for
the
devops
adoption
table
we're
going
to
continue
working
on
adding
the
devops
adoption
table
to
the
group
level.
So
right
now,
it's
still
only
available
as
an
instance
level
feature
on
self-managed
instances
and
adding
it
to
the
group
level
will
make
it
a
lot
more
accessible
by
other
users
and
the
you'll
see
it
show
up
here.
A
B
A
B
A
B
A
A
So
even
though
the
backhands,
I
believe,
support
up
to
100.
So
if
the
back
end
should
not
should
not
return
more
than
100
on
one
page,
and
that
is
for
country
security
purposes,
you
really
don't
want
anybody
to
be
able
to
pull
a
huge
amount
of
data
and,
like
you
know,
slow
down
the
system
so
for
for
performance,
they
do
limit
the
back
end
to
100.
A
So
what
I've
done
in
a
table
that
we
recently
implemented
was
implemented
a
selectable
page
size.
So
default
was
20,
but
you
can
say
I
mean,
show
me
50
or
show
me
100.,
so
you
can
see
like
pages
of
20,
50
or
or
100,
which
was
the
max
that
the
back-end
would
support
and
we
felt
like
that
was
a
great
improvement
to
the
user
experience.
A
So
the
option
for
page
size
that
we
selected
were
20,
50
and
100.
So
20
was
the
default,
which
kind
of
was
aligned
with
the
defaults
on
all
the
other
tables,
but
our
additional
user
experience
was
to
allow
the
user
to
then
override
it
and
say
well,
instead
of
20,
show
me
50
or
show
me
100.,
so
they
could
select
how
big
of
a
page
and
then
it
means
like
each
page
would
go
by
a
hundred.
So
you
see
the
first
hundred
the
second
one,
hundreds
third
100.
A
If
you
select
the
largest
page,
it
was
easier
to
see
large
amount
of
data
because
we
had
some
some
some
of
the
projects
that
we
were
looking
at
migrating
could
have
even
thousands
of
different
projects
or
sub
projects
in
them
so
listing
that
20
at
a
time
was,
was
really
ugly.
And
then
we
looked
at
that
yeah.
We
also
looked
into
lazy
load
or
just
kind
of
continuous
infinite
load
and
that
experience,
while
it
sounds
cool
when
you
really
try
to
use
it
it,
it
does
not
work
as
well
either.
A
So
my
other
comment
was
about
switching
from
medians
to
average,
and
thank
you
for
that.
I
did
try
using
vs
and
I
had
to
ask
like.
Why
is
my
average
and
I
would
call
it
average
right.
Why
is
my
average
zero
like
there's
just
no
weight
zero?
Well,
it's
because
I
have
half
of
my
values.
Are
zeros
and
half
of
them
something
else,
but
the
median
value
is
going
to
be
the
zero
and
it's
not
informative
at
all.
If
you
have
large
sets
that
are
so
not
well
distributed
right.
B
B
A
So
I
really
like,
where
they
work
good
and
finally,
thanks
for
showing
the
star
stop
events.
That
was
also
not
clear.
Just
like
just
understanding
like
what
is
the
definition
of
this.
I
thought
I
defined
this
as
such
and
such
and
I
can't
believe
these
are
the
numbers.
So
I
start
questioning
myself
as
far
as
like.
How
did
I
define
this
stage?
What
was
my,
what
were
my
events
so
just
showing
those
right?
A
B
Yeah
yeah
we
found
when
we
went
through
and
looked
at
the
usability
of
valley
stream
analytics
that
there
are
quite
a
few
things
where
you
have
to
really
go
and
read
the
documentation
to
figure
out
what's
going
on,
and
we
want
to
put
more
and
more
of
that
in
to
the
tooltips.
So
you
don't
have
to
reference
the
documentation
as
much.
I.