v1.1.0-a2 dbt_zendesk

PR #216 includes the following updates on top of v1.1.0-a1.

Bug Fix

• Removes a filter in int_zendesk__updates that was erroneously filtering out some first reply messages. This filter was intended to remove "batched" chat messages stored in the TICKET_COMMENT table, but the filter is unnecessary (and in some cases problematic) for properly calculating downstream SLA metrics.

Full Changelog: v1.1.0-a1...v1.1.0-a2

v1.1.0-a1 dbt_zendesk

PR #216 includes the following updates:

Schema Changes

4 total changes • 0 possible breaking changes

Data Model/Column	Change type	Old	New	Notes
int_zendesk__ticket_work_time_business	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the zendesk__ticket_metrics model.
int_zendesk__ticket_first_reply_time_business	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the zendesk__ticket_metrics model.
int_zendesk__ticket_full_resolution_time_business	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the zendesk__ticket_metrics model.
int_zendesk__ticket_first_resolution_time_business	Materialization	Ephemeral	Table	This is intended to resolve potential timeout issues when running the zendesk__ticket_metrics model.

Feature Update

• Materializes the above intermediate models as tables so as to optimize runs of zendesk__ticket_metrics and avoid potential timeout issues.
  • If you would like maintain the ephemeral materialization of these models and are running the Zendesk package via dbt Core, add the following configuration to your dbt_project.yml:

models:
  zendesk:
    agent_work_time:
      int_zendesk__ticket_work_time_business:
        +materialized: ephemeral
    reply_times:
      int_zendesk__ticket_first_reply_time_business:
        +materialized: ephemeral
    resolution_times:
      int_zendesk__ticket_full_resolution_time_business:
        +materialized: ephemeral
      int_zendesk__ticket_first_resolution_time_business:
        +materialized: ephemeral

Full Changelog: v1.0.1...v1.1.0-a1

v1.0.1 dbt_zendesk

This is the general release of v0.25.1-a1. PR #208 includes the following updates:

Bug Fixes

• Fixed uniqueness issue in int_zendesk__user_role_history by removing duplicate and erroneous logs with identical timestamps.

Full Changelog: v1.0.0...v1.0.1

v1.0.0 dbt_zendesk

PR #211 includes the following updates:

Breaking Changes

Source Package Consolidation

• Removed the dependency on the fivetran/zendesk_source package.
  • All functionality from the source package has been merged into this transformation package for improved maintainability and clarity.
  • If you reference fivetran/zendesk_source in your packages.yml, you must remove this dependency to avoid conflicts.
  • Any source overrides referencing the fivetran/zendesk_source package will also need to be removed or updated to reference this package.
  • Update any zendesk_source-scoped variables to be scoped to only under this package. See the README for how to configure the build schema of staging models.
• As part of the consolidation, vars are no longer used to reference staging models, and only sources are represented by vars. Staging models are now referenced directly with ref() in downstream models.

dbt Fusion Compatibility Updates

• Updated package to maintain compatibility with dbt-core versions both before and after v1.10.6, which introduced a breaking change to multi-argument test syntax (e.g., unique_combination_of_columns).
• Temporarily removed unsupported tests to avoid errors and ensure smoother upgrades across different dbt-core versions. These tests will be reintroduced once a safe migration path is available.
  • Removed all dbt_utils.unique_combination_of_columns tests.
  • Moved loaded_at_field: _fivetran_synced under the config: block in src_zendesk.yml.

Full Changelog: v0.25.0...v1.0.0

v0.25.1-a1 dbt_zendesk

PR #208 includes the following updates:

Bug Fixes

• Fixed uniqueness issue in int_zendesk__user_role_history by removing duplicate and erroneous logs with identical timestamps.

Full Changelog: v0.25.0...v0.25.1-a1

v0.25.0 dbt_zendesk

Schema/Data Changes

2 total changes • 2 possible breaking changes

