►
From YouTube: GitLab 13.8 Kickoff - Enablement:Global Search
Description
Leave us feedback in our kick-off issue.
https://gitlab.com/gitlab-org/search-team/team-tasks/-/issues/27.
B
Hi,
I'm
terry,
so
the
first
thing
we're
going
to
be
talking
about
is
the
move
of
the
group
in
project
filters
to
view
components,
that's
something
that
we're
going
to
be
working
on
for
13,
8
and
john.
If
you
would
move
to
the
next
tab
and
as
part
of
that
we're
going
to
be
addressing
an
issue
where,
if
you
select
a
project
from
the
drop
down,
it
doesn't
auto-populate
the
group,
so
that
fix
will
be
included
in
the
work
that
is
done
when
the
view
component
is
moved
over.
A
You
know
that's
great.
I
know
that
there's
been
a
lot
of
feedback
from
our
community
on
actually
like
trying
to
improve
the
way
these
group
and
project
drop
downs,
work,
and
so
it's
exciting
to
see
that
we're
going
to
be
moving
us
into
a
view
component,
which
will
make
additional
updates
further
and
we're
already
getting
our
first
update
in
which
will
be.
You
know
something
that
is
at
least
a.
A
A
Yeah-
and
so
this
is,
you
know,
this
is
interesting.
We
talked
about
this
a
little
bit
as
we
were
getting
into
1370
and
really
kicking
off
the
work
that
was
going
on
here.
You
know
it's
not
it's.
It's
not
clear
that
we
actually
get
all
of
this
complete
in
138
that
we're
going
to
keep
moving
through
that
milestone,
but
once
this
is
complete,
we
do
expect
that
users
are
going
to
have
faster
searches
when
they're.
Looking
at
issues,
we
had
something
that
came
up
in
1307
was
a
great
surprise.
B
Right
the
work
that's
already
been
completed
in
13
7
is
denormalizing
the
permission
data
for
issues
which
is
moving
the
permission,
data
into
the
issues,
documents
versus
trying
to
pull
them
from
the
project
documents
and
then
removing
the
reliance
upon
the
project
data
and
this
the
search
queries
for
elasticsearch.
So
when
you
do
group
global
and
project
searches,
it's
only
querying
data.
That's
issued
data
in
the
issue
document
and
that
was
also
already
completed.
A
And
so,
if
I've
got
this
right,
you
know
if
I'm
a
user
and
I'm
going
through
and
I'm
searching
for
something
in
issues
you
know
before
I
would
have
actually
searched
on
something.
You
know,
let's
say
that
my
my
company
does
a
lot
of
permissions
across
projects
that
say
you
know.
Every
project
has
a
specific
list
of
users
that
are
able
to
view
it.
We
use
confidentiality
a
lot.
A
So
if
I'm
understanding
this
correctly,
we
actually
we're
doing
a
bunch
of
checks
to
make
sure
that
the
list
that
comes
back
is
something
that
you
can
view,
and
this
would
have
had
been
done
across
any
project
that
would
have
a
result
that
was
going
to
be
shown
and
now
that's
actually
going
to
be
consolidated.
So
the
permission
information
is
in
the
issue
itself,
so
we
won't
have
to
check
against
the
project.
Is
that
right.
A
Yeah,
that's
great,
especially,
I
think,
for
the
customers
that
are
using
lots
of
you,
know
confidentiality
and
projects
and
using
permissions
across
projects
to
view
them
like.
That's
where
it
seems
like
it
would
have
the
most
impact,
which
there
are
a
lot
of
our
customers
that
do
have
some
complex
structures
and
how
they
manage
projects.
That
way.
B
A
Okay,
that's
super
all
right,
so
the
next
thing
we're
going
to
be
working
on
we're
going
to
start
working
through
some
of
the
pieces
in
the
admiral
console.
The
first
thing
that
we're
going
to
do
is
move
advanced
search
out
of
the
general
section
that
it's
in
right
now,
so
that
it
actually
appears
next
to
general,
with
settings
so
you'll
be
able
to
go
to
admin
settings
and
then
see
advanced
search
and
with
advanced
search.
We're
also
going
to
be
starting
to
update
some
of
these
areas.
A
There's
a
lot
of
different
version
updates
that
are
going
to
be
happening
and
they
will
be
enabling
new
features
we've.
We
definitely
want
to
make
sure
that's
more
visible
to
our
customers,
as
we
can,
as
we
actually
see
more
migration
to
the
newer
versions
of
elasticsearch
in
the
in
the
years
to
come,
we'll
be
able
to
provide
more
feature,
sets
and
less
complexity.
A
All
right,
we're
also
going
to
be
improving.
Something
that
came
up
in
some
research
is
a
really
important
use
case
for
us,
so
file
searching
has
become
one
of
our
top
use
cases
that
we've
seen
our
users,
you
know
really
doing
in
global
search,
and
we
want
to
make
this
easier.
So
I've,
you
know,
pulled
together
three
items
that
I
think
is
going
to
help
a
lot
with
that
and
the
first
one
is
is
really
just
a
bug
right.
A
So
when
you're
actually
searching
for
a
file
using
path,
if
it
has
a
space,
it
doesn't
always
find
it
fun
and
we'll
be
addressing
that
fixing
it.
The
next
one
is
searching
with
the
filename
syntax
as
a
confusing
behavior.
So
when
you
do
a
file
name,
syntax
search-
and
you
have
your
wildcard
in
there
to
try
to
capture
everything
that
has
an
extension
as
an
example.
It
doesn't
return
some
of
those
results
and
then
modifying
this
by
adding
the
wild
card
in
front
of
the
file.
A
So
right
now,
when
you
go
into
a
search
and
if
you
copy
this
out
of
you
know,
for
example,
if
you're
copying
it
out
of
a
you,
know
a
file
location
from
internet
or
something
like
that,
you
paste
in
the
google
search,
it
doesn't
actually
find
it
it'll
find
references
to
it
in
the
code,
but
it
won't
find
the
file
that
you're
looking
for
and
as
we
make
this
searchable
you'll
be
able
to
just
take
what
you
pasted
into
the
search
box
and
be
able
to
return.
You
know
that
specific
result.
A
C
C
C
A
Yeah,
thank
you
and
I'll.
Tell
you
it's
really
good
to
see
that
we've
had
you
know
more
community
contributions
continue
to
increase
every
milestone,
and
I
look
forward
to
seeing
even
more-
and
I
really
want
to
help
do
whatever
I
can
to
advocate
prioritizing
issues
that
will
give
our
community
an
opportunity
to
develop
with
us
and
contribute.