Filter query language

Use the filter query language in command search and saved views.

Queries combine plain text with key:value tokens. Tixio pulls out recognized tokens and searches the remaining text normally.

project:tixi status:in_progress assigned_to:me label:docs

Syntax rules

Use one space between tokens.

Quote values with spaces:

assigned_to:"John Smith" cycle:"Sprint 26"

Use | or , for OR within one key:

priority:high|urgent status:backlog,todo

Repeat a key to OR values:

priority:high priority:low

Unknown tokens are treated as plain-text search. Saved view creation can show a warning when a token looks like a filter but does not parse.

Common examples

assigned_to:me status:in_progress
created_by:me created_at:this_week
project:web|api label:customer-request
cycle:current hide_done:1
type:bug priority:high|urgent estimated:false
due:overdue assigned_to:none

Supported tokens

Token	Values	Example
`type`	`bug`, `task`, `story`, `epic`	`type:bug`
`priority`	`no_priority`, `low`, `medium`, `high`, `urgent`	`priority:high\|urgent`
`status`	Project status key	`status:todo\|in_progress`
`assigned_to`	`me`, `none`, user name, handle, UUID	`assigned_to:me`
`assignee`	Alias for `assigned_to`	`assignee:none`
`created_by`	`me`, user name, handle, UUID	`created_by:me`
`creator`	Alias for `created_by`	`creator:"John Smith"`
`created_at`	`today`, `yesterday`, `this_week`	`created_at:this_week`
`created`	`me`, `today`, `yesterday`, `this_week`	`created:me`
`project`	Project slug, key, or UUID	`project:tixi\|web`
`cycle`	`current`, `active`, `past`, `none`, cycle name, UUID	`cycle:current`
`epic`	Epic key, UUID, or `none`	`epic:TIXI-111`
`milestone`	Milestone UUID or `none`	`milestone:none`
`label`	Label name, UUID, or `none`	`label:customer-request`
`cf:<fieldId>`	Custom field value, `__empty__`, or `__not_empty__`	`cf:2f4d8f4f-0a6d-4c4f-bf8f-0b7e2f5d4a11=__not_empty__`
`fix_version`	Version name, UUID, or `none`	`fix_version:v1.2`
`affects_version`	Version name, UUID, or `none`	`affects_version:v1.1`
`version`	Version name, UUID, or `none`; matches fix or affects version	`version:v1.2`
`resolution`	Resolution key	`resolution:wont_fix`
`due`	`overdue`, `today`, `this_week`, `none`	`due:overdue`
`estimated`	`true`, `false`	`estimated:false`
`estimate`	`sized`, `none`	`estimate:sized`
`is`	`open`, `overdue`	`is:open`
`hide_done`	`1` or `0`	`hide_done:1`
`hide_subtasks`	`1`	`hide_subtasks:1`
`group_subtasks`	`1`	`group_subtasks:1`

Project and status tokens

Use project: when a query needs project-specific context.

Status keys are project-specific. A query such as status:in_progress is most reliable when paired with a project:

project:tixi status:in_progress

Cross-project status queries can work when the named status keys exist in the target projects, but status meanings and custom workflow names can differ by project.

Cycle tokens

Use:

cycle:current or cycle:active for the current active cycle.
cycle:past for past cycles.
cycle:none for work with no cycle.
cycle:"Sprint 26" when the cycle name is unique in the project.

Cycle names need project context when they could be ambiguous:

project:tixi cycle:"Sprint 26"

Assignment tokens

Use assigned_to:me for work assigned to you.

Use assigned_to:none for unassigned work.

Use names when they are unambiguous:

assigned_to:"John Smith"

If two people share a name, use a handle or UUID.

Labels

Use label names:

label:docs
label:"customer request"

Use label:none for unlabeled issues.

Without a project: token, label matching uses the workspace label catalog so a label name can match across projects.

Custom fields

Custom field filters use the field UUID as part of the token:

cf:2f4d8f4f-0a6d-4c4f-bf8f-0b7e2f5d4a11=__not_empty__
cf:2f4d8f4f-0a6d-4c4f-bf8f-0b7e2f5d4a11=gold

The value is interpreted using the field's type:

Short text matches text.
Number matches numeric values.
Date matches YYYY-MM-DD values.
Single select matches an option value.
User matches a user value.

Use __empty__ to find issues with no value for a field. Use __not_empty__ to find issues where the field has any value.

Custom field filters are project-specific because field definitions belong to a project. Pair them with project: when the current view is not already scoped to one project.

Versions

Use fix_version: to find work planned for or fixed in a release.

Use affects_version: to find bugs or issues observed in a release.

Use version: when either relationship should match.

fix_version:v1.2
affects_version:v1.1
version:none

Use version UUIDs when names are ambiguous.

Dates and estimates

Use created_at: for issue creation windows:

created_at:today
created_at:yesterday
created_at:this_week

Use due: for due date state:

due:overdue
due:today
due:this_week
due:none

Use either estimate token:

estimated:true
estimated:false
estimate:sized
estimate:none

Display tokens

Saved views show done issues by default. Add hide_done:1 to hide completed and cancelled work.

Use hide_subtasks:1 to hide sub-tasks. Use group_subtasks:1 to show sub-tasks nested under their parent on surfaces that support grouping.

Order By

Saved views store Order By separately from the query text. Available orders include:

Created, earliest to latest or latest to earliest.
Modified, earliest to latest or latest to earliest.
Priority, low to high or high to low.
Title, A to Z or Z to A.
Due date, closest to latest or latest to closest.
Status, A to Z or Z to A.
Type, bug to epic or epic to bug.
Manual.

When a saved view opens on list, board, or table, Tixio maps Order By to that surface's sort controls when the surface supports it.

Troubleshooting

If a saved view opens as a flat view instead of a project surface, check whether the query has exactly one resolvable project: token. Multi-project board and table views can open across projects; list, calendar, and timeline need one project.

If a status or label warning appears, add project: so Tixio can validate the value against the right project catalog.