Within the int_jira__issue_type_parents model we perform a coalesce and join in order to associate issues with epics. This works fine for next gen projects. However, if a user is leveraging a classic project then the reference is associated using the epic link. This can cause an issue in the join because we are specifically creating the epic_issue_id the int_jira__issue_epic model as an integer. Although it is clear that this is not always going to be an integer since classic projects will have this be a link.
Therefore, we need to update the following lines to cast the fields as strings to avoid this error:
Is there an existing issue for this?
Describe the issue
Within the int_jira__issue_type_parents model we perform a coalesce and join in order to associate issues with epics. This works fine for next gen projects. However, if a user is leveraging a classic project then the reference is associated using the epic link. This can cause an issue in the join because we are specifically creating the epic_issue_id the int_jira__issue_epic model as an integer. Although it is clear that this is not always going to be an integer since classic projects will have this be a link.
Therefore, we need to update the following lines to cast the fields as strings to avoid this error:
Relevant error log or model output
Expected behavior
The models can succeed regardless of next gen or classic Jira projects
dbt Project configurations
Quickstart
Package versions
Latest
What database are you using dbt with?
snowflake
dbt Version
1.7.1
Additional Context
No response
Are you willing to open a PR to help address this issue?