@kapa.ai Is there a known issue with the jira connector where the projects stream returns 0 records because the connector sends a malformed

status

parameter (

"['live', 'archived', 'deleted']"

) to

/rest/api/3/project/search

and Jira returns a 400 that the error handler silently ignores?

This is a plausible failure mode based on what the knowledge sources reveal, but it is not explicitly documented as a known/confirmed bug. Here's what the sources do tell us: What the Knowledge Sources Confirm 1. The

status

parameter encoding is acknowledged as tricky. The unit test for the projects stream explicitly notes: > "Using

with_any_query_params()

because the CDK's

HttpRequest

matcher requires exact parameter matching, and the status parameter encoding varies." [test_projects.py] This means the connector developers themselves recognized that the

status

parameter encoding is non-trivial and worked around it in tests rather than asserting the exact encoded value. 2. The connector globally silently ignores all HTTP 400 responses. From the CONTRIBUTING.md: > "The base error handler for source-jira silently ignores ALL HTTP 400 (Bad Request) responses across every stream. This means any malformed request, invalid JQL query, unsupported field, or missing parameter will produce zero records for that request rather than raising an error." [CONTRIBUTING.md] This is confirmed by unit tests for the projects stream specifically — a 400 response results in 0 records and no ERROR logs. [test_projects.py] 3. The manifest sends

status=['live', 'archived', 'deleted']

as static parameters. The conftest fixture shows the expected URL includes

status=live&status=archived&status=deleted

(repeated params), not a stringified list: [conftest.py]

/rest/api/3/project/search?maxResults=50&expand=description%2Clead&status=live&status=archived&status=deleted

Summary The scenario you describe — a malformed

status

parameter causing a 400 that is silently swallowed — is mechanically possible given the connector's design: • The

status

encoding is acknowledged as variable/tricky. • A 400 from

/rest/api/3/project/search

would silently produce 0 records with no error logged. • The CONTRIBUTING.md explicitly warns that this silent 400 suppression makes missing data hard to debug. However, the knowledge sources do not explicitly document this as a confirmed, filed bug. If you are seeing 0 records from the projects stream, the recommended debugging approach (per the CONTRIBUTING.md) is to inspect the actual API request being sent and the raw Jira API response directly, since the connector will not surface the error in logs. [CONTRIBUTING.md] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.