v0.22.0-a1 dbt_zendesk

This pre-release builds upon the changes made in v0.21.0-a2 and v0.21.0-a1 and includes updates made in v0.21.0.

Bug Fixes

• Fixes an issue introduced in v0.21.0-a2 and truly allows for Full Resolution Time logic to handle tickets marked as closed but never solved. This update ensures that the model will prioritize the solved status if available and use the first closed status record otherwise. (PR #187)

v0.21.0 dbt_zendesk

This release includes the following updates:

Dependency Changes

• Removed the package dependency on calogica/dbt_date, which is no longer actively maintained. Replaced the following macros with fivetran_* equivalents that provide the same functionality and have been tested for compatibility: (#191)
  • dbt_date.week_end → zendesk.fivetran_week_end
  • dbt_date.week_start → zendesk.fivetran_week_start

Documentation

• Added Quickstart model counts to README. (#183)
• Corrected references to connectors and connections in the README. (#183)

Full Changelog: v0.20.0...v0.21.0

v0.21.0-a2 dbt_zendesk

This pre-release builds upon the changes made in v0.21.0-a1.

Feature Update

• Adjusts Full Resolution Time logic to handle tickets that were marked as closed but not solved. This is not the norm for tickets, but a case that the Data Model will still accommodate. (PR #187)

v0.21.0-a1 dbt_zendesk

New Features

• Incorporated the ticket_chat and ticket_chat_event source tables to properly capture tickets created via chat and native_messaging channels in SLA Policy and other ticket metrics. (PR #187)
• Added the using_ticket_chat variable to enable/disable ticket_chat and ticket_chat_event staging models and transformations. (PR #187)
  • For Fivetran Quickstart users, using_ticket_chat is dynamically set based on the presence of the ticket_chat and ticket_chat_event source tables.
  • For other users, using_ticket_chat is set to False by default. To change this and enable the ticket chat models, add the following configuration (see README for details).

vars:
  zendesk_source:
    using_ticket_chat: True
  zendesk:
    using_ticket_chat: True

Note: If using_ticket_chat is enabled, this update increases the model count of the package by 4 models.

Documentation

• Added Quickstart model counts to README. (#183)
• Corrected references to connectors and connections in the README. (#183)

v0.20.0 dbt_zendesk

Upstream Under-the-Hood Updates

• (Affects Redshift only) Updates the union_zendesk_connections macro to use a limit 1 instead of limit 0 for empty tables.
  • When a table is empty, Redshift ignores explicit data casts and will materialize every column as a varchar. Redshift users may experience errors in downstream transformations as a consequence.
  • For each staging model, if the source table is not found, the package will create a empty table with 0 rows for non-Redshift warehouses and a table with 1 all-null row for Redshift destinations. The 1 row will ensure that Redshift will respect the package's datatype casts.

Documentation Update

• Moved badges at top of the README below the H1 header to be consistent with popular README formats.

Full Changelog: v0.19.3...v0.20.0

v0.19.3 dbt_zendesk

PR #185 includes the following updates:

Quickstart Update

• Removed organization from using_organization_tags configuration to maintain a one-to-one mapping between a Quickstart source table and whether its corresponding variable in the models should be enabled or disabled.

Under The Hood

• Updated the packages.yml to point to the latest release of the dbt_zendesk_source package.

Full Changelog: v0.19.2...v0.19.3

v0.19.2 dbt_zendesk

PR #181 includes the following updates:

New Features

• Introduced new config variables using_brands and using_organizations to allow customers to enable and disable brand and organization source data, resulting in potential downstream impacts:
• End models that could be impacted by these variables include:
  • zendesk__ticket_backlog: using_brands and/or using_organizations can be set to false to disable brand and/or organization fields.
  • zendesk__ticket_enriched: using_organizations can be set to false to remove organization fields from the final model.
• Intermediate models that could be impacted by these variables include:
  • int_zendesk__organization_aggregates: using_organizations can be utilized to completely disable the model.
  • int_zendesk__ticket_aggregates: using_brands can be set to false to remove brand fields from the final model.
  • int_zendesk__updater_information: using_organizations can be set to false to remove organization fields from the final model.

Under the Hood

• Updated table_variables in the quickstart.yml with the new brand and organization tables.
• Updated our Buildkite model run script to ensure we test for when using_brands and using_organizations is set to either true or false.

Documentation Updates

• Updated README with instructions on how to disable brand and organization sources.

Full Changelog: v0.19.1...v0.19.2

v0.19.1 dbt_zendesk

PR #180 includes the following update:

Bug Fixes

• In v0.19.0, Snowflake users may have seen when searching for a relation, dbt found an approximate match errors when running the stg_zendesk__group_tmp model. We have updated the adapter.get_relation() logic that was causing this error in the zendesk_source package (see source package release).

Full Changelog: v0.19.0...v0.19.1

v0.19.0 dbt_zendesk

PR #178 includes the following updates:

Feature Update: Run Models on Muliple Zendesk Sources

• This release supports running the package on multiple Zendesk sources at once! See the README for details on how to leverage this feature.

Please note: This is a Breaking Change in that we have a added a new field, source_relation, that points to the source connector from which the record originated. This field addition will require a dbt run --full-refresh, even if you are not using this new functionality.

Documentation

• Cleaned up the column-level documentation descriptions for the zendesk__ticket_enriched and zendesk__ticket_metrics models.

Under the Hood

• Relevant to package maintainers only:
  • Added a consistency data validation test for each end model.
  • Added consistency_test_exclude_fields to ignore in consistency tests. These are largely timestamp fields that can differ slightly due to different runtimes, but source_relation is also currently included due to the nature of this update.
  • Filtered out records made or updated today from consistency tests to avoid false positive failures due to different runtimes.
  • Incorporated source_relation into each validation test.

Full Changelog: v0.18.1...v0.19.0

v0.18.1 dbt_zendesk

PR #174 includes the following changes:

Bug Fix

• Addressed an issue in which some records in zendesk__sla_policies might erroneously have a null sla_policy_name due to system-generated millisecond-long gaps in timestamps. The package now compares timestamps to the nearest second when selecting valid SLA policy names in int_zendesk__sla_policy_applied.

Under the Hood

• Updated consistency_sla_policies and sla_count_match data validation tests to account for the above change.

Full Changelog: v0.18.0...v0.18.1