Hi @bearavan ! Thanks for the question.
Our solutions team did work on a Jira transformation dbt package which does join issues with components in the `jira__daily_issue_field_history` (which compiles historical records of fields for when the issue was open) and `jira__issue_enhanced` model (which has enriched data for each issue, including components)!
But all of our end models do tie back issues and components! You can trace the model lineage by clicking the green circle in the bottom right of our documentation. I've attached an image of part of that graph which runs components and issues into those end models.
I'd recommend installing the package and follow the instructions in the README then try and run the package to see if the end models that are produced with your data satisfies what you are looking for.
Let us know if you have any follow-up questions!
Hi @bearavan ! Thanks for the question.
Our solutions team did work on a Jira transformation dbt package which does join issues with components in the `jira__daily_issue_field_history` (which compiles historical records of fields for when the issue was open) and `jira__issue_enhanced` model (which has enriched data for each issue, including components)!
But all of our end models do tie back issues and components! You can trace the model lineage by clicking the green circle in the bottom right of our documentation. I've attached an image of part of that graph which runs components and issues into those end models.
I'd recommend installing the package and follow the instructions in the README then try and run the package to see if the end models that are produced with your data satisfies what you are looking for.
Let us know if you have any follow-up questions!
