--- title: "Advanced Search and Work Item Query Language | Orangescrum" description: "Find work items with a structured query language. Filter by status, assignee, sprint, custom fields, and change history, then save the query and re-run it." canonical: https://www.orangescrum.com/advanced-search --- # Advanced Search and Work Item Query Language | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Advanced Search Advanced search # Advanced Search With a _Real Query Language_ Some questions are too specific for a filter panel. Type the question instead, get the exact set of work items back, and save the query so you can run it again next week. Available inCloud[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Explore Self-Hosted →](/self-hosted)[Book a Demo](https://calendly.com/orangescrum) Available in the Self-Hosted edition - runs on your own servers This capability is available in the **Self-Hosted (on-premise)** edition. It is not part of the Cloud edition today. ## What is a work item query language? A work item query language lets you describe the set of tasks you want as a short piece of text rather than by clicking through filter menus. Orangescrum reads a query such as status = "In Progress" AND assignee = currentUser(), turns it into a scoped database query, and returns the matching work items. Queries can combine fields with AND, OR, and NOT, sort with ORDER BY, and be saved and re-run like any other filter. The problem ## Why filter panels _run out of room_ The question has too many parts High priority bugs, not mine, still open, in this sprint, over five points. ✓ One query expresses all of it, including OR and NOT. The same search gets rebuilt weekly Every stand-up someone clicks the same eight filters again. ✓ Save the query once and re-run it. Your own fields are not searchable You added a custom field, then could not filter by it properly. ✓ Custom fields are queryable with cf\["Field Name"\]. What you get ## Ask for _exactly the set you want_ A small, documented grammar over the work item fields you already use, scoped to what you are allowed to see. - ### A documented grammar Combine predicates with AND, OR, NOT, and brackets, then sort with ORDER BY. For example: type = Bug AND priority IN (High, Medium) ORDER BY created DESC. - ### Operators that fit the field Use =, !=, >, >=, <, <=, IN, NOT IN, IS EMPTY, ~ for contains, and ~~ for a typo tolerant match. Each field allows only the operators that make sense for it. - ### The fields you actually work with Query status, type, priority, assignee, reporter, labels, sprint, project, story points, estimated hours, due date, and created date, with friendly aliases for each. - ### Your custom fields Reference a custom field by name or by id, such as cf\["Risk Level"\] = High, so the data you added is as searchable as the built in fields. - ### Change history Ask what changed, not just what is true now. status\_changed\_to = "Closed", priority\_was = "High", and status\_changed\_on >= 2026-01-01 all work. - ### Saved queries Save a query with a name and run it again later. Saved queries sit alongside your existing saved filters. How it works ## How it _works_ 1 Open Advanced Search The Advanced Search page sits in the left navigation. 2 Type the question Write the query. Validation runs as you go and points at the exact character it could not read. 3 Read the results Matching work items come back paginated, scoped to your company, your projects, and your permissions. 4 Save it Give the query a name so you or your team can run it again without rebuilding it. Who it's for ## Useful when _the question is specific_ Delivery leads Everything unassigned in the current sprint, sorted by points, in one line. [Learn more →](/agile-project-management) QA and support High priority defects raised by someone else that are still not closed. [Learn more →](/bug-and-issue-tracking) Regulated teams Evidence questions about what moved to Closed and when, on your own servers. [Learn more →](/self-hosted) Availability ## Which edition includes _what_ Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes. Saved filters are in every edition. The query language is Self-Hosted. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Saved filters and point and click filtering | ✓ | ✓ | ✓ | | Structured query language | ✗ | ✓ | ✗ | | Saved and re-runnable queries | ✗ | ✓ | ✗ | | Custom fields in queries | ✗ | ✓ | ✗ | | Change history in queries | ✗ | ✓ | ✗ | | Typo tolerant matching | ✗ | ✓ | ✗ | Frequently asked questions ## Advanced search _FAQ_ ### Does Orangescrum have an advanced search? Yes. The Self-Hosted edition includes an Advanced Search page with a structured query language, so you can describe the set of work items you want as text instead of clicking through filter menus. ### Is advanced search available in Cloud? No. The query language is in the Self-Hosted edition only. Cloud and the free Community Edition both include saved filters and point and click filtering, but not the query language. ### What does a query look like? A query is a list of conditions joined by AND, OR, and NOT, with an optional sort. For example: status = "In Progress" AND assignee = currentUser() ORDER BY due\_date ASC, or sprint IS EMPTY AND story\_point >= 5. ### Which fields can I search on? Title, description, work item key, status, type, priority, assignee, reporter, labels, sprint, project, story points, estimated hours, due date, and created date. Common aliases such as assigned\_to, points, and milestone resolve to the right field. ### Can I query my custom fields? Yes. Reference a custom field by name or by id, for example cf\["Risk Level"\] = High. Exact matches and substring matches are both supported. ### Can I search on what changed rather than what is true now? Yes. Change history fields let you ask questions such as status\_changed\_to = "Closed", priority\_was = "High", or status\_changed\_on >= 2026-01-01. ### Can I save a query and run it again? Yes. A saved query is stored with your existing saved filters and is scoped to you and your organisation, so it reloads and can be shared the same way. ### Will a query show me work I should not see? No. Every query runs inside the same scope as your normal task list, which covers your organisation, your project membership, and your view permissions. Values you type are bound as parameters, and field names come from a fixed catalogue rather than from your input. ## Ask harder questions of your work items Advanced Search is included in the Orangescrum Self-Hosted edition, running entirely on your own infrastructure. [Explore Self-Hosted →](/self-hosted)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [Custom fieldsAdd the data you want to query](/custom-fields)[Task managementEverything about tasks](/task-management)[Advanced reportingReport on what you find](/advanced-reporting)[Self-Hosted editionRun Orangescrum on your own servers](/self-hosted)