Jira
Jira
Scan Jira issues, comments, links, and attachments.
- Category
- Collaboration
- Source type
- JIRA
- Produces
- issueattachmentcomments
Tickets accumulate everything: production logs pasted into a description, customer details in a bug report, a database dump attached “for reproduction”. Jira is a rich source precisely because people paste into it without thinking.
What you need to connect
Your Jira Cloud URL, the account email, and an API token.
Shared behaviour · Atlassian Cloud
Authentication is your Atlassian account email plus an API token — the same token type across Jira and every other Atlassian product. The account only ever needs read access, and it sees exactly what that account would see in the browser: nothing is escalated, so restricted spaces and projects stay invisible unless the account is entitled to them.
Attachments are scanned, not skipped. Each attached file becomes an asset of its own, linked back to the page or issue it came from, and is read with the full file-format pipeline — which is where the interesting material usually is.
What Classifyre reads
- Issues — summary and description.
- Comments — gathered into one comments asset per issue.
- Attachments — each attached file as its own asset, linked to its issue.
Scope by project key or id, and narrow further with JQL — which lets you
target exactly what you care about (created >= -90d, a label, a component, a
custom field).
Issue attachments are read with the shared file pipeline: see Supported File Formats for everything it can open, and OCR & Transcription for reading text out of images, audio and video.
Metadata on every asset
Asset kind · issue
| Field | Type | Always present | What it is |
|---|---|---|---|
| issue_key | string | Yes | Jira issue key |
| links_count | integer | Yes | Number of linked or related assets |
| issue_type | string | No | Issue type |
| priority | string | No | Priority |
| project_key | string | No | Project key |
| assignee | string | No | Assignee display name/email |
| author | string | No | Reporter display name/email |
| status | string | No | Current status |
| tags | string[] | No | Labels |
Asset kind · attachment
| Field | Type | Always present | What it is |
|---|---|---|---|
| filename | string | Yes | Original file name |
| mime_type | string | No | MIME type |
| size_bytes | integer | No | Raw byte size |
| issue_hash | string | Yes | Hash of the parent issue asset |
| author | string | No | Uploader display name/email |
Asset kind · comments
| Field | Type | Always present | What it is |
|---|---|---|---|
| comments_count | integer | Yes | Number of comments |
| issue_key | string | Yes | Parent issue key |
Lineage
Lineage
This source records no lineage. Nothing in the system it reads describes data moving from one place to another, so no FLOW edges are produced. Related items are still linked — see Lineage & Relationships for what those links mean and how they differ from lineage.
Worth knowing
- Start with a JQL filter on a large instance. Scanning every issue ever filed is rarely the fastest way to learn something.
- Issue links are recorded as relationships, so related tickets stay connected in the graph.
Configuration
Beyond the fields below, every source also has the settings shared by all of them: the sampling strategy, the detectors to run, the scan schedule, and the compute limits for its scan jobs.
Required
Without these, the source will not save.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| required | object | Yes | —no extra properties | — |
| account_email | string | Yes | Atlassian account email used with API token for Basic authenticationformat email | — |
| base_url | string | Yes | Jira Cloud tenant URL (for example, https://your-domain.atlassian.net)format uri | — |
Secrets
Stored encrypted and never shown again after you save them. See Configuration & Fields.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| masked | object | Yes | —no extra properties | — |
| api_token | string | Yes | Atlassian API token for Jira Cloud | — |
Optional
Everything you can tune. Sensible defaults apply when you leave them alone.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| optional | object | No | —no extra properties | — |
| connection | object | No | HTTP and retry settings for Jira API calls.no extra properties | — |
| connection.max_retries | integer | No | Maximum retry attempts for transient API failures and rate limitsmin 0, max 10 | 3 |
| connection.rate_limit_delay_seconds | number | No | Additional delay between API requests to reduce rate-limit pressuremin 0 | 0 |
| connection.request_timeout_seconds | number | No | HTTP request timeout for Jira API callsmin 1 | 30 |
| content | object | No | Jira issue content extraction controls.no extra properties | — |
| content.attachment_max_bytes | integer | No | Maximum bytes downloaded per attachment for MIME inference and text extractionmin 1024 | 5242880 |
| content.include_attachments | boolean | No | Include issue attachments as related assets | true |
| content.include_comments | boolean | No | Include issue comments and aggregate them into a per-issue comments asset | true |
| scope | object | No | Optional Jira scope filters. When omitted, all visible issues are eligible for sampling.no extra properties | — |
| scope.jql | string | No | Additional JQL filter to combine with project scopemin length 1 | — |
| scope.project_ids | array | No | Project IDs to include (up to 50)min items 1, max items 50 | — |
| scope.project_ids[] | integer | No | — | — |
| scope.project_keys | array | No | Project keys to include (up to 50)min items 1, max items 50 | — |
| scope.project_keys[] | string | No | — | — |