Query shows two entries for one ticket for First Internal Comment - Timestamp

Beantwortet

4 Kommentare

  • Chandra Robrock
    Community Moderator
    Most Helpful - 2021

    Hey Timothy! Mind confirming what metric(s) your query is looking at? I couldn’t tell based on your screenshot but that may provide some additional insight here.

    0
  • Timothy Pisarski

    Sure! The only Metric it has is COUNT(Tickets Created)

     

    0
  • Chandra Robrock
    Community Moderator
    Most Helpful - 2021

    Thanks for confirming! When querying the Ticket Updates dataset, each individual update would be a unique row. Since a ticket being created would be one update and then an internal comment being left on the ticket would be a different update, it is expected that you would see these timestamps on two different rows. I can't think of a way to get these two timestamps to appear on the same row, I'm afraid. 

    -1
  • Timothy Pisarski

    Thanks, Chandra. I'm not looking to have both timestamps on one row. If an Internal Comment Timestamp exists, then I only want to see that row in the table. If no Internal Comment Timestamp exists, then there should still only be one row for the ticket, but that column would be empty. Essentially, I only want to see a single row for each ticket.

    I've tried adding Internal Comments as a Metric but I end up with the same issue.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Powered by Zendesk