.svg)
Jira Connector for eDiscovery & Data Collection
Collect Jira issues, comments, attachments, and project metadata for eDiscovery, compliance, and internal investigations, without manual exports. The Onna + Jira Connector lets you access data across your organization on a defensible, unified platform.
Why Connect Jira to Your eDiscovery Collections Platform
Jira is where teams manage projects, track issues, document work, and collaborate on product and operational execution. When legal, compliance, or investigative needs arise, that data needs to be accessible, complete, and defensible.
Without the right tools, collecting from Jira is harder than it should be:
Relevant data is spread across projects, issues, comments, and attachments
Workflows, statuses, and custom fields add context that must be preserved
Attachments and updates can materially change the meaning of an issue record
Large environments may require scalable, resumable syncs across multiple projects
The Onna + Jira Connector enables organizations to collect Jira data in a scalable and defensible way. Through Jira’s API, the connector captures issues, attachments, comments, and metadata in native format while preserving the structure and business context of each record.
Jira Connector Capabilities
The Onna + Jira Connector is designed for enterprise-scale data collection. Key capabilities include:
Direct API-based connection to Jira
No authorized connection requirement
Audit logs for collection activity
Full archive support
Admin access support
Resumable sync for large environments
One-time sync, auto-sync, and auto-sync with archive
Source Holds support
Project-level collection configuration
Native-format issue collection
These capabilities allow organizations to run targeted Jira collections for specific matters or maintain ongoing archives for compliance and investigative readiness.
What Data Can Be Collected from Jira
The connector captures both content and metadata from Jira environments, including:
Issues
Issue descriptions
Issue names
Summaries
Status
Type
Progress
Priority
Resolution
Due date
Due date
Original estimates
Time spent
Votes
Issue links
Custom fields
Comments & Collaboration
Issue comments
Issue-level updates tied to project workflows
Files & Attachments
Attachments associated with issues
Files synced from Jira records
These collections preserve the issue record and its surrounding project context so legal and compliance teams can review how work, approvals, and decisions were documented over time.
Jira Metadata Collected
Along with standard file metadata such as filename and size, the connector collects Jira-specific metadata fields including:
Project key
Project name
Project type
Creator
Updater
Issue status
Issue type
Priority
Resolution
Due date
Components
Original estimate
Time spent
Votes
Issue links
Custom field values
This metadata allows teams to reconstruct issue history, understand project context, and identify the records most relevant to a matter.
How Jira Data Collection Works
The connector simplifies Jira data collection through a structured workflow.
Add Jira as a data source
Navigate to the workspace where you want to set up your sync and add Jira as a source.
Name the source and enter the host name
Create a source name and enter your Jira site URL in the host name field.
Authenticate the connection
Connect to Jira using one of two methods:
- Login with user and API token
- Login with user and password
Configure the collection
Select Configure to define what data to sync and choose your preferred sync settings.
Select projects
Choose the Jira projects you want to include in the collection.
Select sync mode
Choose the synchronization mode that aligns to your matter or compliance workflow.
Set sync dates
Depending on sync mode, define:
- Sync start date
- Sync end date for one-time collection
If no sync start date is entered, the connector collects all available Jira data.
Start sync
Once configuration is complete, the Jira collection begins and data appears in your Onna workspace.
Jira Data Collection Options
The Onna + Jira Connector supports flexible sync modes depending on legal, compliance, and investigative needs.
One-Time Sync
A targeted collection used for litigation, investigations, or requests with a defined date range.
Auto Sync
Continuously collects new Jira data from the selected start date forward.
Auto Sync & Archive
Maintains an ongoing collection and archive of Jira data as records continue to change over time.
Common Jira
eDiscovery Use Cases
Litigation Response
Collect Jira issues, comments, and attachments relevant to disputes, deadlines, and product decisions.
Internal Investigations
Review project records, issue activity, and supporting tied to incidents, escalation paths, or policy concerns.
Regulatory Compliance
Archive Jira records that document operational processes, approvals, controls, and service workflows.
Incident Response
Investigate how teams tracked, updated, and resolved technical or operational incidents inside Jira.
Related Data Source Connectors
Onna connects to 29+ collaboration apps so when a matter spans Slack and Google Workspace, Zoom, Microsoft Teams, or Atlassian, you handle it all in one platform. No switching between tools. No duplicating workflows.
Get more info about related connectors:
%201.webp){kind=logo}
%201.webp)
Onna + Jira Connector FAQs
Yes. Onna connects directly to Jira through Jira’s API and collects information in native format.
Onna can collect issues, attachments, comments, and issue-related metadata including status, type, priority, resolution, due date, project details, issue links, and custom fields.
Yes. During configuration, you can select the specific Jira projects you want to sync.
The Jira connector supports one-time sync, auto-sync, and auto-sync and archive.
No. The Jira connector does not support custodian-based collections.
No. In-place preservation is not supported for Jira. However, Source Holds are supported.
Yes. The Jira connector supports resumable sync, which helps with large-scale data collection.
No. The connector does not require an authorized connection, but it does require valid Jira access credentials.
No. File versioning is not supported for the Jira connector.
Because Jira native files are in HTML format, Onna takes what Jira’s API returns and formats it like a ticket for review and collection workflows.
Start Collecting Jira Data for eDiscovery
Connect Jira in minutes and begin collecting issues, comments, attachments, and project metadata for eDiscovery, compliance, and investigations.