Búsquedas recientes
No hay búsquedas recientes

Alisha (amaysim)
Incorporación 16 abr 2021
·
Última actividad 09 dic 2024
Seguimientos
0
Seguidor
1
Actividad total
40
Votos
22
Suscripciones
16
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de Alisha (amaysim)
Alisha (amaysim) hizo un comentario,
Hi there, That link on Translations brings me to a 404 - not found.
Ver comentario · Publicado 26 oct 2021 · Alisha (amaysim)
0
Seguidores
0
Votos
0
Comentarios
Alisha (amaysim) hizo un comentario,
We are very interested in seeing macros being available at a ticket updates data set level.
We want to measure more activity and highlight more information in events such as who is using which macros (most cases the agent / updater / person applying the macro will never historically be an assignee of the ticket).
I thought that adding tags would be the answer to this but it turns out that tags are not related to ticket updates data set and therefore update level attributes such as updater are also not available.
Is there any way to work around this or is anyone looking to add tags to an update data set level or make tags available as a text field change?
My use case is only one idea but so much more could be done with reporting on tags at update level.
Ver comentario · Publicado 26 ago 2019 · Alisha (amaysim)
0
Seguidores
2
Votos
0
Comentarios