Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

Yanni's Avatar

Yanni

Beigetreten 02. März 2022

·

Letzte Aktivität 23. März 2023

Folge ich

0

Follower

0

Gesamtaktivitäten

24

Stimmen

10

Abonnements

9

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von Yanni

Yanni hat einen Kommentar hinterlassen

Community-Kommentar Q&A - Objects, workspaces, and rules

Hi @Amie Brennan

Thank you for sharing the sample webhook. While your example is from string + ticket number for the value of a custom field. Is it possible to get the initial value from a certain text field instead?

Ex.
get the value of field #1 "4413122487577" and paste it to field #2 "4413122501657"

I'm using this one, and it gives me a parse error.

JSON Body:
{

"ticket": {

"custom_fields": [{"id": 4413122487577, "value":"id": 4413122501657}]

}

}



Another question:
Similar to your example, have you tried creating a webhook to get the ticket ID from a follow-up ticket?


The final goal is to create a webhook that will get the follow-up ticket ID and automatically set it as an incident / link to the problem ticket


Sorry for having so many questions :( but thank you in advance :)

Respectfully,
Yanni

Kommentar anzeigen · Gepostet 09. Sept. 2022 · Yanni

0

Follower

0

Stimmen

0

Kommentare


Yanni hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

Kommentar anzeigen · Gepostet 05. Apr. 2022 · Yanni

0

Follower

1

Stimme

0

Kommentare


Yanni hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

+1 vote to this

Definitely need it. It's a very basic feature to be honest.

Kommentar anzeigen · Gepostet 03. März 2022 · Yanni

0

Follower

8

Stimmen

0

Kommentare


Yanni hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Reporting and analytics (Explore)

+1 we need this attribute

Kommentar anzeigen · Gepostet 03. März 2022 · Yanni

0

Follower

3

Stimmen

0

Kommentare


Yanni hat einen Kommentar hinterlassen

KommentarExplore recipes

@Oliver White (Admin)

 
I agree completely with the above, received at is an important attribute which exists on the ticket data, so to not include this within Explore doesn't make a lot of sense to me. As above, I want to report on historic tickets which simply isn't possible via your suggested workaround.

_____________________________________________

Correct! We are also doing migration, and the said workaround is not applicable for all old tickets.

Workaround is retroactive, we are hoping for the availability of this attribute soon.

Kommentar anzeigen · Bearbeitet 02. März 2022 · Yanni

0

Follower

2

Stimmen

0

Kommentare