Saved filters & JQL

ActionConnect includes a JQL-style query language for finding work items and tickets, and lets you save any query as a reusable, optionally shared filter.

Querying with JQL

A query is one or more field operator value clauses joined by a single combinator — AND or OR. For example:

status = todo AND assignee = me
points >= 3 AND due < 2025-02-01
title ~ login OR status != done

Queries run against the same underlying data as every view — a query only narrows which rows you see. You can type a query ad-hoc to search, or attach it to a saved view so the view always shows the matching set.

NOTE

A query uses one combinator throughout. Mix AND clauses or OR clauses, but not both in the same query — split mixed logic into two saved filters instead. There is no IN (...) operator; use OR to list alternatives (status = open OR status = pending).

Operators

Operator	Meaning	Example
=	equals (loose: "3" matches 3)	status = open
!=	not equal	status != done
>	greater than (numbers / dates)	points > 5
<	less than (numbers / dates)	due < 2025-12-31
>=	greater than or equal	points >= 3
<=	less than or equal	due <= 2025-06-30
~	contains, case-insensitive (text)	title ~ login

Values

• Barewords — unquoted single tokens: status = open.
• Quoted strings — wrap values containing spaces in single or double quotes: title ~ "login error".
• Numbers — bare numerics are compared numerically: points >= 3.
• Dates — YYYY-MM-DD is interpreted as a calendar date (midnight UTC) and compared chronologically: due < 2025-02-01.

Fields

You can query any column on the row, plus these friendly aliases for tasks:

Alias	Maps to
status	item status
assignee	assigned user id
points	story points
due	due date
start	start date
type	item type
sprint	sprint
epic	epic
title	title
project	project

TIP

A malformed clause (missing field, operator, or value) is rejected when you type or save the query — not silently ignored.

Saving a filter

Save a query under a name to reuse it. A saved filter has:

• a name,
• the query itself,
• an entity type (task or ticket), and
• a shared flag, so you can keep a filter private or share it with the team.

Saved filters are validated when you create them — an invalid query is rejected up front, not when it next runs.

Using a filter in a view

Any saved view can reference a saved filter (or carry an inline query). When the view renders, ActionConnect applies the filter to scope the rows — so a Board, Table, or List view can be pinned to "my open high-priority items" or any other saved query. See Views.

Tips

• Save the queries you run often; share the ones the whole team relies on.
• Combine a filter with a Board view to make a focused, query-driven board.
• Keep queries narrow with AND clauses; widen with OR only when needed.
• For free-text search across tickets, tasks, KB, and contacts at once, use Global search instead of a field-scoped JQL query.