►
From YouTube: GitLab 15.3 - Enablement:Global Search
A
So
the
first
thing
that
we're
looking
at
is
a
feature
that
has
to
do
with
autocomplete
drop
downs
and
in
the
navbar.
This
is
a
feature
that
works
and
it's
it's
actually
really
helpful,
but
sometimes
it
is
really
slow
and
it
just
depends
on
a
couple
different
things
of
why
it
could
be
slow,
but
we
have
a
pretty
good
fix
that
should
make
this
very
fast
and
that's
going
to
be
going
into
15
3..
A
The
next
thing
that
we're
going
to
be
working
on
is
a
a
big
change.
This
is
maybe
one
of
the
biggest
changes
we've
made
to
the
way
things
look
on
the
result
page,
but
we're
moving
the
scopes
from
where
they
normally
would
be
up
here
at
the
top
we're
going
to
move
the
scope
list
over
to
the
left-hand
side.
This
allows
us
to
kind
of
show
this
a
little
bit
more
in
a
traditional
design.
A
So
that's
a
pretty
important
big
change
coming
the
next
piece
we're
going
to
be
getting
into
has
to
do
with
code
search.
We've
been
iterating
on
creating
language
filters
in
code
search
for
a
couple
different
milestones.
We
believe
that
the
15
3
will
be
the
one
where
everything
is
going
to
come
together.
A
We
believe
it's
going
to
be
delivered
down,
15
3.,
so
we're
very
excited
about
that,
and
going
into
code
search
a
little
bit
more
we're
starting
a
new
epic
around
trying
to
make
code
search
work
more
like
it
does
on
a
local
ide.
That
seems
to
be
where
a
lot
of
our
developers
that
we
work
with
and
customers
really
see
that
they're
really
kind
of
expecting
something.
A
That's
a
little
bit
more
familiar
that
the
first
area
we're
going
to
start
delivering
on
this
has
to
do
with
some
of
the
special
character
functions
that
are
difficult
to
make
work
because
of
how
this
gets
indexed
and
it
made
available
and
so
we're,
starting
with
not
trying
to
change
how
that
works,
but
actually
build
out
the
test
case.
That
says
you
know
here
are
the
test
suite
that
we
want
to
make
sure
our
examples
that
work
and
then
with
test
driven
design.
B
Hi,
so
for
the
maintenance
work
that
we
planned
for
b-slab
15-3
release,
we
have
two
major
issues.
First,
we
currently
have
an
advanced
search
migrations.
That's
going
to
pause
the
indexing
if
we
detect
a
unsupported
elasticsearch
version
or
open
search
version,
and
this
should
be
converted
from
a
migration
to
a
preflight
check.
That's
used
in
the
migration
workers
to
support
future
search
versions
upgrade
and
the
application
work.
B
A
All
right
so
with
every
milestone,
we're
always
trying
to
kind
of
pay
off
some
of
our
check
debts,
and
then
you
know
also
trying
to
make
sure
that
we're
keeping
with
a
goal
of
decreasing
the
number
of
bugs
that
are
are
currently
out
there.
This
milestone,
we
have
two
pretty
important
ones,
one
of
them's,
a
little
bit
old
too.
So
it's
good
to
be
able
to
clear
some
of
the
older
ones
out.
A
The
first
one
is
our
is
a
sev2
and
it
has
to
do
with
search
results
that
have
a
long
line,
that's
showing
it
that
actually
causes
for
horizontal
scrolling
scrolling
to
happen
in
the
result
view,
and
so
it
you
can
kind
of
see
that,
like
it,
it
actually
makes
this
the
result
scroll
because
it
just
has
too
many
characters
in
that
one
line,
and
so
we
have
a
a
fairly
simple
change.
It's
just
going
to
actually
allow
us
to
wrap
it,
as
the
different
number
of
characters
displayed
in
that
that
table
will
change.
A
The
next
piece
has
to
do
with
something
that
can
be
really
confusing
to
customers
when
you
have
a
a
default
scope
that
is
set
and
you
change
your
project
from
a
project
search
to
a
group
search
that
default
scope
will
not
persist,
it'll
change
and
you
could
be
looking
at
code
results
and
all
of
a
sudden,
it
switches
over
to
your
project,
results
or
issues.
So
this
is
something
that
we're
it
can
be
definitely
confusing,
because
it's
not
something
you
asked
for
when
you
changed
your
search
type.
C
So
today
we
do
offer
you
know
a
way
to
get
to
our
documentation
from
our
results
page,
but
it's
somewhat
hidden
from
users,
and
we
want
to
make
this
a
bit
easier
for
them
to
find
and
get
help
when
they
need
it.
So
we've
already
actually
tested
one
solution
with
this
during
some
solution.
Validation
last
milestone-
and
we
just
have
a
little
bit
more
design
work
to
do
on
this-
to
get
this
ready
for
development.
C
So
that's
one
of
the
items
that
we'll
be
focusing
on
the
next
item
that
we'll
be
working
on
is
adding
epics
to
advanced
search.
So
one
of
the
other
insights
that
came
out
of
our
research
was
that,
because
things
often
change
between
our
different
scopes,
such
as
issues,
mrs
epics
things
not
appearing
the
same
in
the
ui
or
offering
different
functionality
based
on
which
scope
you're
on
that
can
be
somewhat
problematic
for
users
and
make
it
harder
for
them
to
use
our
product.
And
so
one
thing
we're
trying
to
do
is
kind
of
standardize.
C
Some
of
the
different
options
that
we
have,
as
well
as
things
like
sorting
options
and
so
by
adding
epics
into
our
advanced
search
index,
we'll
be
able
to
make
that
appear
more.
Like
you'd,
see
for
like
issues
nmrs
where
you
can
have
certain
filters,
such
as
like
open
and
closed
as
well
as
other
facets
that
we
continue
to
add
on
along
the
way.
A
All
right
that
looks
like
some
really
good
stuff
that
we
have
coming
up
here
for
15.3.
It's
definitely
see
how
the
the
ability
to
kind
of
break
this
out
into
feature
and
maintenance
and
bug,
as
well
as
ux
design,
really
helps
kind
of
explain.
You
know
where
we're
kind
of
going
from
a
feature
standpoint.
A
How
we're
you
know
still
investing
in
the
ideas
of
continuing
to
add
maintenance
and
pay
down
our
technical
debts
around
maintenance
and
bugs,
while
we're
still
looking
forward
with
some
of
the
things
that
are
coming
out
with
ux
design.
So
I'm
really
excited
about,
especially
some
of
the
things
we
have
coming
in
153,
like
moving
the
scopes
over
to
the
left
and
all
the
changes
that
we
have
coming.
That
will
be
left
nav
related
as
we
continue
to
create
features
for
global
search.
Thank
you.