Hi @greengil,

As of now, the Jira connector doesn’t support passing an arbitrary Jira JQL. The only source-side filtering it exposes is by project/space via connector_options.jira_options.include_jira_spaces (using project keys), and then you do any finer-grained filtering (status, dates, etc.) downstream in Databricks.

That project filter is applied per table. If you include_jira_spaces only on the issues table, issues will be pruned to those projects, but other tables (components, custom fields, users, etc.) will still be read according to their own settings, which, by default, means "all available data" for that table.

If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.