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 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.

1. Add created_at and author_id columns to the ISSUE_LINK table — populated from the Jira issueLink API endpoint if that data is available there, or from the changelog
2. Write Link changelog entries from GET /rest/api/3/issue/{id}?expand=changelog into a new ISSUE_LINK_HISTORY table with columns: issue_id, related_issue_id, relationship, action (added/removed), author_id, created_at
3. Alternatively include Link changelog entries in ISSUE_MULTISELECT_HISTORY under field_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}

Please let us know , If there is already an existing workaround or an alternative table/field in the Fivetran Jira Cloud connector that captures this data, we may have missed it in our investigation.

Thanks in advance!