Closed wdepril closed 3 years ago
Hi @wdepril thanks so much for opening this issue.
I completely see how this would be generating an error if you do not have the versions
table being synced. Our team has been able to tackle these requests in the past and we will add this task to our next sprint. I will post back here once we are able to start working on this fix.
Thanks again!
Thanks for the message. As I mentioned no urgency.
On Thu, Aug 12, 2021 at 11:37 AM Joe Markiewicz @.***> wrote:
Hi @wdepril https://github.com/wdepril thanks so much for opening this issue.
I completely see how this would be generating an error if you do not have the versions table being synced. Our team has been able to tackle these requests in the past and we will add this task to our next sprint. I will post back here once we are able to start working on this fix.
Thanks again!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/fivetran/dbt_jira_source/issues/20#issuecomment-897831233, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOEXBAYBYMVJZVB2OPOR2LT4QBF3ANCNFSM5B7QO34Q . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .
--
Wim De Pril @.*** +1 303 653 5853
@wdepril This change is now reflected within the latest releases of the dbt_jira and dbt_jira_source packages!
You may disable the version models by setting the new jira_using_versions
variable to false. Please feel free to open a new issue if you have any other questions. Thanks again for raising this issue to our team 😄
Are you a current Fivetran customer? Customer - ZERO.health.
Describe the bug
Expected behavior have a variable similar to jira_using_sprints to turn versions of
We worked around it by creating some fake version which created the table. So no urgency for a fix.