docs(#2513): add Jira data leakage warnings for public repository configurations#2518
docs(#2513): add Jira data leakage warnings for public repository configurations#2518fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
…figurations Add documentation warning that connecting private Jira instances to public GitHub repositories risks exposing sensitive customer data via JSONL workflow artifacts. The installation guide now includes a prominent warning, and the private repositories guide has a new section covering the exposure vector, required configuration (private repos), and cross-references to Jira setup issues #2263–#2269 and #1189. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
E2E tests did not runE2E tests run automatically for org/repo members and collaborators on pull requests. For other contributors, a maintainer must add the See E2E testing guide for details. |
Site previewPreview: https://67a62ffb-site.fullsend-ai.workers.dev Commit: |
|
🤖 Finished Review · ✅ Success · Started 4:13 PM UTC · Completed 4:26 PM UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Looks good to me Low-severity findings (11)Low
Labels: PR exclusively modifies user-facing documentation guides with security warnings about Jira data leakage. |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
| - **Intermediate agent reasoning** that quotes or paraphrases Jira content | ||
|
|
||
| See [ADR 0021](../../ADRs/0021-jsonl-reasoning-trace-exposure.md) for the full analysis of JSONL trace exposure vectors. | ||
|
|
There was a problem hiding this comment.
[low] internal-consistency
The reference to ADR 0021 for 'the full analysis of JSONL trace exposure vectors' is slightly imprecise. ADR 0021 analyzes JSONL exposure generally but defers the choice of storage mechanism; it does not specifically cover GitHub Actions artifact downloadability.
|
|
||
| If your org uses per-repo install: | ||
|
|
||
| - The target repository must be **private**. Per-repo install is the recommended mode for private Jira integrations because it keeps all artifacts self-contained. |
There was a problem hiding this comment.
[low] edge-case
The documentation states a private repository is 'the only reliable mitigation,' but ADR 0021 also describes a JSONL suppression mechanism. This is a second viable mitigation not mentioned here.
| Actions tab to see the Fullsend workflow in action. In some minutes the | ||
| `fullsend-ai-triage` bot should post a comment in the issue. | ||
|
|
||
| ## Jira integration: private repository requirement |
There was a problem hiding this comment.
[low] heading-capitalization
The new heading uses sentence case while some existing h2 headings in this file use title case. The file already has mixed capitalization.
|
|
||
| ## Jira integration: private repository requirement | ||
|
|
||
| > **⚠ Warning:** If you plan to connect a **private Jira instance** to this repository, the repository **must be private**. Refinement pipelines produce JSONL workflow artifacts that contain Jira issue content (titles, descriptions, comments, custom fields). In a public repository, these artifacts are downloadable by anyone, exposing private Jira data. See [Private repositories — Private Jira instances and public repositories](../infrastructure/private-repositories.md#private-jira-instances-and-public-repositories) for configuration details and the full risk analysis. |
There was a problem hiding this comment.
[low] admonition-format
The warning uses an emoji prefix which is not used in other admonitions in the documentation guides.
|
|
||
| ## Private Jira instances and public repositories | ||
|
|
||
| > **⚠ Data leakage risk:** Connecting a private Jira instance to a pipeline running in a **public** GitHub repository can expose sensitive customer information. Always use a **private** GitHub repository when processing issues from a private Jira instance. |
There was a problem hiding this comment.
[low] admonition-format
Same emoji prefix inconsistency. The same file's existing admonitions use the format without emoji.
| - **Enable:** all agents | ||
| - **Recommended:** `AGENTS.md` with basic private-repo rules as defense in depth | ||
|
|
||
| ## Private Jira instances and public repositories |
There was a problem hiding this comment.
[low] section-organization
The new Jira section is placed after the sensitivity tier recommendations and before 'See also.' Consider whether it fits better earlier in the document flow.
|
|
||
| ## Private Jira instances and public repositories | ||
|
|
||
| > **⚠ Data leakage risk:** Connecting a private Jira instance to a pipeline running in a **public** GitHub repository can expose sensitive customer information. Always use a **private** GitHub repository when processing issues from a private Jira instance. |
There was a problem hiding this comment.
[low] architectural-misalignment
ADR 0021 addresses JSONL exposure generally, not Jira-specific scenarios. Referencing it as the full analysis for this specific vector slightly misrepresents its scope.
fullsend-ai-review
Bot
added
ready-for-merge
Add documentation warning that connecting private Jira instances to public GitHub repositories risks exposing sensitive customer data via JSONL workflow artifacts. The installation guide now includes a prominent warning, and the private repositories guide has a new section covering the exposure vector, required configuration (private repos), and cross-references to Jira setup issues #2263–#2269 and #1189.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Closes #2513
Post-script verification
agent/2513-jira-data-leakage-docs)619c19d688c0aa3c25af0be4fd8b07cbc8099241..HEAD)