►
From YouTube: GitLab 13.4 Kickoff - 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
A
We
may
even
remove
all
of
the
mark
down
to
a
search
result.
All
those
features
that
are
really
enable
markdown.
You
should
be
able
to
see
on
the
resulting
page
anyway,
but
it
should
it
should
create
a
significant
improvement
in
our
performance
and
the
next
item.
We're
going
to
be
looking
at
is
kind
of
a
traditional
search
question
that
dates
back
for
a
very
long
time.
A
Should
we
use
and
or
or-
and
there
is
a
lot
of
debate
on
what
we
would
use
and
versus,
or
we
are
starting
to
look
at
this
right
now,
we're
currently
defaulting
to
and
if
we
move
to
or
one
of
the
things
that
we're
going
to
need
to
do
is
you
know
really
make
sure
that
we're
giving
the
right
type
of
rank
because
you're
going
to
get
a
lot
more
results
back
and
that
really
is
going
to
require
a
better
rank.
So
we
may
try
this
and
we
may
actually
change
it
back.
A
If
we
don't
see
the
results
that
we
want.
As
we
add
more
features
in
the
future,
it
will
be
easier
to
and
really
important
to
actually
move
to,
using
or
so
that
we
don't
miss
the
opportunity
of
returning
everything
that
the
user
may
want
to
see
and
then
letting
them
kind
of
filter
out
what
they
don't
want.
A
The
next
thing,
I'm
really
excited
about
we're
we're
going
to
start
updating
the
user
interface.
Now
this
hasn't
really
been
updated
in,
I
think
two
years,
but
we
have
a
lot
of
modernization
to
search
that
we
want
to
plan
we're
going
to
start
iterating
on
this
in
thirteen
four.
So
the
we're
gonna
have
a
new
result
view
we're
at
least
gonna
target
issues
and
we'll
we
may
add,
merge
requests
to
that
as
well.
A
A
One
of
those
type
of
features
we're
looking
at
right
now-
and
we
do
want
to
do
something
with
this
in
thirteen
four,
but
it
may
be
an
iteration
of
it
is
to
add
the
ability
to
filter
out
issue,
searches
and
merge
requests
by
their
status.
So
the
if
the
state
is
open,
closed
merged
we
want
to.
We
want
to
give
the
user
control
of
actually
determining
what
they
have
showing
at
any
particular
time.
A
You
know
sometimes
it's
not
helpful,
to
have
a
bunch
of
issues
that
are
listed
or
merge,
requests
that
are
merged
already
or
issues
that
are
already
closed,
so
you
should
be
able
to
filter
those
out,
but
we
don't
want
to
prevent
them
from
showing
up.
So
we
do
want
to
make
sure
we
continue
to
include
them,
but
let
the
user
determine
if
they
want
to
filter
those
out
or
not.
A
And
finally,
the
other
thing
which
I
think
is
a
long
time
coming,
is
the
ability
to
sort
so
to
each
user
at
each
time,
you're
actually
going
through
and
looking
for
an
issue
or
a
merge
request.
We
have
some
rank
in
there
and
the
rank
is
going
to
try
to
say
this
is
what
I
think
is
the
most
important,
but
the
sort
is
really
going
to
give
the
user
the
control
of
saying
I
want
to
see
the
most
frequent
things.
I
realize
that
some
of
these
ranks
are
maybe
the
most
accurate.
A
But
what
I
really
need
is
the
newest
thing.
That's
out
there
or
the
thing
that's
most
recently
updated,
so
we're
going
to
be
adding
sort
into
the
plan
would
be
at
least
issues
and
we
hope
merge
requests
as
well,
but
eventually
you
want
to
add
all
these
features
across
all
the
different
scopes
that
you
can
do.