Component

CDK Jira adapter, attachment screening, agent context

Describe the feature

Jira-origin tasks should include the same practical issue context that Linear-origin tasks can use: attached files and relevant comments, not only the issue summary and description.

Current Jira task creation converts the issue summary/description and extracts embedded HTTPS image URLs. It explicitly skips Jira media file attachments because those require a Jira REST lookup/download, and it does not include issue comments. That means logs, screenshots, PDFs, specs, and clarifications attached to the Jira ticket can be invisible to the agent.

Use case

A Jira ticket often says “see attached log,” “use the attached screenshot,” or contains acceptance clarifications in comments. If ABCA only sees the title and description, it may implement the wrong thing or stop to ask for context that was already on the ticket.

Proposed solution

Add authenticated Jira context enrichment during task admission:

• After the Jira webhook is verified and tenant OAuth is resolved, fetch the full Jira issue context needed for the task through Jira REST.
• Include recent human comments in the task description, with clear attribution and ordering.
• Resolve Jira file attachments through the REST API rather than relying on unauthenticated URLs.
• Route downloaded attachment content through the existing ABCA attachment validation and Bedrock Guardrail screening path before it reaches the agent.
• Preserve existing limits: max attachment count, max size, supported MIME types, and fail-closed behavior for blocked or unscreenable content.
• If Jira context fetch fails for optional comments, proceed with a warning; if an attachment is selected for inclusion but cannot be safely fetched/screened, reject the task with a clear Jira comment.
• Document which Jira attachment types are supported.

Acceptance criteria

• Jira issues with supported file attachments pass those attachments to the agent after security screening.
• Jira issues with recent comments include those comments in the task context.
• Unsupported, too-large, blocked, or unscreenable attachments do not reach the agent.
• Jira REST/auth failures are logged clearly and produce operator-visible feedback when they prevent task creation.
• Existing embedded image URL extraction from the description continues to work.
• Linear, Slack, API, and GitHub-context behavior are unaffected.

Tests

• Jira webhook processor tests cover fetching comments, selecting supported attachments, skipping unsupported attachments, and task payload construction.
• Attachment screening tests cover authenticated Jira downloads flowing through the existing screening pipeline.
• Failure tests cover blocked attachments, oversized attachments, REST auth failures, and optional-comment fetch failures.
• Docs update JIRA_SETUP_GUIDE.md with supported attachment/comment behavior and limits.

Out of scope

• Atlassian Remote MCP support.
• Jira project documents/Confluence pages.
• Fetching every historical comment on long-running issues.
• Agent-side unauthenticated download of Jira attachment URLs.
• New attachment limits or new file type support beyond what ABCA already screens.