Ricerche recenti


Nessuna ricerca recente

Yanni's Avatar

Yanni

Data ingresso 02 mar 2022

·

Ultima attività 23 mar 2023

Seguiti

0

Follower

0

Attività totali

24

Voti

10

Abbonamenti

9

PANORAMICA ATTIVITÀ

Ultima attività di Yanni

Yanni ha commentato,

Commento nella community 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

Visualizza commento · Data ultimo post: 09 set 2022 · Yanni

0

Follower

0

Voti

0

Commenti


Yanni ha commentato,

Commento nella community Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

Visualizza commento · Data ultimo post: 05 apr 2022 · Yanni

0

Follower

1

Voto

0

Commenti


Yanni ha commentato,

Commento nella community Feedback - Ticketing system (Support)

+1 vote to this

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

Visualizza commento · Data ultimo post: 03 mar 2022 · Yanni

0

Follower

8

Voti

0

Commenti


Yanni ha commentato,

Commento nella community Feedback - Reporting and analytics (Explore)

+1 we need this attribute

Visualizza commento · Data ultimo post: 03 mar 2022 · Yanni

0

Follower

3

Voti

0

Commenti


Yanni ha commentato,

CommentoExplore 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.

Visualizza commento · Data ultima modifica: 02 mar 2022 · Yanni

0

Follower

2

Voti

0

Commenti