Feature Marketplace · Connectors
Jira Connector
Atlassian Jira Cloud work management platform. Syncs issues, projects, and users via the REST API v3 with JQL-based incremental search and webhook support for real-time event notifications.
What syncs
The Jira records STRAX brings into your hub.
Each kind of record is mapped once to your company model in the STRAX hub, then kept current in every system that needs it. Where Jira announces changes, they arrive as they happen.
Issues
Jira issues retrieved via the JQL search endpoint including status, priority, assignee, and dates.
Changes arrive as they happenProjects
Jira projects retrieved via /project/search including type, style, lead, and visibility.
Changes arrive as they happenUsers
Jira users retrieved via /users/search including account type, status, and locale.
Changes arrive as they happenJira data in your own SQL Server, then wherever it is needed.
STRAX is a self-hosted integration platform. The Jira records land in the STRAX hub, a SQL Server database on your own servers, where your reports, portals and workflows read them. From there the hub delivers them to the other systems you connect, whether those run on SQL Server, MySQL, PostgreSQL or another API. STRAX signs in to Jira with an API key that you provide, stored encrypted.
How STRAX connectors work → How the STRAX integration engine works → Connecting a system, in the documentation →
About this listing
| Version | 1.0.1 |
| Author | STRAX |
| Category | Connectors |
| Published | 2026-07-15 |
What's inside
| Connector profile | 1 |
Free listing
Install it from Feature Marketplace inside STRAX
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "Jira Connector"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.