Data Model/Column	Change type	Old	New	Notes
zendesk__ticket_metrics • first_resolution_business_minutes • first_reply_time_business_minutes • agent_wait_time_in_business_minutes • requester_wait_time_in_business_minutes • solve_time_in_business_minutes • agent_work_time_in_business_minutes • on_hold_time_in_business_minutes • new_status_duration_in_business_minutes • open_status_duration_in_business_minutes • first_reply_time_calendar_minutes • total_reply_time_calendar_minutes • ticket_unassigned_duration_calendar_minutes • requester_last_login_age_minutes • assignee_last_login_age_minutes • unsolved_ticket_age_minutes • unsolved_ticket_age_since_update_minutes	Column Data Type	Integer	Numeric rounded to four decimal places	Removed logic casting ticket metric values as integers in intermediate models. This may have caused minor rounding discrepancies between the Zendesk data models and UI reports. (PR #204)
zendesk__sla_policies • sla_elapsed_time	Data Type	Integer	Numeric rounded to four decimal places	May particularly affect agent_work_time, first_reply_time, next_reply_time, and requester_wait_time SLA policy metrics. (PR #204)

Under the Hood

PR #205 includes the following updates:

• Updated conditions in .github/workflows/auto-release.yml.
• Added .github/workflows/generate-docs.yml.
• Added +docs: show: False to integration_tests/dbt_project.yml.
• Migrated flags (e.g., send_anonymous_usage_stats, use_colors) from sample.profiles.yml to integration_tests/dbt_project.yml.
• Updated maintainer_pull_request_template.md with improved checklist.
• Updated .gitignore to exclude additional DBT, Python, and system artifacts.

Full Changelog: v0.24.2...v0.25.0

v0.25.0-a1 dbt_zendesk

PR #204 includes the following updates:

Bug Fixes

• Removes logic casting ticket metric values as integers in intermediate models. This may have caused minor rounding discrepancies between the Zendesk data models and UI reports.
  • This may impact the following fields in the zendesk__ticket_metrics model, which will now be numerics rounded to the fourth decimal place:
    • first_resolution_business_minutes
    • full_resolution_business_minutes
    • first_reply_time_business_minutes
    • agent_wait_time_in_business_minutes
    • requester_wait_time_in_business_minutes
    • solve_time_in_business_minutes
    • agent_work_time_in_business_minutes
    • on_hold_time_in_business_minutes
    • new_status_duration_in_business_minutes
    • open_status_duration_in_business_minutes
    • first_reply_time_calendar_minutes
    • total_reply_time_calendar_minutes
    • ticket_unassigned_duration_calendar_minutes
    • requester_last_login_age_minutes
    • assignee_last_login_age_minutes
    • unsolved_ticket_age_minutes
    • unsolved_ticket_age_since_update_minutes
  • Particularly for the following SLA policy metrics, this may impact zendesk__sla_policies.sla_elapsed_time, which is also now a numeric rounded to the fourth decimal place:
    • agent_work_time
    • first_reply_time
    • next_reply_time
    • requester_wait_time

v0.24.2 dbt_zendesk

This release includes the following updates:

Schema/Data Changes

2 total changes • 0 possible breaking changes

Data Model	Change type	Old	New	Notes
int_zendesk__commenter_reply_at	Materialization	View	Ephemeral	This intermediate model is now ephemeral, meaning the view will no longer be updated in the warehouse. While the view will still exist in the warehouse, it will become outdated. We therefore recommend manually dropping the int_zendesk__commenter_reply_at view. (PR #203)
stg_zendesk__ticket_chat_event	Filter			Excludes ticket_chat_event records where the actor_id is __trigger or __system (instead of the expected ###### or agent:###### formats). This was done to avoid data-casting errors and maintain downstream joins and comment metrics. (Source PR #72)

Under the Hood

• Added a system-facing using_ticket_schedules variable to the quickstart.yml to better support Quickstart. This variable is not available for use otherwise. (PR #195)

Full Changelog: v0.24.1...v0.24.2

v0.24.1 dbt_zendesk

This release includes the following updates:

Bug Fix

• Replaced erroneous description key in the zendesk.yml docs file. (PR #201)

Under the Hood

• Updated package maintainer PR template. (PR #202)

Contributors

• @raphaelvarieras (PR #201)

Full Changelog: v0.24.0...v0.24.1

v0.24.0 dbt_zendesk

PR #199 includes the following updates:

Breaking Change for dbt Core < 1.9.6

Note: This is not relevant to Fivetran Quickstart users.

Migrated freshness from a top-level source property to a source config in alignment with recent updates from dbt Core (Zendesk Source v0.18.0). This will resolve the following deprecation warning that users running dbt >= 1.9.6 may have received:

[WARNING]: Deprecated functionality
Found `freshness` as a top-level property of `zendesk` in file
`models/src_zendesk.yml`. The `freshness` top-level property should be moved
into the `config` of `zendesk`.

IMPORTANT: Users running dbt Core < 1.9.6 will not be able to utilize freshness tests in this release or any subsequent releases, as older versions of dbt will not recognize freshness as a source config and therefore not run the tests.

If you are using dbt Core < 1.9.6 and want to continue running Zendesk freshness tests, please elect one of the following options:

1. (Recommended) Upgrade to dbt Core >= 1.9.6
2. Do not upgrade your installed version of the zendesk package. Pin your dependency on v0.23.0 in your packages.yml file.
3. Utilize a dbt override to overwrite the package's zendesk source and apply freshness via the previous release top-level property route. This will require you to copy and paste the entirety of the previous release src_zendesk.yml file and add an overrides: zendesk_source property.

Under the Hood

• Updates to ensure integration tests use latest version of dbt.

Full Changelog: v0.23.0...v0.24.0