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] "pausable_update_time" in ticket_field_history.field_name #168

Open
dfberdoy opened this issue Aug 30, 2024 · 2 comments
Open
Labels
type:enhancement New functionality or enhancement

Comments

@dfberdoy
Copy link

dfberdoy commented Aug 30, 2024

Hi Team,
I'm just wondering if is possible somehow to include "pausable_update_time" in this filter:

and ticket_field_history.field_name in ('next_reply_time', 'first_reply_time', 'agent_work_time', 'requester_wait_time')

or if there is a workaround to avoid filtering out those cases

Thank you!

@fivetran-catfritz
Copy link
Contributor

Hi @dfberdoy thanks for opening up this ticket. Are you looking to use int_zendesk__sla_policy_applied directly or would you ultimately want pausable_update_time persisted through to model zendesk__sla_policies? The reason we don't include pausable_update_time is because we haven't built out support for it in the downstream models, so I'm curious to hear how you're using this metric!

@fivetran-catfritz fivetran-catfritz added the type:enhancement New functionality or enhancement label Sep 6, 2024
@fivetran-catfritz
Copy link
Contributor

fivetran-catfritz commented Sep 6, 2024

Hi @dfberdoy I am going to mark this as a feature request and will leave this issue open in case anyone else wants to chime with interest or input on this feature!

@fivetran-catfritz fivetran-catfritz changed the title "pausable_update_time" in ticket_field_history.field_name [Feature] "pausable_update_time" in ticket_field_history.field_name Sep 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New functionality or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants