New Connector: Jira Service Management (JSM) Assets Connector → AWS RDS
AnsweredOverview
Requesting a new Fivetran connector to extract data from Jira Service Management (JSM) Assets (formerly Insight) using the JSM Assets REST API, and sync it into AWS RDS.
This connector will enable centralized analytics and reporting on asset/inventory data alongside other enterprise systems (finance, procurement, incident management, etc.).
Why Needed
Current Jira connectors only pull project and issue data (tickets, projects, workflows). However, JSM Assets stores configuration items (CIs) — hardware, software, contracts, and relationships — which are not accessible via Jira’s project APIs.
Without this connector, asset data must be manually exported or synced using custom scripts, leading to data silos and inconsistent schemas.
Proposed Connector Design
-
Source: JSM Assets REST API
-
Endpoints include
/objectschema,/objecttype,/object/{id}for schema and object retrieval. -
Supports retrieval of object types, attributes, and relationships.
-
-
Destination: AWS RDS (e.g., PostgreSQL, MySQL, or Aurora).
-
Behavior:
-
Discover object schemas and object types automatically.
-
Extract asset objects with attributes and relationships.
-
Map each object type to a corresponding RDS table (or use a metadata-driven design).
-
Support incremental sync using
updatedAtor similar timestamp. -
Handle schema changes dynamically (new attributes, object types).
-
Optional soft-delete tracking for removed assets.
-
Key Differences from Existing Jira Project Connector
| Area | Jira Projects Connector | JSM Assets Connector |
|---|---|---|
| Data Domain | Issues, Projects, Workflows | Assets, CIs, Object Types, Attributes |
| Schema | Fixed tables (issues, comments) | Dynamic schema (custom object types & attributes) |
| Relationships | Issue → Project | Object → ObjectType → Attributes → Linked Objects |
| Use Cases | SLA tracking, ticket analysis | Asset lifecycle, inventory, license tracking, dependency mapping |
Benefits
-
Integrates asset data into enterprise data lake/warehouse.
-
Enables cross-domain analytics (e.g., asset vs. incident, cost, risk).
-
Reduces ETL maintenance by using managed Fivetran sync.
-
Supports compliance, inventory audits, and hardware/software lifecycle visibility.
Technical Considerations
-
API authentication (OAuth or API token).
-
Pagination and rate-limit handling.
-
Metadata-driven schema updates in RDS.
-
Secure data transport (HTTPS/TLS 1.2+).
References
-
JSM Assets REST API documentation:
https://confluence.atlassian.com/servicemanagementserver/assets-rest-api-documentation-1044101761.html -
Example endpoint:
/jsm/assets/workspace/{workspaceId}/v1/object/{id}
-
Official comment
Hi Sampath,
I'll have our team take a look at this and get back to you.
Thanks,
Frank
Please sign in to leave a comment.
Comments
1 comment