This PR will address the following Issue/Feature:
For Quickstart transformations we have removed the ticket_schedule requirement. As such we need to remove it from the config in our quickstart.yml, otherwise customers who don't have the ticket_schedule table will not see certain end objects populating.
This PR will result in the following new package version:
v0.13.2
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fix
Removed the ticket_schedule dependency in the quickstart.yml as it has been removed as a requirement in Quickstart transformations.
PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
[x] dbt run –full-refresh && dbt test
[x] dbt run (if incremental models are present) && dbt test
Before marking this PR as "ready for review" the following have been applied:
[na] The appropriate issue has been linked, tagged, and properly assigned
[x] All necessary documentation and version upgrades have been applied
[x] docs were regenerated (unless this PR does not include any code or yml updates)
[x] BuildKite integration tests are passing
[ na] Detailed validation steps have been provided below
Detailed Validation
Please share any and all of your validation steps:
This will be validated by seeing the relevant end objects such as the first_reply_time_business_minutes metric populate
If you had to summarize this PR in an emoji, which would it be?
PR Overview
This PR will address the following Issue/Feature: For Quickstart transformations we have removed the ticket_schedule requirement. As such we need to remove it from the config in our quickstart.yml, otherwise customers who don't have the ticket_schedule table will not see certain end objects populating.
This PR will result in the following new package version:
v0.13.2
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:
Bug Fix
ticket_schedule
dependency in the quickstart.yml as it has been removed as a requirement in Quickstart transformations.PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:
Before marking this PR as "ready for review" the following have been applied:
Detailed Validation
Please share any and all of your validation steps:
This will be validated by seeing the relevant end objects such as the
first_reply_time_business_minutes
metric populateIf you had to summarize this PR in an emoji, which would it be?
:dancer: