List saved queries
list_queriesList saved OpenProject work-package views (queries) for the current user, enabling discovery of existing team boards and filters before building custom ones.
Instructions
List the saved work-package views (queries) this user can open.
Use it to discover what a team already tracks — "Sprint board", "My open bugs",
"Overdue in Platform" — before hand-building filters: running someone's saved view
with run_query reproduces exactly what they see in the UI, including their
grouping and sums.
Returns the standard list envelope: rows of {id, name, project, public, starred, updated_at} plus pagination. project is null for a global query (saved outside
any project); public false means the query is private to its owner, and only the
owner's queries are visible to this account.
Pitfalls. Query ids are instance-wide, not per project — never guess one, take it from here. This lists definitions only; it never runs them, so nothing here says how many work packages a query returns.
Cross-references: run one with run_query(query_id=…); build an ad-hoc query
instead with list_work_packages; project ids come from list_projects.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | 1-based page number. | |
| page_size | No | Queries per page (max 100). | |
| project_id | No | Numeric project id to list only that project's saved views. Comes from list_projects. Omit to list everything visible to the current user, global queries included. A project identifier (URL slug) is not accepted here by OpenProject — use the numeric id. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sums | No | Present only when show_sums was requested. | |
| items | No | The page of results. | |
| notes | No | Degradation markers: capped aggregations, unavailable modules, … | |
| groups | No | Present only when group_by was requested. | |
| pagination | Yes | Total/page/page_size/has_more. |