Búsquedas recientes
No hay búsquedas recientes

Svend Koustrup
Incorporación 15 abr 2021
·
Última actividad 22 oct 2021
Seguimientos
0
Seguidores
0
Actividad total
22
Votos
9
Suscripciones
7
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Svend Koustrup
Svend Koustrup hizo un comentario,
We also need this. When requesters quit their job in their organizations, i'd like to move his/her tickets ("requester" on those tickets) to another person in that organization. I could merge the user thus moving all tickets, but that also moves one user's details into another, which is not what I want. I also actually don't want to delete the end user, as old archived tickets should stay on that old user, so we can see who managed that old ticket.
Just add requester field to the Bulk edit ticket view, thanks :-)
Ver comentario · Publicado 19 mar 2021 · Svend Koustrup
0
Seguidores
1
Voto
0
Comentarios
Svend Koustrup creó una publicación,
Hi Zendesk
We often save SQL code as an internal note in tickets that we solve, and we use the Code Block editor tool to format the text "as code".
I do have one request (that I'm unsure if solveable in a web form)
We copy the code from SQL Server Management Studio and every tab is converted to a single space. It's still indented, but it's not as nice as in SSMS.
Could you do something to support tabs in the Code Block?
We need to copy the code into SSMS at a later point, if we have to do the same thing in another ticket, and I'd like the tabs to recuperated in SSMS. Tabs converted to 4 spaces or something could also work somehow.
Best regards
SvendK
Publicado 11 mar 2021 · Svend Koustrup
1
Seguidor
3
Votos
0
Comentarios
Svend Koustrup hizo un comentario,
@... what thoughts did the product manager have on this? (Previous comment - yeay, a permalink :D)
Ver comentario · Publicado 10 feb 2021 · Svend Koustrup
0
Seguidores
3
Votos
0
Comentarios
Svend Koustrup hizo un comentario,
Thanks Chandra, I've updated my post. I hope this can make someone reboot this 5 year old request :-)
Ver comentario · Publicado 10 feb 2021 · Svend Koustrup
0
Seguidores
3
Votos
0
Comentarios
Svend Koustrup creó una publicación,
Hi Zendesk Support.
UPDATE: Chandra Robrock commented below about a feedback post from 2016 asking for the same. And as you can see, you already made this a feature here in the Help Center system with Permalinks. Please, it's just about 15 characters addition in the code, and people has been waiting for this for 5 years now? Any reason NOT to implement this feature?
When referring to a ticket, sometimes I am referring to a specific comment. It would be awesome if you could just put a tag around each comment's timestamp with an ID for that specific comment. I guess it's the div.content's parameter data-comment-id.
The link should work for both Agents and Requesters ("users"?), just like normal ticket links do today, linking to the Agent url.
The below ticket is at https://flexpos.zendesk.com/agent/tickets/10060
Comment URL could be like this: https://flexpos.zendesk.com/agent/tickets/10060#706638506819
or
https://flexpos.zendesk.com/agent/tickets/10060#!comment=706638506819
It would be much appreciated and as I see it a quick thing to implement.
Thank you for amazing user experience - helping us give amazing customer experience :-)
Best regards
SvendK
Publicado 04 feb 2021 · Svend Koustrup
14
Seguidores
14
Votos
8
Comentarios
Svend Koustrup hizo un comentario,
We have a slight variation to this, but the same concerns applies.
Example:
- We get a support request via email from person@company.com.
- We reply.
- Then that person replies to the email but with their support@company.com email address.
This flags the reply as "not part of this conversation".
Also, does that person see this comment in the email replies and in the Help Center, or is their own replies invisible to them?
I understand that this, if not implemented, could be used as email relay spam, but if it's from the same organization, it should be safe.
Please, could we have an official update to this?
@... wrote this two years ago
There are some big changes being planned for the Support workflow and UI in the coming year, so I have flagged this thread as one of the ones for PM's to read through as they determine what the highest priority changes are. However up to this point it has not been deemed higher priority than other requests or plans.
Ver comentario · Publicado 12 jun 2020 · Svend Koustrup
0
Seguidores
1
Voto
0
Comentarios