Closed fivetran-joemarkiewicz closed 7 months ago
This has issue should now be addressed in the latest v0.14.0
release of the dbt_zendesk package. As such, closing this out.
Please feel free to reopen or create a new issue if the original issue persists following the upgrade.
Is there an existing feature request for this?
Describe the Feature
Currently the
zendesk__sla_policies
end model does provide a SLA breach time field. However, it has become apparent that this field is inconsistent when it comes to thefirst_reply
andnext_reply
SLAs. This is due to the logic pulling the max breach at time for each record pulled through in the intermediate models. What the logic needs to do is identify which record the SLA was breached within and then pull that down for all records so we may persist it to the final model.Describe alternatives you've considered
As of right now there is no intuitive way to directly generate the breach time from the models.
Are you interested in contributing this feature?
Anything else?
No response