►
From YouTube: GitLab 14.1 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
Hi,
I'm
john
mcguire,
I'm
the
search
product
manager
for
global
search.
I'm
going
to
take
you
through
some
of
the
things
that
we're
working
on
for
get
lab,
14-1
and
cover
some
of
the
research
that
we're
doing
for
beyond
that,
and
I
have
with
me
nick
nick-
is
the
designer
who
who
works
with
me
on
global
search,
and
so
he
will
take
us
through
some
of
the
design
pieces
that
we're
working
through
during
this
milestone.
A
These
are
pieces
that
won't
be
developed
at
the
time,
but
they'll
they're
getting
prepared
to
go
into
the
development
cycle.
A
So
the
first
item
that
we
have
is
something
that
really
comes
out
of
the
understanding
of
how
users
are
using
the
drop
downs
that
are
provided
in
the
group
search
in
the
project
search.
A
We
find
that
a
very
high
percentage
of
users
are
using
the
same
groups,
which
makes
a
lot
of
sense
but
they're
also
using
just
a
handful
of
different
projects,
and
so
we
thought
it'd
be
a
very
helpful
feature
to
add
in
the
recently
searched
groups
and
projects
in
these
drop-down
lists
and
show
those
at
the
top.
And
the
idea
with
this
is
that,
if
you're
trying
to
search
through
it,
you
don't
have
to
have
an
extensive
list
of
of
projects
that
you
may
not
be
interested
in
that
time.
A
A
The
next
thing
we're
going
to
be
working
through
is
around
the
timeout
state
in
a
search
result
page
that
currently
500.
So
if
you
have
a
query
that
may
be
complex
for
some
reason,
it
takes
a
long
time
to
get
a
response
back
today.
This
will
time
out
to
a
500
page.
We
think
it
would
be
more
helpful
to
time
this
out
and
the
with
a
message
in
the
results
section
that
then
allows
you
to
continue
to
make
changes
to
what
you
had
in
the
search
without
having
to
click
the
back
button.
A
A
Okay,
the
next
piece
that
we're
working
on
in
14.1
is
to
improve
some
of
the
sorting
features
that
we
have
across
project
and
group
drop-downs
in
global
search.
So
this
is
a
process
to
get
through
lots
of
particularly
complex
solutions
that
we're
just
now
getting
started
on,
but
there
is
a
lot
of
value
to
really
getting
this.
This
feature
kind
of
ironed
out
and
to
to
understand
how
we
can
provide
a
better
selection.
A
Here
we
have
gotten
lots
of
feedback
from
our
customers
over
the
years
requesting
that
we
provide
a
better
experience
in
those
project
and
group
drop-downs.
B
A
A
And
now
I'm
going
to
hand
it
over
to
nick
to
kind
of
talk
through
what
we
do
on
the
research
side,
because
we
spend
a
lot
of
effort
to
really
try
to
understand
what
is
the
right
experience
and
how
do
we
want
to
really
craft
that
for
users,
I'm
hoping
that
can
kind
of
share
a
little
bit
about
that
process
with
us?
He
takes
us
some
of
the
things
that
we're
working
on
designing
through
this
14-1
milestone.
B
What
we'll
do
is
is
some
generative
research
just
to
to
better
understand
some
of
these
tasks
that
users
are
trying
to
do
and
some
of
the
problems
that
they're
facing
while
doing
them,
and
during
this
research
we
came
through
with
quite
a
few
different
insights
of
how
we
could
make
specifically
searching
for
code
better
and
meet
their
needs
and
expectations
a
little
bit
easier
in
the
future,
and
so
what
we're
doing
now
is
we're
working
through
and
we're
actually
trying
to
put
together
some
designs
of
how
we
can
solve
these
problems,
some
of
the
first
ones
being
users.
B
You
know,
really
wanted
to
be
able
to
search
across.
You
know
multiple
projects
or
repositories
in
global
search.
Today,
you
can
do
this
by
selecting
a
group,
but
also
sometimes
you
just
want
to
select
just
a
couple
of
those
projects
to
search
within,
and
so
this
will
allow
them
to
do
that,
and
you
know,
as
we
continue
to
to
flush
out
designs
for
this.
B
What
we
do
typically,
is
also
some
solution,
validation
just
to
ensure
that
not
only
do
we
feel
comfortable
with
the
solution
that
we
put
together,
but
it's
actually
we're
ensuring
that
it's
solving
these
needs
and
we'll
do
that
through
some
either
lightweight
evaluative
testing,
where
we'll
actually
do
some
unmoderated
testing
with
users,
or
we
might
even
have
some
sessions
where
we
actually
get
together
with
some
of
our
users
in
person
or
remotely,
I
should
say,
and
actually
have
them
walk
through
different
scenarios
to
actually
validate
some
of
these
designs.
B
Another
issue
that
we're
currently
working
on
is
users
really
want
more
information
related
to
when
a
code
search
result
was
last
modified,
and
so
this
takes
an
effect
like
not
only
like
when
it
was
modified
but
who
what
the
change
was
etc
and
so
go
ahead.
John.
A
Oh,
I
was
going
to
say
let's,
let's
I
wanted
to
dive
into
this
one
just
a
little
bit.
If
that's
okay,
because
you
know,
I
think
this
is
an
important
piece
that
comes
out
of
kind
of
demonstrates
why
the
user
research
is
important
too.
A
So
you
know
when
you,
when
you
think
about
code
search
right
now.
So
when
you
think
about
code
search,
you
think
you
know
you're
just
going
to
be
able
to
search
across
an
example
piece
of
code
right
and
it's
going
to
return
back
any.
You
know
files
that
have
that
example
piece
of
code,
but
this
goes
deeper
into
understanding
why
someone
would
want
to
search
across
an
example,
piece
of
code
right.
B
Yep
yeah,
so
you
know
a
lot
of
times
when
people
are
looking
for
specific.
You
know
snippets
of
code
they're
they're,
not
only
wanting
to
find
that
you
know
specific
code,
but
they
also
want
to
investigate
and
understand
changes
behind
that
code.
And
so
that's
what
this
really
is
is
looking
to
to
dive
into
and
provide
users
is
getting
to
that
information
quicker
and
so
like
we're
looking
at
either.
B
You
know
adding
some
of
this
information
available
within
the
actual
result
listing,
as
well
as
making
it
easier
for
a
user
to
get
from
that
result
to
a
few
things
like
the
blame,
for
instance,
to
see
a
little
bit
more
detailed
information
as
to
the
when
and
the
who,
as
it
relates
to
some
of
those
changes
to
that
specific
code.
A
A
If
you
look
across
a
large
development
organization's
I.t
budget,
it's
it's
not
uncommon,
to
see
a
scenario
where
you
know
somewhere
around
80
of
that
budget
is
spent
on
maintaining
existing
code
or
existing
product
versus
building
a
new
product,
and
when
you
have
that
you,
you
start
to
realize
that
the
majority
of
you
know
code
changes
or
you
know,
maintenancing.
A
That
code
starts
with
the
fact
that
it's
existing
somewhere
and
you
know
trying
to
doubt
trying
to
understand
not
just
the
details
about
where
that
code
exists,
but
then,
maybe
with
blame
as
an
example
to
be
able
to
start
to
reveal
some
of
the
details
about
when
how
why
who
made
it?
What's
the
origin
of
it
can
help
kind
of
you
know
emphasize
the
value
of
that
task.
B
This
one
being
you
know,
adding
labels
as
a
facet
to
advanced
search
so,
as
we
know,
like
a
lot
of
users
today
use
labels
as
a
filtering
method
when
looking
for
things
such
as
issues
and
merge
requests,
and
so
it's
something
that
we
definitely
have
been
wanting
to
add
to
global
search
for
for
quite
a
long
time
and
we're
gonna
be
able
to
do
that
here.
Pretty
soon.
B
You
know
we.
We
have
a
variety
of
additional
facets
that
we're
looking
to
add
in
the
future
as
well
to
these
different
scopes
in
global
search.
But
labels
is
going
to
be
one
of
those
first
ones.
It's
going
to
add
quite
a
bit
of
value
to
users
and
helping
to
narrow
down
the
results
and
find
the
things
that
they're
looking
for.
A
B
B
A
Just
one
of
the
ways
that
you
organize
information
across
get
lab
and
we
we
think
this
is
probably
going
to
end
up
being
one
of
the
most
used,
if
not
the
most
used
facet,
especially
based
on
what
we've
seen
as
we
we've
done.
Some
deeper
analysis
on
how
users
utilize
filtering
by
labels
in,
for
example,
issue
search
the
issue
list
search.
A
So
this
is
some
great
stuff,
so
really
looking
forward
to
the
pieces
that
we're
we're
putting
together
in
14-1,
you
know,
I
think
that
once
we
have
some
of
these
additional
design
pieces
laid
out
that
will
then
get
developed
in
these
upcoming
releases.