Jira Cloud Connector — Add created_at and author_id columns to ISSUE_LINK table
Connector name: Jira cloud
Table name: ISSUE_LINK
Column to add:
created_at (TIMESTAMP) — when the link between issues was created
author_id (VARCHAR) — the account ID of the user who created the link
These values are available in the Jira Cloud changelog API response under
GET /rest/api/3/issue/{issueKey}?expand=changelog for items where field = "Link"
Additional details:
The Fivetran Jira Cloud connector currently syncs issue link relationships to the ISSUE_LINK table, but this table only captures the current state snapshot — it has no created_at or author_id columns. As a result, there is no way to determine who created or removed a link between issues and when.
The Jira Cloud REST API does expose this data in the changelog endpoint:
GET /rest/api/3/issue/{issueKey}?expand=changelog
The changelog response includes full history for Link field changes with
We verified this by querying all relevant tables in Snowflake —
author.accountId, author.emailAddress, and created timestamp. For example:{
"author": { "emailAddress": "......" },
"created": "2026-05-03T20:03:10.243+0000",
"items": [
{
"field": "Link",
"fieldtype": "jira",
"from": null,
"to": "....",
"toString": "This work item impacts account ...."
}
]
}
However, Fivetran only routes changelog data to ISSUE_FIELD_HISTORY (non-array fields) and ISSUE_MULTISELECT_HISTORY (array fields). Issue links are a relationship object and do not fit either table's schema, so Link changelog entries are silently dropped and never written to Snowflake.We verified this by querying all relevant tables in Snowflake —
ISSUE_FIELD_HISTORY, ISSUE_MULTISELECT_HISTORY, and ISSUE_LINK — and confirmed no rows for any link-related field_id.
Feature Request:One of the following solutions would address this gap:
- Add
created_atandauthor_idcolumns to theISSUE_LINKtable — populated from the JiraissueLinkAPI endpoint if that data is available there, or from the changelog - Write Link changelog entries from
GET /rest/api/3/issue/{id}?expand=changeloginto a newISSUE_LINK_HISTORYtable with columns:issue_id,related_issue_id,relationship,action(added/removed),author_id,created_at - Alternatively include Link changelog entries in
ISSUE_MULTISELECT_HISTORYunderfield_id = 'issuelinks'Jira Cloud API reference:- Changelog:
GET /rest/api/3/issue/{issueKey}?expand=changelog - Bulk changelog:
POST /rest/api/3/changelog/bulkfetch - Issue links:
GET /rest/api/3/issueLink/{linkId}
- Changelog:
Thanks in advance!
Please sign in to leave a comment.
Comments
0 comments