Fivetran's Jira connector once modeled a many-to-many relationship between the issue and the component tables in an issue_components table, visible in this ERD. Fivetran changed its Jira connector on September 10, 2020. This resulted in the removal of the issue_components table. The current ERD as of March 5, 2025 shows component now only related to project.

Software teams around the world commonly use Jira component as a way of categorizing issues into software products, team names, functionality groups, etc. In Jira, an issue has one-to-many components. Components are essential for sense-making of Jira issues. Modeling a relationship of component only to project does not help with making sense of issues.

This request is to restore the modeled relationship of issue to component. This could be implemented as either a many-to-many bridge table as before, or an array of component IDs in the issue table.

Fivetran is likely already fetching the necessary data with its existing connector to the /issue API, but may be throwing it away.