Skip to main content
Redmine’s search finds content across all major resource types. You can scope a search to the current project, a project’s subprojects, your own projects, your bookmarked projects, or all projects globally.
1

Open search

Click the search box in the top navigation bar, or press the shortcut key if configured. Alternatively, go to /search.
2

Enter a query

Type one or more keywords. By default, all words must be present in the results (all words mode).
3

Select the scope

Choose how broadly to search:
  • This project — current project only
  • This project and subprojects — includes all descendant projects
  • My projects — all projects you are a member of
  • My bookmarks — projects you have bookmarked
  • All projects — all projects visible to you
4

Choose content types

Check or uncheck the content types to include in the results.
5

Apply options and search

Adjust search options and click Search.
If you type a number (or # followed by a number) in the search box, Redmine redirects you directly to the issue with that ID, bypassing the search results page.

​
Search scope

ScopeDescription
This projectSearches only within the currently open project.
This project and subprojectsIncludes the current project and all its descendants.
My projectsAll projects where you are a member.
My bookmarksProjects you have starred or bookmarked.
All projectsEvery project visible to you (including public projects).
When searching within a specific project, the Projects content type is removed from the scope automatically, since you are already inside a project.

​
Searchable content types

Redmine indexes the following content types:
Content typeFields searched
IssuesSubject, description
NewsTitle, summary, description
DocumentsTitle, description
ChangesetsComments/commit messages
Wiki pagesTitle, body text
Messages (forums)Subject, content
ProjectsName, identifier, description
You can restrict the search to only certain content types by checking the corresponding boxes on the search page.

​
Search options

When enabled (the default), results must contain all search terms. Disable this option to return results that contain any of the terms.
When enabled, only the title or subject field is searched, not the body content. Useful for finding a specific issue or page by its exact name.
When enabled, the file names of attachments are included in the search. Note that file contents are not indexed — only the attachment file name is matched.
When enabled for an issues search, only issues with a non-closed status are returned.

​
Understanding results

Results are grouped by content type and sorted by relevance. Each result shows:
  • Type icon — identifies whether the result is an issue, wiki page, news item, etc.
  • Title or subject — links to the resource
  • Project name — the project the resource belongs to
  • Date — the creation or last-updated date
  • Excerpt — a snippet of matching content with search terms highlighted

​
Pagination

Results are paginated. The number of results per page is controlled by Administration → Settings → Results per page (default: 10). For API requests, pagination uses the standard offset and limit parameters.

​
Searching via the API

The search endpoint is available at GET /search.json (or .xml) with the same query parameters: 
GET /search.json?q=login+error&issues=1&open_issues=1&scope=my_projects
See the REST API documentation for full parameter details.
Save frequently used searches as Saved queries on the Issues list page if you regularly filter issues by the same criteria. Saved queries are faster and more predictable than free-text search for structured data.

​
Permissions

Search results are filtered by your project membership and permissions. You only see resources you are allowed to view:
  • Issues respect the view_issues permission and the issue’s is_private flag.
  • Wiki pages require view_wiki_pages.
  • News requires view_news.
  • Forum messages require view_messages.
  • Documents require view_documents.
  • Changesets require view_changesets.