Recherches récentes
Pas de recherche récente

Alisha (amaysim)
Adhésion le 16 avr. 2021
·
Dernière activité le 09 déc. 2024
Suivis
0
Abonné
1
Activité totale
40
Votes
22
Abonnements
16
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 Alisha (amaysim)
Alisha (amaysim) a ajouté un commentaire,
Hi there, That link on Translations brings me to a 404 - not found.
Afficher le commentaire · Publication le 26 oct. 2021 · Alisha (amaysim)
0
Abonnés
0
Votes
0
Commentaire
Alisha (amaysim) a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 26 août 2019 · Alisha (amaysim)
0
Abonnés
2
Votes
0
Commentaire