Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Ben McCormack
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 22. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
6
Stimmen
2
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Ben McCormack
Ben McCormack hat einen Kommentar hinterlassen
Not being able to link to a specific comment is a real pain.
For example, when I escalate to engineering, I have to say something like, "for the best summary of this issue, look for the comment that I left at [timestamp]". And do you know how I have to get that timestamp? I have to dig into the HTML of the page to grab the timestamp because the copy on the page is in relative time (e.g. "9 minutes ago"), which isn't helpful when trying to make an absolute reference.
Relative links that go to specific comments would fix this.
Kommentar anzeigen · Gepostet 05. Juli 2018 · Ben McCormack
0
Follower
6
Stimmen
0
Kommentare
Ben McCormack hat einen Kommentar hinterlassen
+1
Here's my use case:
I recently started doing an analysis where I wanted to understand where our customers came from. I have all of the data ready to go and I made custom fields to pipe the data into Zendesk. Then I discovered I can't update old closed tickets :(
We even have a process for piping our Zendesk data into a MySQL instance, so I was hoping to be able to lean on this process to write SQL queries against the data. However, because I can't update closed tickets, I'll have to create a table separate from my usual tables to do the analysis. Doable, but a pain.
Kommentar anzeigen · Gepostet 07. Aug. 2017 · Ben McCormack
0
Follower
0
Stimmen
0
Kommentare