Búsquedas recientes


No hay búsquedas recientes

Yanni's Avatar

Yanni

Incorporación 02 mar 2022

·

Última actividad 23 mar 2023

Seguimientos

0

Seguidores

0

Actividad total

24

Votos

10

Suscripciones

9

RESUMEN DE LA ACTIVIDAD

Última actividad de Yanni

Yanni hizo un comentario,

Comentario de la comunidad 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

Ver comentario · Publicado 09 sept 2022 · Yanni

0

Seguidores

0

Votos

0

Comentarios


Yanni hizo un comentario,

Comentario de la comunidad Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

Ver comentario · Publicado 05 abr 2022 · Yanni

0

Seguidores

1

Voto

0

Comentarios


Yanni hizo un comentario,

Comentario de la comunidad Feedback - Ticketing system (Support)

+1 vote to this

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

Ver comentario · Publicado 03 mar 2022 · Yanni

0

Seguidores

8

Votos

0

Comentarios


Yanni hizo un comentario,

Comentario de la comunidad Feedback - Reporting and analytics (Explore)

+1 we need this attribute

Ver comentario · Publicado 03 mar 2022 · Yanni

0

Seguidores

3

Votos

0

Comentarios


Yanni hizo un comentario,

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

Ver comentario · Editado 02 mar 2022 · Yanni

0

Seguidores

2

Votos

0

Comentarios