Pesquisas recentes
Sem pesquisas recentes

Ben McCormack
Entrou em 15 de abr. de 2021
·
Última atividade em 22 de out. de 2021
Seguindo
0
Seguidores
0
Atividade total
6
Votos
2
Assinaturas
2
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Ben McCormack
Ben McCormack comentou,
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.
Exibir comentário · Publicado 05 de jul. de 2018 · Ben McCormack
0
Seguidores
6
Votos
0
Comentários
Ben McCormack comentou,
+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.
Exibir comentário · Publicado 07 de ago. de 2017 · Ben McCormack
0
Seguidores
0
Votos
0
Comentários