Recherches récentes


Pas de recherche récente

Yanni's Avatar

Yanni

Adhésion le 02 mars 2022

·

Dernière activité le 23 mars 2023

Suivis

0

Abonnés

0

Activité totale

24

Votes

10

Abonnements

9

APERÇU DES ACTIVITÉS

Dernière activité effectuée par Yanni

Yanni a ajouté un commentaire,

Commentaire de la communauté 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

Afficher le commentaire · Publication le 09 sept. 2022 · Yanni

0

Abonnés

0

Votes

0

Commentaire


Yanni a ajouté un commentaire,

Commentaire de la communauté Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

Afficher le commentaire · Publication le 05 avr. 2022 · Yanni

0

Abonnés

1

vote

0

Commentaire


Yanni a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)

+1 vote to this

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

Afficher le commentaire · Publication le 03 mars 2022 · Yanni

0

Abonnés

8

Votes

0

Commentaire


Yanni a ajouté un commentaire,

Commentaire de la communauté Feedback - Reporting and analytics (Explore)

+1 we need this attribute

Afficher le commentaire · Publication le 03 mars 2022 · Yanni

0

Abonnés

3

Votes

0

Commentaire


Yanni a ajouté un commentaire,

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

Afficher le commentaire · Modification le 02 mars 2022 · Yanni

0

Abonnés

2

Votes

0

Commentaire