Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Richard Dawson
Beigetreten 16. Apr. 2021
·
Letzte Aktivität 22. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
11
Stimmen
0
Abonnements
9
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Richard Dawson
Richard Dawson hat einen Kommentar hinterlassen
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 #
Kommentar anzeigen · Gepostet 23. Aug. 2021 · Richard Dawson
0
Follower
2
Stimmen
0
Kommentare
Richard Dawson hat einen Kommentar hinterlassen
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.
Kommentar anzeigen · Gepostet 22. Apr. 2020 · Richard Dawson
0
Follower
0
Stimmen
0
Kommentare