Graeme Carmichael

1. Community
2. Feedback - Reporting and analytics (Explore)
3. Tickets solved metric discrepancy in Updates history Explore dataset

Thanks Eugene Hopefully, this default metric can be updated.

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 8. August 2022 06:46
• 0 Stimmen

1. Community
2. Feedback - Reporting and analytics (Explore)
3. Tickets solved metric discrepancy in Updates history Explore dataset

Nathan I can recreate this. The metric for Tickets_Solved in the Support Updates History dataset is defined as: IF ([Changes - Field name]="status"       AND [Changes - Previous value]!="solved"   ...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 1. August 2022 15:07
• 1 Stimme

1. Community
2. Zendesk Suite Q&A
3. Random ticket - Quality purpose

Jingwei The easiest way would be to create separate reports for each group. Each report having the required value coded into the report. Then place each report on a dashboard so that you can see al...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 7. Juli 2022 06:42
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Report on previous assignee of a ticket

Greg The easiest way would be to use the Updates History dataset. Metrics DCOUNT(Tickets updated) Rows Ticket ID Update Date Update ticket assignee Assignee name Filter Changes Field Name = as...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 6. Juli 2022 07:56
• 1 Stimme

1. Community
2. Zendesk Suite Q&A
3. Last assignment to resolution time in Business Hour

Pam Unfortunately, I do not believe that is possible. Zendesk tracks business hours metrics at ticket level, not at the assignee level. So it is not possible to drill to that level of detail.  

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 29. Juni 2022 06:46
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Bug when applying updater tag to query?

Jack How about using brackets. It works for me without them, but try… IF ( [Changes - Field name] = "Number of Active engineers" )THEN [Ticket ID] ENDIF

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 25. Juni 2022 09:51
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Bug when applying updater tag to query?

Sorry, Jack. I am at a bit of a loss. At least you know the problem is with the condition on the custom field and nothing else. You may have to reach out to Zendesk using the support chat.  

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 25. Juni 2022 09:47
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Bug when applying updater tag to query?

Jack So it looks like the DATE_DIFF condition is working as the DATE DIFF attribute is returning the expected results. Try adding a further new attribute to check we are finding the custom field. I...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 24. Juni 2022 15:16
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Bug when applying updater tag to query?

Jack Lets try adding the [Changes- Field Name] and [Update - Timestamp] to the body of our report. It may also be worth creating a new attribute for the DATEDIFF(...) formula and adding that too. T...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 24. Juni 2022 12:51
• 0 Stimmen

1. Community
2. Zendesk Suite Q&A
3. Bug when applying updater tag to query?

Jack Ticket and Users can have multiple tags. It is likely that your output is reflecting that. To filter by a tag, you need to create a custom attribute to check if the tag is included. So you can...

• Kommentar anzeigen
• Graeme Carmichael
• Erstellt 23. Juni 2022 07:37
• 1 Stimme