Pesquisas recentes
Sem pesquisas recentes

Jay Nelson
Entrou em 13 de mai. de 2021
·
Última atividade em 03 de ago. de 2022
Seguindo
0
Seguidor
1
Atividade total
19
Votos
2
Assinaturas
9
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 Jay Nelson
Jay Nelson comentou,
Any reply to April's comment on March 17th?
The Triggers and Macros allow for functions to add Followers easily, but now if a user has followed to many items or wants to unfollow tickets, they have the pain to open each and every ticket to perform this action. This is extremely time consuming.
When will at least Followers functions be added to the bulk edit functionality?
Exibir comentário · Editado 29 de jul. de 2022 · Jay Nelson
0
Seguidores
0
Votos
0
Comentários
Jay Nelson comentou,
But for a user to generate an OAuth token that matches their user and scope, we would need to enable password API auth. This would allow all users to generate a token during this time period.
Would your recommendation be as an Admin to leverage an API token and generate a user a personal OAuth token and scope then provide it to them?
The concern still comes back to ensuring that ticket visibility does not reach past that specific users Groups. Where as I have seen if I am generating this, will it carry my visibility or theirs.
Exibir comentário · Publicado 09 de mar. de 2022 · Jay Nelson
0
Seguidores
0
Votos
0
Comentários
Jay Nelson criou uma publicação,
Currently today Zendesk API Tokens do not offer enough security to allow non-admin teams to have access to tokens. As Zendesk does not validate a specific user to a token, or what a token has permission to do, all tokens are Admin level.
This is caused by a user only needing to know an admin email address and the token. If they replace their email with the admin email, they are now an Admin instead of the role that was designated to their user.
Publicado 08 de mar. de 2022 · Jay Nelson
7
Seguidores
9
Votos
8
Comentários
Jay Nelson criou uma publicação,
Currently triggers can source Requester Custom Fields as part of their conditions. It would be great to source Current User Custom Fields as part of the available rules.
Example: A user to fully disable their email based notifications if they selected Email Type to None.
Publicado 08 de mar. de 2022 · Jay Nelson
3
Seguidores
4
Votos
1
Comentário
Jay Nelson criou uma publicação,
We often find the need for different trigger handling based on users groups. This means that the 'Current user is (agent)' is to broad of a condition.
Example - Having an action on if the current user is part of support vs if the current user is part of the sales team.
It would be nice if there was an available condition for if the current user belongs to a group.
Publicado 08 de mar. de 2022 · Jay Nelson
8
Seguidores
7
Votos
4
Comentários
Jay Nelson comentou,
@Simon you need to add the /hc/en-us/ to ensure you are navigating to the help center.
Exibir comentário · Publicado 22 de dez. de 2021 · Jay Nelson
0
Seguidores
0
Votos
0
Comentários
Jay Nelson comentou,
It would also be useful if Zendesk offered a Chrome extension that would allow for ticket links opened outside of the existing Zendesk UI to join into the same Zendesk browser tab.
The idea that Zendesk has a single tab for tickets is quite misleading when tickets are more frequently opened from outside of the UI.
Exibir comentário · Publicado 01 de set. de 2021 · Jay Nelson
0
Seguidores
1
Votos
0
Comentários
Jay Nelson comentou,
Will there ever be support for pathing on the host mapping? This would allow for usage of multiple tools during transitions and make the platform more versatile.
https://subdomain.domain.com/>
Exibir comentário · Publicado 08 de abr. de 2021 · Jay Nelson
0
Seguidores
1
Votos
0
Comentários