Recherches récentes
Pas de recherche récente

Richard Dawson
Adhésion le 16 avr. 2021
·
Dernière activité le 22 oct. 2021
Suivis
0
Abonnés
0
Activité totale
11
Votes
0
Abonnements
9
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 Richard Dawson
Richard Dawson a ajouté un commentaire,
Here is how we found a way to do it.
Select tickets to edit [Link]
Step 1. Change ticket "Type" to Incident [even if this is already set to Incident.
Step 2. The "Linked problem" field appears for you to enter the Problem ticket #
Afficher le commentaire · Publication le 23 août 2021 · Richard Dawson
0
Abonnés
2
Votes
0
Commentaire
Richard Dawson a ajouté un commentaire,
In our case the Organization is much more important than the Requester and having the ability for multi-select at the organization level enables us to add comments and other automation via Triggers when tickets are generated. This will eliminate repetitive Ticket Field population as the info we want to drive while different for each organization it would be the same on each ticket for that specific Organization. Some of our sequesters are customers and vendors of our customers so we can't rely on the End User's account for consistency.
As it is now every ticket we create we have to look up this data and manually input.
Afficher le commentaire · Publication le 22 avr. 2020 · Richard Dawson
0
Abonnés
0
Votes
0
Commentaire