Update filter in filtered reply times CTE in int_zendesk__reply_time_combined

CHANGELOG.md

@@ -1,3 +1,13 @@
+# dbt_zendesk v0.13.2
+
+[PR #134](https://github.com/fivetran/dbt_zendesk/pull/134) includes the following changes:
+
+## Bug Fixes
+- Updated the `int_zendesk__reply_time_combined` model to account for when a ticket is first replied to outside SLA schedules or not yet replied to.
+
+## Under the Hood
+- Adjusted the filter used in the `filtered_reply_times` CTE for business hours to account for the aforementioned cases, as these records were mistakenly being filtered out previously.
+
 # dbt_zendesk v0.13.1
 
 [PR #128](https://github.com/fivetran/dbt_zendesk/pull/128) includes the following changes:

README.md

@@ -23,6 +23,8 @@
   - Calculates SLA policy breaches for Zendesk Professional or Enterprise users
 - Generates a comprehensive data dictionary of your source and modeled Zendesk data through the [dbt docs site](https://fivetran.github.io/dbt_zendesk/).
 
+> Note: Tickets from the Zendesk Chat channel will not populate in this package as the Fivetran connector does not currently support Chat based tickets. This is a feature request that has been flagged. 
+
 <!--section="zendesk_transformation_model"-->
 The following table provides a detailed list of final models materialized within this package by default. 
 > TIP: See more details about these models in the package's [dbt docs site](https://fivetran.github.io/dbt_zendesk/#!/overview?g_v=1).

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'zendesk'
-version: '0.13.1'
+version: '0.13.2'
 
 
 config-version: 2

integration_tests/dbt_project.yml

@@ -1,7 +1,7 @@
 config-version: 2
 
 name: 'zendesk_integration_tests'
-version: '0.13.1'
+version: '0.13.2'
 
 profile: 'integration_tests'
 

models/sla_policy/reply_time/int_zendesk__reply_time_combined.sql

@@ -119,7 +119,8 @@ with reply_time_calendar_hours_sla as (
       and ((
         agent_reply_at >= sla_schedule_start_at and agent_reply_at <= sla_schedule_end_at) -- ticket is replied to between a schedule window
         or (agent_reply_at < sla_schedule_start_at and sum_lapsed_business_minutes_new = 0 and sla_breach_at = first_sla_breach_at) -- ticket is replied to before a schedule window and no business minutes have been spent on it
-        or (agent_reply_at is null and {{ dbt.current_timestamp() }} >= sla_schedule_start_at and {{ dbt.current_timestamp() }} < next_schedule_start) -- ticket is not replied to and therefore active. But only bring through the active SLA record that is most recent (after the last SLA schedule starts but before the next)  
+        or (agent_reply_at is null and {{ dbt.current_timestamp() }} >= sla_schedule_start_at and ({{ dbt.current_timestamp() }} < next_schedule_start or next_schedule_start is null)) -- ticket is not replied to and therefore active. But only bring through the active SLA record that is most recent (after the last SLA schedule starts but before the next, or if there does not exist a next SLA schedule start time)  
+        or (agent_reply_at >= sla_schedule_end_at and agent_reply_at <= next_schedule_start ) -- ticket is replied to outside sla schedule hours
       ))
     or not in_business_hours