Missing Historic Attributes in ExploreGeplant
We used to measure some Updates regarding changes of Ticketgroup by using the historic attributes in Insights.
"Each Historic attribute shows the value at the start of an update, not the end. This is important if one of these four fields changes."
"These Historic attributes are recorded whenever an update includes at least one Ticket Text Field Change, Ticket Numeric Change, and/or Satisfaction Survey Change."
Trying to find a way with Explore is quite a Quest.
Only by creating a quite comlicated Query, buildig Metrics and using result metric calculation I come close to the data produced easly via Insights.
Execution of the querie takes incredibly long and it would be much easier to simply chose the Historic Attributes in Explore.
Please consider migrating the historic attributes to the Explore datasets.
@..., thank you for bringing this up.
It is a known Insight parity gap and I can definitely relate to the fact that setting similar configuration in Explore is quite complex at the moment. We plan to introduce equivalent historic attributes in the Ticket Updates dataset in the second half of this year.
Can I be added to a list to be informed when this is live? This is also an important attribute for many of our reports.
Hi Jarrod -
Just make sure you're following this post, and you'll receive notifications as we update it.
Looking forward to updates on this since knowing ticket group flow is important to us.
This is marked planned, but there have been no updates from Zendesk in 2 years. Is this on the roadmap?
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.