Open-source AI Security Operations Center: alert fusion, LLM-agent triage, MITRE ATT&CK investigation, and a replayable decision ledger for every agent step. Self-hostable, runs with no API keys, MIT licensed. Ships an MCP server for Claude, Cursor and Continue.
Python agentic-aiai-securityalert-triageblue-teamcybersecuritydetection-engineeringincident-responselanggraphllm-agentsmcpmitre-attackmodel-context-protocolpurple-teamsecurity-operationsself-hostedsiemsoarsocthreat-detectionthreat-intelligence
fix(connectors): move Jira issue pull to /rest/api/3/search/jql (#1524)
Agustin Torres3164fb54343f
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex b55a6af9f..fbb4d52f0 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0### Fixed+- The Jira connector pulls issues from `GET /rest/api/3/search/jql`. Jira+ Cloud removed `GET /rest/api/3/search` (it now answers 410 Gone), which left+ the connector's alert pull failing on every poll. The request already names+ the fields `normalize()` reads, so the issue shape it receives is unchanged.- **The image `stable` channel guard read the registry through a buildxtemplate, and when the runner's buildx stopped resolving it the guardfailed open** — the read returned empty with stderr discarded, "empty" wasdiff --git a/services/connectors/app/connectors/jira_connector.py b/services/connectors/app/connectors/jira_connector.pyindex 9e3272b41..464bd7ad2 100644--- a/services/connectors/app/connectors/jira_connector.py+++ b/services/connectors/app/connectors/jira_connector.py@@ -143,7 +143,7 @@ class JiraConnector(BaseConnector):async with httpx.AsyncClient(timeout=30.0) as client:resp = await client.get(- f"{self._base_url}/rest/api/3/search",+ f"{self._base_url}/rest/api/3/search/jql",headers=self._auth_header(),params={"jql": jql,