Files
codex-security/docs/plugin-connectors.md
T
Michael D'AngeloandCodex dae9d40746 feat(publish)!: share issue receipts with finding tracking (#1426)
* feat!: share finding issue receipts across publication and tracking

* fix(tracking): recover issue receipts after plugin restart

* fix(tracking): recover stored history before initial writes

* fix(tracking): preserve fallback for inaccessible primary stores

* fix(tracking): defer inaccessible receipt stores to SQLite

* refactor: derive publication membership from the sealed scan

* Preserve accepted receipt URLs and complete receipt diagnostics

* Index finding issue ownership checks without rewriting migrations

* test(deep-scan): isolate the Node capability bundle probe

* test(package): adapt Deep Scan fixture to direct engine

* fix(tracking): allow full-scan receipt work to complete

---------

Co-authored-by: Codex <codex@users.noreply.github.com>
2026-10-17 04:58:04 +09:00

2.4 KiB

Plugin connectors

Codex Security uses optional connected apps for ticket intake and finding tracking. Their identities are declared in plugins/codex-security/.app.json.

App Workflows
Linear Ticket intake and finding tracking
GitHub Finding intake, source lookup, and issue tracking
Atlassian Jira Cloud ticket intake and finding tracking

Finding tracking and CLI publication share issue associations when they use the same local state directory, including reuse across scan occurrences. The tracking skill reads them with get_codex_security_finding_issues and records accepted writes or verified reuse with record_codex_security_finding_issues. Provider reads still confirm saved candidates and search for unrecorded duplicates. Accepted writes remain recorded even when follow-up reads fail. The tools accept sealed scan bundles without requiring their original local scan history and keep receipts outside those bundles.

Jira setup

Connect the Atlassian app in the app directory. Existing Atlassian Rovo (Legacy) connections do not connect the new app; authorize it separately with the intended account and site.

Intake and duplicate checks need read and search access. Creating or updating issues also needs write access. Before creating an issue, the tracking skill resolves the project, issue type, and required fields.

Use the app's live schemas and discover deferred operations when needed. See Atlassian's supported tools and the skill's Jira workflow.

QA

Test the plugin build with synthetic findings in a selected QA project:

  • Verify that Jira calls use the new Atlassian app and the selected account and site.
  • Read a synthetic issue directly and through project-scoped JQL, including pagination.
  • Create one issue, reuse it without creating a duplicate, and update approved fields. Verify each write by reading the issue back.
  • Verify that missing connections and insufficient access produce recovery guidance without duplicate creates.

Record live results separately from static checks. Keep account and project details, issue keys, and raw tool responses out of public PRs.