Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature/first_reply_time_hours_performance_fix #152

Conversation

fivetran-joemarkiewicz
Copy link
Contributor

@fivetran-joemarkiewicz fivetran-joemarkiewicz commented Apr 25, 2024

PR Overview

This PR will address the following Issue/Feature: #151

This PR will result in the following new package version: v0.14.1

This will be a non breaking change and planned to be incorporated into the upcoming release.

Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Bug Fixes

  • Adjusted the int_zendesk__reply_time_business_hours model to only perform the weeks cartesian join on tickets that require the further look into the future.
    • Previously the int_zendesk__reply_time_business_hours would perform a cartesian join on all tickets to calculate weeks into the future. This was required to accurately calculate sla elapsed time for tickets with first replies far into the future. However, this was only necessary for a handful of tickets. Therefore, this has been adjusted to accurately only calculate the future weeks as far as either the first reply time or first solved time.

PR Checklist

Basic Validation

Please acknowledge that you have successfully performed the following commands locally:

  • dbt run –full-refresh && dbt test
  • dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

  • The appropriate issue has been linked, tagged, and properly assigned
  • All necessary documentation and version upgrades have been applied
  • [will be regenerated in release branch] docs were regenerated (unless this PR does not include any code or yml updates)
  • BuildKite integration tests are passing
  • Detailed validation steps have been provided below

Detailed Validation

Please share any and all of your validation steps:

Detailed validation includes two customers confirming that these changes drastically improved the performance of the int_zendesk__reply_time_business_hours model. No further validation required.

If you had to summarize this PR in an emoji, which would it be?

🚤

@fivetran-joemarkiewicz fivetran-joemarkiewicz marked this pull request as ready for review April 26, 2024 21:36
Copy link
Contributor

@fivetran-catfritz fivetran-catfritz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm--approved!

@fivetran-joemarkiewicz fivetran-joemarkiewicz merged commit 414849d into bugfix/duplicate_sla_event_ids_from_dst Apr 30, 2024
8 checks passed
fivetran-jamie added a commit that referenced this pull request Jun 25, 2024
* cast from timestamp to date

* reduce week generate from 208 to 52

* Update int_zendesk__reply_time_combined.sql

try different order of operations

* update schedule spine to explode out holiday periods

* forgot to add dbt timestamp

* addd timestamp cast and update test schema

* guess this didnt get staged

* new schema?

* remove the extra parenthesis that was just used for testing

* documentation/streamlit-report-addition (#149)

* documentation/streamlit-report-addition

* Update CHANGELOG.md

* Update README.md

* no changes to reply time combined

* versioning and changelog

* feature/first_reply_time_hours_performance_fix (#152)

* feature/first_reply_time_hours_performance_fix

* cleanup adjustments and documentation

* fix for databricks

* changelog

* Update models/sla_policy/reply_time/int_zendesk__reply_time_business_hours.sql

Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>

* decision log

* more updates on changelog

* up version

* docs

* bugfix/remianing-sla-issues

* validation additions

* changelog addition

* Update CHANGELOG.md

Co-authored-by: Renee Li <91097070+fivetran-reneeli@users.noreply.github.com>

* Update CHANGELOG.md

Co-authored-by: Renee Li <91097070+fivetran-reneeli@users.noreply.github.com>

* moving tests and adding new ones

* changelog update and requirements limit

* Update CHANGELOG.md

Co-authored-by: Renee Li <91097070+fivetran-reneeli@users.noreply.github.com>

* dics

* customer metrics drafted

* bk

* switch schedule

---------

Co-authored-by: Renee Li <renee.li@fivetran.com>
Co-authored-by: Renee Li <91097070+fivetran-reneeli@users.noreply.github.com>
Co-authored-by: Joe Markiewicz <74217849+fivetran-joemarkiewicz@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants