►
From YouTube: GitLab 14.1 Kickoff - Manage
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
the
kickoff
video
for
part
of
the
manage
stage
for
fourteen
one
today
larissa,
and
I
will
talk
about
what
the
optimize
group,
as
well
as
the
import
group,
are
planning
for
the
14
1
release.
A
So
with
that
said
larissa,
would
you
take
it
with
optimize.
B
Okay,
the
first
thing
that
we
have
coming
up
is:
we
are
going
to
be
adding
more
get
lab
features
into
the
devops
adoption
table
and
in
14.1
we're
going
to
be
focusing
on
security
scanning
features.
A
lot
of
this
will
be
back
end
work
recently.
We
added
this
dev
sec
and
ops
grouping
to
the
devops
adoption
table
so
we'll
be
doing
the
back
end
work
to
be
adding
a
lot
more
features
into
this
security
view
of
the
adoption
table,
specifically
we'll
be
adding.
B
B
So,
in
addition
to
well
actually,
instead
of
just
having
this
scanning
column,
which
currently
just
detects
whether
you've
got
any
kind
of
scan
enabled
will
be
will
be
getting
more
specific
about
which
scans
have
been.
B
Enabled
next
up
we'll
be
adding
a
view
like
this
to
the
adoption
table,
so
this
section
at
the
top
here
that
shows
out
of
the
number
of
features
that
are
available
in
the
devops
adoption
table.
How
many
of
those
features
have
your
groups
adopted?
So
this
will?
This
is
the
first
iteration
we're
making
to
give
you
a
better
sense
of
the
maturity
of
adoption
of
your
devops
processes.
B
Then
we
will
be
doing
some
improvements
to
value
stream
analytics
so
for
value
stream
analytics.
We
have
value
stream
analytics
available
both
at
the
project
level
and
the
group
level
there.
They
both
actually
use
different
code
bases
and
so
the
user
experience.
The
ui
is
a
little
bit
different
between
the
two
we
are
merging
those
together
and
the
next
iteration
we're
making
on.
B
That
is
to
add
sorry,
I've
gone
out
of
order
here
I'll
come
back
to
the
to
the
order
in
a
minute,
so
we
will
be
adding
a
filter
bar
in
the
group
view.
You
see,
you
have
this
filter
option
here
and
that's
not
available
in
the
project
view,
so
we'll
be
adding
filtering
to
the
project
view.
So
you
can
be
a
lot
more
specific
about
the
data
that
is,
that
you're
getting
returned
for
your
value
stream.
B
Also,
when
you're
in
a
stage-
so
let's
say
I'm
in
the
code
stage
in
the
project
view,
the
data
down
here
is
not
actually
part
of
a
table.
So
there's
no
ability
to
sort
the
data
in
group
value
stream
analytics.
We
did
implement
a
table
and
the
ability
to
sort.
So
you
can
actually
sort
based
on
time
so
that
you
can
see,
for
example,
in
the
code
stage
which
issues
have
spent
the
most
amount
of
time
in
the
code
stage
or
the
least
amount
of
time
in
the
code
stage.
B
Sorting,
okay,
I'm
going
to
go
back
to
the
one
that
I
skipped
over,
which
is
in
the
group
view
for
value
stream
analytics.
You
have
the
ability
to
select
projects,
so
you
can
narrow
down
the
issues
that
you're
seeing
here
to
specific
projects,
but
this
user
interface
is
a
little
bit
confusing.
So
if
I
search
for
a
project
here,
for
example-
and
I
picked
this
project-
then
the
drop
down
closes,
and
so
we've
found
that
users
think
you
can
only
filter
by
one
project.
B
In
reality,
you
can
filter
by
multiple
projects,
but
it's
just
not
a
very
intuitive
interface,
so
we're
going
to
be
making
some
improvements
to
that
drop
down.
So
it's
more
obvious
that
you
can
choose
multiple
projects
to
filter
by
and
finally
we're
going
to
be
doing
some
ongoing
background
work
to
change
how
this
date
selector
gets
applied
in
value
stream
analytics
today.
If
I
filter
by
these
dates,
it's
going
to
show
me
it's
going
to
apply
that
that
date
filter
to
the
date
that
an
issue
was
created.
B
It's
going
to
take
quite
a
bit
of
back
end
work
to
make
this
change
because
of
some
database
changes.
We
have
to
make
to
support
it,
but
we
we
have
a
great
proposal
that
adam
has
been
working
on,
we'll
go,
we'll
be
refining
that
proposal
in
14,
1
and
doing
a
proof
of
concept
and
potentially
even
starting
work
on
those
changes.
B
That's
all
I
have
harris
over
to
you.
I
see
you
have
some
questions.
A
B
A
Was
just
really
kind
of
lagging
behind
the
other
three
and
when
you
showed
all
three,
it
made
sense
that
you
would
have
that
you
would
have
like.
You
know
those
three
bullet
points.
I
really
love
that
view
because
it
makes
it
simple.
It
makes
it
also
kind
of
almost
balanced
okay,
and
you
should
check
out.
These
are
the
three
most
important
things.
Clearly,
it's
not
all
that
you
can
do
right,
but
you
know
these
are
three
most
important
things.
A
You
should
check
for
each
one
of
the
stages,
so
I
definitely
thought
that
was
cool
yeah.
B
That's
exactly
right,
so
ops
and
dev
have
a
lot
more
features
added
in
those
views.
Sec
is
very
sparse,
so
we'll
be
bringing
it
up
to
par
in
that
there
are
more
features
being
displayed
for
the
sec
grouping.
A
Awesome
so
looking
at
the
new
filter
that
you
were
working
on
for
the
groups,
it
looked
like
you
had
the
ability
to
look
at
the
vsa
by
milestone,
which
is
really
going
to
help
me
a
lot,
because
we
use
milestones,
kind
of
kind
of
as
a
standing
for
iterations.
B
A
We
never
switched
iterations,
so
I'd
be
able
to
see
kind
of
the.
You
know
the
progression
and
you
know
how
things
move
across
by
milestone,
but
I'm
curious
for
our
users,
who
might
be
using
iteration
as
iteration.
B
That's
a
great
point:
we
haven't
added
it
yet
because
iteration
is,
is
a
newer
feature
in
gitlab,
but
I
think
that's
a
great
point
that
we
should
create
an
issue
if
we
don't
have
one
already
to
add
iterations.
A
Cool
and
then
the
new
project
filter
selection.
A
I
I
there
are
several
interactions
that
really
caused
me
trouble
in
in
gitlab,
and
and
most
of
them
are
typically
you
know,
a
kind
of
a
type
ahead
search
among
many
things
so
like
finding
epic
to
associate
with
an
issue
finding
an
maybe
an
epic
or
an
issue
to
well,
let's
say
an
epic
to
associate
with
a
filter
like
those
are.
You
know
really
painful.
A
B
B
A
You
come
up
with
a
better
way,
I'd
like
to
see
if
there's
a
way
to
like
advertise
this,
and
maybe
you
know,
use
that
component
like
create
a
great
component
and
use
that
component
elsewhere.
I'm
really
a
strong
believer
in
creating
good
components,
as
opposed
to
like
recreating
the
same
solution
in
all
the
pages.
B
Absolutely
yeah,
I
agree
yeah.
I
know
that
they,
the
team,
has
been
looking
at
different
ways
that
we
can
optimize
how
that
search
works.
So
I'd
be
happy
to
share
that
with
you.
A
Yeah
and
I
haven't
seen
kind
of
any
visual
cues
in
the
front
and
two
date
that
kind
of
tell
me
one
way
or
the
other
what
those
dates
are.
So
I
was
wondering,
maybe
if
it
would
make
sense
to
just
add
you
know
pop
over
is
great
other
visual
cues.
Maybe
I
don't
know
if
the
from
and
the
two,
maybe
the
start
and
end
or
creation
date,
or
some
some
other
words
that
we
might
use.
That,
may
give
me
more
of
a
clue
what
those
days
really
represent.
B
Yeah
we
just
added
this
pop
over
in
the
last
release.
I
think
it
was
because
we
you're
right
it
didn't
say
what
these
date
ranges
apply
to
how
they're
how
they're
filtering
the
data.
So
we
added
this
line
here,
showing
data
for
workflow
workflow
items
created
in
this
date
range,
but
I
think
we
could
do
even
better
to
instead
of
having
it
in
a
pop-over.
Have
it
even
more
obvious.
A
Right
and
given
that
we're
actually
changing
the
meaning
of
this.
B
A
A
Thank
you
and
if
there's
nothing
else,
to
share
and
optimize
I'll,
take
it
from
here
and
talk
about
import.
So
let
me
share
my
view.
A
So
what
I
have
you
know
kind
of
the
most
important
directional
item
is
the
continuation
of
the
delivery
of
the
gitlab
migration
feature
and
if
I
scroll
down
just
a
little
further
you'll
see
that
there
were
a
lot
more
x's
in
like
what's
missing
from
the
ability
to
have
all
the
details
about
epics
migrate
across
with
the
group.
A
A
A
A
Next
up
are
some
of
the
features
that
are
still
related
to
the
group
migration,
which
is
also
known
as
bulk
import
in
the
code,
so
so
sometimes
some
of
that.
Some
of
those
words
actually
that
do
seep
through
into
the
issues
but
I'll
make
sure
that
they
don't
get
into
any
kind
of
marketing
or
release
notes.
A
So
the
one
thing
that
we've
been
looking
at
from
the
front-end
perspective
is
the
ability
to
select
more
than
one
group
for
for
bulk
import
or
for
the
group
migration.
A
So
in
particular
you
know
having
the
kind
of
the
check
boxes
on
the
side
of
the
table
and
then
being
able
to
select
one
or
many
of
these
and
once
they're
selected,
you
know
once
you
select
one
or
many
be
able
to
do
an
import
on
only
the
things
that
were
selected
up
until
now,
we
have
had
individual
imports,
so
each
one
of
these
lines
had
kind
of
an
import
button
on
it,
and
you
would
have
to
press
all
of
those
imports
for
each
one
of
the
lines
that
you
want.
A
A
So
that's
the
interaction,
we're
looking
for
and
we'll
be
moving
that
interaction
into
the
other
importers.
Once
we
get
the
group
migration
to
use
this
interaction,
but
even
more
importantly,
we
would
like
to
actually
go
ahead
and
start
a
new
component
that
I
hope
to
be
able
to.
You
know.
I
hope
that
other
groups
and
other
pms
will
be
able
to
utilize
in
what
they're
doing,
and
the
component
is
something
of
an
enterprise
table
component.
A
A
A
So
I
I
really
wanted
to
get
a
new
component
going
that
we
can
all
contribute
to
that
would
have
all
of
these
features
as
options
that
we
can
utilize
across
a
lot
of
different
views.
So
you
know
for
anyone,
who's
watching
and
who's
interested
in
contributing
to
this.
Please,
let
me
know,
please
let
ilya
know
he
is
the
front
developer.
Who
is
going
to
be
running
with
this?
We'll
start
it
off
by
just
creating
you
know
the
table.
A
That
has
the
one
feature
that
we
need,
but
we're
gonna
want
to
maybe
invest
and
expand
that,
as
opposed
to
you
know,
coming
up
with.
You
know
a
lot
of
different
ways
to
solve
the
same
problem,
so
this
is
kind
of
a
call
to
action
for
everyone
as
well
and
learners.
I'd
like
to
talk
to
you
as
well
about
that
vsa
table
and
see
if
we
can
maybe
combine
the
efforts
to
where
you
may
be
able
to
get.
A
You
know
either
the
pagination
or
you
know
just
like
some
of
the
things
that
we've
implemented
in
in
our
table
and
we
get
the
pretty
column
sorting.
B
A
A
Yeah
and
even
an
expandable
table
to
where
maybe
you
know,
each
one
of
these
items
does
have
sub
items.
So
there
are
a
lot
of
views
where
that
makes
sense
if
you're
looking
epic,
sometimes
epics
have
you
know,
sub
epics
and
potentially
sub
potential
issues
underneath.
A
B
We've
been
talking
about
the
expansion
as
well,
because
in
the
devops
adoption
table
we
show
groups
and
we
it
would
be
interesting
to
expand
those
out
and
see
subgroups
within
the
groups
or
projects
within
the
groups.
Right.
A
And
we
have
the
same
name
here,
because
this
actually
shows
groups
like
this
is
importing
groups,
so
the
groups
will
have
subgroups
and
right
now
we
can
just
select
the
top
level
groups
and
you
just
kind
of
select
the
top
level
group
and
then
everything
underneath
gets
migrated,
but
there's
no
ability
to
just
pick
and
choose
which
one
which
one
of
the
subgroups
you
may
want
to
migrate.
So
that
would
give
us
that
would
give
us
that.
A
Cool
next
up
is
allowing
groups
to
be
re-imported,
so
the
one
thing
that
we
have
a
lot
of
need
for
is
for
a
group
once
it's
imported
right
now,
it
does
tell
you
that
it
was
already
important
gives
you
a
link
to
where
it
got
imported
to,
but
in
case
that
you
know,
you
want
to
run
another
import
a
week
later,
because
it
was
just
kind
of
a
test
import
and
now
you
want
to
do
it
for
real
and
you
you
know
you
want
to
import
it
again.
A
You
should
be
able
to
rerun
or
re-import
a
group
and
right
now,
that's
not
even
possible
without
you
deleting
the
group,
that's
already
there
or
renaming
the
source,
so
there's
kind
of
a
creating
a
mismatch
between
the
source
and
destination.
A
So
we're
going
to
be
looking
to
to
do
that
in
14
1..
Next,
one
is
something
that
we've
tried
something
and
didn't
work
and
came
back.
A
So
we
have
you
know
we
have
originally
found
an
issue
to
where,
if
there
is
no
dot
git
in
the
url
and
it
is
required,
like
it
exists
out
there,
we
are
unable
to
do
the
import,
so
we
kind
of
had
to
require
the
users
to
put
the
dot
git
in
in
the
url
in
order
to
avoid
those
just
mistakes
like
typos
or
just
not
even
thinking
about
the
fact
that
you
need
to
really
add
a
dot
git
if
it
if
the
url
requires
it.
A
So
we
made
this
a
requirement
and
it
turns
out
there's
a
type
of
git
server
that
has
the
opposite
problem,
which
is
it
does
not
allow
the
dot
git
extension
on
their
git
servers.
So
we
have
pretty
much
disabled
the
ability
for
those
people
to
do
imports
so
we're
finding
compromise
in
the
middle,
which
is
show
a
warning.
A
So,
in
most
cases,
omitting
the
dot
git
will
cause
you
a
failed
import,
but
in
you
know
for
for
those
cases
where
it
doesn't
we'll
just
kind
of,
let
you
know
that
hey,
you
have
not
put
the
dot
git
in
the
url
check
it
and
if
you
want
to
proceed,
go
ahead
and
proceed.
So
this
is
a
second
attempt
on
this.
A
Finally,
the
one
thing
that
we
don't
currently
have
in
the
group
export
import,
so
the
current
feature
set
for
migrating
groups
does
not
allow
for
migrating
users,
so
you're
supposed
to
get
your
users
migrated
ahead
of
the
import
manually
or,
however,
you
want
to
do
it
by
engaging
professional
services,
but
all
that
needs
to
be
like
all
those
users
kind
of
need
to
be
already
in
the
destination
before
you
attempt
an
import.
A
If
you
don't,
then
all
of
the
objects
that
get
transported
that
they
get
migrated
such
as
epics
and
anything
else,
will
get
associated
with
the
importer
user.
So
the
importer
user
will
look
like
the
the
creator
of
all
the
epics
creator
of
all
the
comments,
because
we
have
no
user
to
match
it
with
so
the
big
enhancement
once
we
reach
the
parity
with
the
current
export
import
is
to
start
including
the
users
in
the
migration
and
really
have
a
full
migration
of
approve.
That
includes
users
from
one
instance
of
the
clap
to
another.
A
This
is
something
that
has
not
been
solved
before.
We
have
run
into
several
roadblocks
prior
to
this
by
just
exploring
this
area
just
even
matching,
because
using
emails
to
match,
which
is
the
most
logical
or
probably
the
best
way
to
match.
The
two
users
between
the
two
systems
is
a
potential
security
issue,
because
if
the
users
have
made
those
emails
private,
we
should
not
be
exposing
those
in
files
or
in
network
traffic.
A
A
B
Yeah
really
exciting
to
see
the
progress
that
you've
made
on
the
group
import.
I
know
you've
been
working
on
that
epic
for
a
long
time
and
it
looks
like
you're
really
close
to
finishing
that
out.
That's
going
to
feel
good
and
then
I
really
liked
the
multi-group
selector.
That
looks
like
a
huge
time
saver
for
users
and
then
a
question
about
the
user
import
that
you're
going
to
be
investigating.
A
B
A
That
will
be
important.
You
know
the
users
would
probably
be
migrated
first
and
then
we
would
migrate
the
groups
and
then,
as
the
groups
are
getting
migrated,
we
would
associate
the
users
with
the
groups.
That's
what
we
currently
do
with
epics.
So,
okay.
A
Exist
already
right
now
we
kind
of
have
to
assume
that
users
already
exist.
We
don't
do
that
part,
but
if
the
users
exist
in
a
destination,
when
we
migrate
an
epic,
we
will
look
up
that
user,
and
if
we
find
that
user
we
will
associate
the
user
as
a
creator
as
a
commenter,
so
we'll
find
all
the
right
users
in
the
destination
and
associate
them
with
each
one
of
the
areas
where
there's
a
user
association
on
epic.
So
for
groups
as
well,
we
will
look
to
transplant
that
membership
as
well.
B
B
Yep
yeah
and
then
just
a
general
question
that
came
up
today
in
a
conversation
when
we
are
so
in
the
devops
adoption
table,
you
can,
you
manually,
add
groups
into
that
table
to
view
adoption
feature
adoption
information,
and
so
that's
fine,
if
you
just
want
to,
if
you're
already
set
up
using
the
adoption
table-
and
you
just
want
to
add
one
or
two
groups,
but
if
you're
going
in
there
for
the
first
time
and
setting
up
a
new
view-
and
you
have
a
thousand
groups,
I
think
we're
really
going
to
need
a
way
to
do
some
kind
of
bulk
import
of
groups
into
that
table.
B
A
Well,
I
would
say,
maybe
it
might
make
sense
to
take
a
look
at
the
group
migration
ui.
Okay,
like
look
looking
at
that
view
and
I'll
try
to
pull
it
up
and
see
if
I
can
actually.
A
B
A
B
B
A
A
So
that
may
be
a
way
to
to
to
go
by
that
as
well.
And
then,
if
I
were
to
you
know
and
then
there's
a
button
that
says
import
all
the
problem
here
is
I've
already
completed
these
two
imports
and
I
can't
import
anymore
yeah
so
that
that
is
disabled.
A
But
I
feel
like
a
similar
interaction
would
be
needed
and
you
might
be
able
to
use
the
same
apis.
This
ui
uses
because
this
ui
really
discovers
what
are
all
the
groups
available
yeah
and
how
do
I
show
them
to
the
user
in
a
way
that
they
could
search
narrow
down,
paginate
and
then
select
a
few
things.
A
B
User
experience
does
this:
is
this
at
an
instance
level
or
if
I
was,
if
I
was
already
inside
a
group,
would
it
have
a
would
the
api
have
awareness
of
the
subgroups
in
a
group.
A
So
this
is
an
instance
of
this
because
we
are
actually
connecting
to
remote
instance
of
git
cloud
right.
So
this
connection
here
is
to
remote
instance
of
gitlab,
so
we're
connecting
to
an
instance
and
talking
to
the
instance
and
saying
please
send
us
all
the
groups
that
you
have
that
we
that
this
user
has
access
to
to
migrate
over
yeah,
and
then
we
get
a
list
of
top
level
groups
from
the
other
instance.
Okay,.