►
From YouTube: GitLab 14.0 - Enablement:Global Search
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
Hi,
I'm
john
mcguire.
I
am
the
senior
product
manager
for
global
search.
I'm
going
to
take
you
through
some
of
the
things
that
we
have
going
on
in
our
get
lab
140
release.
The
very
first
thing
is
before
you
do
your
14-0
upgrade.
If
you
are
running
advanced
search,
you
definitely
want
to
upgrade
to
1312
prior
to
that.
A
During
that
13-12
migration,
it
will
remove
some
of
the
components
that
won't
be
referenced
in
14.
We
do
this
from
time
to
time
to
make
the
code
less
complex
so
that
it's
easier
to
add
features
in
the
future,
and
if
you
don't
do
the
1312
upgrade
before
doing
14,
you
might
have
to
rebuild
your
entire
index
and,
if
you're
running
something
that's
like
half
a
terabyte
or
terabyte
that
could
take
several
hours,
maybe
even
half
a
day
in
some
cases.
A
A
So
the
first
thing
that
we
are
happy
to
start
working
through
is
vulnerability.
So
vulnerabilities
has
been
introduced
last
year
in
in
a
new
form
for
us
that
that
we
don't
have
yet
searchable
in
gitlab,
and
we
are
going
to
start
working
through
the
details
of
what
it
takes
to
add
this
as
a
new
content
scope.
A
This
is
very
exciting
because
we
haven't
added
a
new
content
scope
into
advanced
search
for
maybe
two
years
and
the
last
scope
we
really
added
in
the
search
overall
was
epics,
but
that
does
not
use
advanced
search
integration.
Yet
so
this
will
be
available.
I
will
use
the
advanced
search
integration
and
we're
really
looking
forward
to
getting
started
on
this.
It
won't
be
released
in
14,
but
we
are
going
to
start
working
through
this
feel
free
to
comment
on
the
issue.
A
A
So
a
lot
of
times
when
you're
trying
to
do
a
search,
you
need
to
change
the
group
that
you're
in
or
set
the
group
that
you're
in
change
the
project
that
you're
in
the
interface
can
be
a
little
bit
wonky
it's
it's
kind
of
difficult
to
necessarily
find
all
of
the
groups
that
might
be
listed
or
all
the
projects
that
are
there,
there's
a
little
limitation
to
it.
The
capabilities
that
we've
that
we've
provided
so
far
allows
us
to
actually
add
multiple
groups
and
projects.
A
So
what
we're
really
planning
on
and
wanting
to
do
and
looking
forward
to
in
this
release
is
actually
having
the
ability
to
do
multi-select
for
this.
So
this
is
incredibly
exciting,
because
now
you
have
better
options
than
just
selecting
one
group
or
selecting
every
group,
including
maybe
even
public
groups.
So
this
will
be
a
lot
more
succinct
to
try
to
give
you
back
information
and
pre-filter
the
results
to
to
look
at
things
that
you're
you're,
more
likely
looking
for
this
is
applied
to
advanced
search.
A
It
works
across
all
of
the
scopes
really
looking
forward
to
bringing
this
forward,
and
we
do
have
the
same
element
that
we're
looking
at
for
project
as
well:
project
drop-down
and
moving
on
into
this
is
more
of
a
bug.
So
we
actually
have
had
some
reports
in
the
past
month
from
some
users
that
have
tried
to
move
large
editions
into
their
repo
and,
as
it
starts
to
index
an
advanced
search.
Sometimes
it
looks
like
the
industry
can
just
get
stuck
or
it
times
out,
for
you
know
an
hour
or
more.
A
So
we
believe
we
have.
This
problem
figured
out
and
a
solution
for
it
and
we'll
be
working
through
this
it'll.
It
should
be
included
in
14.0
so
that,
if
you
upgrade
1400
you've
had
this
problem,
we
hope
it's
resolved.
Definitely
look
forward
to
feedback
on
that
and
if
you
still
see
additional
issues,
I
am
happy
to
to
hear
them.
Please.
Let
me
know.
A
So
the
next
piece,
as
we've
added
in
different
variable
pieces
into
different
scopes,
one
that
has
kind
of
come
up
as
our
next
item
is-
is
I
think
it's
it's
not
going
to
be
too
complicated
for
us
to
really
add
this,
since
we've
already
added
additional
sort
options
in
other
areas,
we're
going
to
be
adding
sort
into
epics
the
epic
scope
for
global
search.
Now,
this
should
be
a
feature
that's
available
for
both
users
that
are
using
basic
search
and
users
that
have
the
advanced
search
integration
enabled.
A
A
So
we've
spent
the
last
few
milestones
last
five
milestones
breaking
out
the
index
by
scope
and
there's
lots
of
reasons
and
advantages
to
doing
this.
But
one
of
the
biggest
advantages
that
we
have
is
that
we're
now
going
to
be
able
to
allow
for
advanced
search
to
have
a
lot
more
features.
A
It's
going
to
be
a
lot
easier
to
create
these
features
and
in
preparation
for
that,
we
have
put
together
some
conceptual
designs
of
where
we
want
to
take
this
and
what
features
we
want
to
put
on
to
the
future
of
of
gitlab's
advanced
search,
and
so
this
is
our
first
conceptual
design
that
you're
looking
at
to
kind
of
give
you
the
quick,
walkthrough
extended
out
the
search
box,
move
the
scopes
over
to
the
left.
There
are
several
different
facets
that
are
available
to
let
you
search
by
groups,
type
status,
author
very
helpful
labels.
A
Labels
don't
exist
in
the
index
yet
so
we
would
need
to
add
those
to
put
it
in
there.
Of
course,
with
that,
there's
a
redesign
for
the
search
result
to
include
context
of
some
of
this
additional
information,
so
that,
when
you
do
decide
to
use
a
facet
or
a
filter,
you'd
be
able
to
see
that
the
results
that
come
back
match
the
filter
that
you've
used.
A
A
I
would
really
encourage
everybody
to
really
get
in
and
try
to
use
the
code
search
and
give
us
feedback
on
it,
because
we
are
actively
going
to
be
iterating
on
this
in
the
very
near
future.
This
design
shows
the
ability
to
do
some
other
faceting.
Of
course
we
have
grouping
projects,
we
have
languages
here,
so
you
can
then
filter
it
out.
A
Of
course,
most
repos
are
going
to
have
lots
of
different
languages
in
it,
so
this
allows
you
to
kind
of
filter
that
down
moving
the
idea
of
what
we've
done
in
the
past
for
syntax
search
into
something
that
is
hopefully
a
little
bit
more
discoverable
and
navigable.
I'm
sure
some
people
that
are
watching
us
probably
don't
even
know
that
we
have
the
ability
to
syntax
search
so
trying
to
give
this
more
context
for
users
that
that
might
find
it
useful
is
very,
very
helpful.
A
There's
a
couple
other
things
that
we're
going
to
be
working
through
with
this
too
one
of
the
things
that's
not
pictured.
Here
we
want
to
start
looking
at
how
we
can
incorporate
the
concept
of
blame
into
code
search.
Blame
can
add
additional
metadata.
That
would
allow
us
to
look
at
some
of
the
results
and
say
you
know
not
when
the
file
was
updated,
but
when
was
that
line
of
code
updated?
What
was
the
commit
that
updated
it?
A
What's
the
purpose
of
that,
mr
that
it's
or
the
merge
request
that
it's
connected
to
so
trying
to
connect
in
all
this
data
is
the
future
of
where
we
want
to
take
a
global
search.
I'm
really
excited
to
show
some
of
these
comps,
and
that
is
our
preview
for
14.0
very
excited
to
hear
feedback
on
it,
and
let
me
know
your
thoughts
you
can
reach
out
to
me
in
gitlab
or
by
email.
I'm
always
happy
to
work
back
with
our
with
our
customers
on
their
ideas.