Open abrown-calix opened 6 months ago
Hi @abrown-calix ,thanks for opening this. I'm understanding that you wish to be able to bring multiple values that can be tied to a Jira entity through in the model. This is a limitation that we're aware of and we have a Feature Request opened here that you may follow.
Thanks for sharing your workaround! I see you're open to creating a PR, we welcome that! Let me know if you have other notes you'd like to share.
-- 4/1/24 update-- corrected the link pointing to the relevant FR
Is there an existing issue for this?
Describe the issue
In our organization we can have multiple components for one jira story. We added component to our list of columns we want to see in the dbt_project.yml issue_field_history_columns variable and it seems to work up to a point. In reviewing the jira__daily_issue_field_history there is a join in the set_values CTE where it does not account for the fact we can have multiple values. If we could add the join further up stream to get the correct values that would be greatly beneficial.
Relevant error log or model output
Expected behavior
That the components all are the names of the components and not just those where a story has one component listed
dbt Project configurations
issue_field_history_columns: ['Story Points','Summary','Components']
Package versions
version: 0.15.0
What database are you using dbt with?
snowflake
dbt Version
1.7.9
Additional Context
No response
Are you willing to open a PR to help address this issue?