Advanced Jira issue search supporting structured filters and raw JQL. At least one filter parameter (e.g., jql, project_key, updated_after) is required; calls with no parameters will be rejected.
Raw JQL (Jira Query Language) query for advanced users. Takes precedence over filters. Can be a complete JQL query with filters and/or ORDER BY clause, or just an ORDER BY clause. CRITICAL JQL SYNTAX RULES - Every comparison needs field + operator + value: (1) WRONG: '("val1" OR…
fieldsarray
List of fields to return for each issue (for example: summary, status, assignee). If omitted, a sensible default set is requested to populate common fields.
labelsarray
Filter by labels (all labels must match).
assigneestring
Filter by assignee. Can be account ID (e.g., '712020:abc...'), email (e.g., 'john@company.com'), display name (e.g., 'John Doe'), or 'unassigned'.
max_resultsinteger
Maximum number of issues to return per page. Capped at 100 per page; total results per JQL query capped at ~10,000. Use next_page_token to paginate.
project_keystring
Filter by project key (e.g., 'PROJ').
text_searchstring
Search in summary and description text.
created_afterstring
Filter issues created after this date. Supports YYYY-MM-DD format or relative dates like '-30m' (last 30 minutes), '-7d' (last 7 days), '-1w' (last week), '-1M' (last month).
updated_afterstring
Filter issues updated after this date. Supports YYYY-MM-DD format or relative dates like '-30m' (last 30 minutes), '-7d' (last 7 days), '-1w' (last week), '-1M' (last month).
created_beforestring
Filter issues created before this date (YYYY-MM-DD format).
updated_beforestring
Filter issues updated before this date (YYYY-MM-DD format).
next_page_tokenstring
Cursor token used to fetch the next page when using enhanced search.
Observable output
data
Required
Data from the action execution
errorstring
Error if any occurred during the execution of the action
successfulboolean
Required
Whether or not the action execution was successful or not