Advanced search

  • Tier: Premium, Ultimate
  • Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated

Use advanced search to find exactly what you need across your entire GitLab instance.

With advanced search:

  • Identify code patterns across all projects to refactor shared components more efficiently.
  • Locate security vulnerabilities across your entire organization’s codebase and dependencies.
  • Track usage of deprecated functions or libraries throughout all repositories.
  • Find discussions buried in issues, merge requests, or comments.
  • Discover existing solutions instead of reinventing functionality that already exists.

Advanced search works in:

  • Code
  • Comments
  • Commits
  • Groups
  • Work items
  • Merge requests
  • Milestones
  • Projects
  • Users
  • Wikis

Prerequisites:

  • Advanced search must be enabled:
    • For GitLab.com and GitLab Dedicated, advanced search is enabled by default in paid subscriptions.
    • For GitLab Self-Managed, an administrator must enable advanced search.

To use advanced search:

  1. In the top bar, select Search or go to.
  2. In the search box, enter your search term.

You can also use advanced search in a project or group.

Available scopes

The availability of group milestones in milestone results is controlled by a feature flag. For more information, see the history.

Scopes describe the type of data you’re searching. The following scopes are available for advanced search:

ScopeGlobal1, 2GroupProject
Codecheck-smcheck-smcheck-sm
Commentscheck-smcheck-smcheck-sm
Commitscheck-smcheck-smcheck-sm
Groups3check-smcheck-smNo
Work items4check-smcheck-smcheck-sm
Merge requests4check-smcheck-smcheck-sm
Milestones5check-smcheck-smcheck-sm
Projectscheck-smcheck-smNo
Userscheck-smcheck-smcheck-sm
Wikischeck-smcheck-smcheck-sm

Filter merge request search results

When you search merge requests, you can filter the results with URL parameters. For example, to return only merge requests that are assigned to the users with IDs 5 and 7:

https://gitlab.example.com/search?scope=merge_requests&search=cache&assignee_ids[]=5&assignee_ids[]=7

The following parameters are available:

ParameterDescription
assignee_ids[]Filter by assignee ID. When you specify more than one ID, only merge requests assigned to all of those users are returned. You can specify a maximum of 20 IDs.
author_usernameFilter by the username of the merge request author.
created_afterFilter by merge requests created on or after the given date and time.
created_beforeFilter by merge requests created on or before the given date and time.
source_branchFilter by source branch name.
target_branchFilter by target branch name.
updated_afterFilter by merge requests updated on or after the given date and time.
updated_beforeFilter by merge requests updated on or before the given date and time.

Dates must be one of these formats:

  • A date only, for example 2026-01-31. A date-only value is treated as the start of that day (00:00), so created_before=2026-01-31 excludes merge requests created later that same day.
  • A full ISO 8601 datetime with seconds, for example 2026-01-31T09:00:00Z.

When advanced search is not available, only created_after and created_before are applied. The other parameters are ignored.

To exclude results instead, use the not[] form of a parameter. The following parameters support exclusion: assignee_ids, author_username, source_branch, and target_branch. For example, to return merge requests that are not authored by alice:

https://gitlab.example.com/search?scope=merge_requests&search=cache&not[author_username]=alice

Syntax

Advanced search uses simple_query_string, which supports both exact and fuzzy queries.

When you search for a user, the fuzzy query is used by default. You can refine user search with simple_query_string.

SyntaxDescriptionExample
"Exact search"gem sidekiq"
~Fuzzy searchJ~ Doe
|Ordisplay | banner
+Anddisplay +banner
-Excludedisplay -banner
*Partialbug error 50*
\Escape\*md
#Issue ID#23456
!Merge request ID!23456
SyntaxDescriptionExample
filename:Filenamefilename:*spec.rb
path:Repository location (full or partial matches)path:spec/workers/
extension:File extension without . (exact matches only)extension:js
blob:Git object ID (exact matches only)blob:998707*

Examples

QueryDescription
rails -filename:gemfile.lockReturns rails in all files except the gemfile.lock file.
RSpec.describe Resolvers -*builderReturns RSpec.describe Resolvers that does not start with builder.
bug | (display +banner)Returns bug or both display and banner.
helper -extension:yml -extension:jsReturns helper in all files except files with a .yml or .js extension.
helper path:lib/gitReturns helper in all files with a lib/git* path (for example, spec/lib/gitlab).

Known issues

  • You can search only files smaller than 1 MB. For GitLab Self-Managed, an administrator can set a limit on the maximum file size indexed.

  • You can use advanced search only on the default branch of a project. For more information, see issue 229966.

  • The search query must not contain any of the following characters:

    . , : ; / ` ' = ? $ & ^ | < > ( ) { } [ ] @
  • Search results show only the first match in a file.


  1. An administrator can disable global search scopes. On GitLab Self-Managed, global search is not available when limited indexing is enabled by default. An administrator can enable global search for limited indexing. ↩︎

  2. On GitLab.com, global search is not enabled for code, commits, and wikis. ↩︎

  3. Group search returns the subgroups of the group you’re searching in, not the group itself. The backfill_groups_to_elasticsearch advanced search migration must be complete before this scope returns results. ↩︎

  4. When you search work items and merge requests, results include comments that match your search term. ↩︎ ↩︎

  5. When the advanced_search_group_milestones feature flag is enabled, advanced search also returns group milestones that you can view. Global search returns group milestones from all groups you can view, and project milestones. Group search returns milestones of the group, its parent groups, and its subgroups, and milestones of projects in the group and its subgroups. Project search returns milestones of the project, its group, and the parent groups of that group. When the feature flag is disabled, advanced search returns only project milestones. Group milestones created before indexing was available appear after a backfill runs. ↩︎