Recherches récentes
Pas de recherche récente

Ben McCormack
Adhésion le 15 avr. 2021
·
Dernière activité le 22 oct. 2021
Suivis
0
Abonnés
0
Activité totale
6
Votes
2
Abonnements
2
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Ben McCormack
Ben McCormack a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 05 juil. 2018 · Ben McCormack
0
Abonnés
6
Votes
0
Commentaire
Ben McCormack a ajouté un commentaire,
+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.
Afficher le commentaire · Publication le 07 août 2017 · Ben McCormack
0
Abonnés
0
Votes
0
Commentaire