Recent searches


No recent searches

Yanni's Avatar

Yanni

Joined Mar 02, 2022

·

Last activity Mar 23, 2023

Following

0

Followers

0

Total activity

24

Votes

10

Subscriptions

9

ACTIVITY OVERVIEW

Latest activity by Yanni

Yanni commented,

Community comment 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

View comment · Posted Sep 09, 2022 · Yanni

0

Followers

0

Votes

0

Comments


Yanni commented,

Community comment Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

View comment · Posted Apr 05, 2022 · Yanni

0

Followers

1

Vote

0

Comments


Yanni commented,

Community comment Feedback - Ticketing system (Support)

+1 vote to this

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

View comment · Posted Mar 03, 2022 · Yanni

0

Followers

8

Votes

0

Comments


Yanni commented,

Community comment Feedback - Reporting and analytics (Explore)

+1 we need this attribute

View comment · Posted Mar 03, 2022 · Yanni

0

Followers

3

Votes

0

Comments


Yanni commented,

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

View comment · Edited Mar 02, 2022 · Yanni

0

Followers

2

Votes

0

Comments