[Feature] Add Flag for CreatedSolvedClosedSameDay

[chanafee]

Is there an existing feature request for this?

• I have searched the existing issues

Describe the Feature

This flag would simply signify if a ticket was either solved or closed on the same day it was created. (day defined by the local time zone of the user). The goal of this flag is to power reporting around how fast tickets are solved, outside of SLA metrics. Additionally, this flag takes auto-closed tickets into account.

Describe alternatives you've considered

Today, I have code that leverages the base Ticket Field History for coding out my own flag that delineates if a ticket was closed or solved on the same day it was created.

Are you interested in contributing this feature?

• Yes.
• Yes, but I will need assistance and will schedule time during your office hours for guidance.
• No.

Anything else?

No response

[fivetran-avinash]

Thanks for submitting this feature @chanafee! I agree this flag would be a worthwhile feature to add and we would love if you'd be willing to contribute.

If you'd like to expedite adding this to the package, would you be able to open a PR on this package and contribute this code? We would then be able to review it more quickly and ship it live to a new package upgrade.

If not, we will be able to look at this in the future, but it might take a bit longer before this goes live.

Let us know which approach works best for you! Looking forward to working with you on getting this flag into our package.

[chanafee]

Hi Avinash! That is great news ☺ I’m happy to wait a little while until your team has capacity to look at this. Thanks a bunch! Caitlin From: Avinash Kunnath ***@***.***> Sent: Monday, February 12, 2024 12:28 PM To: fivetran/dbt_zendesk ***@***.***> Cc: Caitlin Hanafee ***@***.***>; Mention ***@***.***> Subject: Re: [fivetran/dbt_zendesk] [Feature] Add Flag for CreatedSolvedClosedSameDay (Issue #145) ATTENTION: This eMail originated from outside of Vail Resorts and may or may not be legitimate. Although we do our best to screen phishing emails, please use extra caution before opening any attachments or clicking on any links unless you are absolutely sure the source of the email is trusted. If in doubt about the legitimacy of this email, please use the Report Phish button for validation. Thanks for submitting this feature @chanafee<https://urldefense.com/v3/__https:/github.com/chanafee__;!!FK2kAO7IF7m7Bw!u-sI4Zi21NsFaN6yQwbPgf62Q5q8YZcZqKdYVWLWTzAkPhguG3JtkQBk4c2i4l3QYBLuUDC70k204s1R3SBg8hOzuKvPq-uM$>! I agree this flag would be a worthwhile feature to add and we would love if you'd be willing to contribute. If you'd like to expedite adding this to the package, would you be able to open a PR on this package and contribute this code? We would then be able to review it more quickly and ship it live to a new package upgrade. If not, we will be able to look at this in the future, but it might take a bit longer before this goes live. Let us know which approach works best for you! Looking forward to working with you on getting this flag into our package. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/fivetran/dbt_zendesk/issues/145*issuecomment-1939395040__;Iw!!FK2kAO7IF7m7Bw!u-sI4Zi21NsFaN6yQwbPgf62Q5q8YZcZqKdYVWLWTzAkPhguG3JtkQBk4c2i4l3QYBLuUDC70k204s1R3SBg8hOzuLRWKkHW$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/A672XVN5KB355GCXPU42GG3YTJUKJAVCNFSM6AAAAABDE34QUSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZGM4TKMBUGA__;!!FK2kAO7IF7m7Bw!u-sI4Zi21NsFaN6yQwbPgf62Q5q8YZcZqKdYVWLWTzAkPhguG3JtkQBk4c2i4l3QYBLuUDC70k204s1R3SBg8hOzuMZ-IjRz$>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>> The information contained in this message is confidential and intended only for the use of the individual or entity named above, and may be privileged. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please reply to the sender immediately, stating that you have received the message in error, then please delete this e-mail. Thank you.