최근 검색


최근 검색 없음

Yanni's Avatar

Yanni

가입한 날짜: 2022년 3월 02일

·

마지막 활동: 2023년 3월 23일

팔로잉

0

팔로워

0

총 활동 수

24

투표 수

10

플랜 수

9

활동 개요

님의 최근 활동 Yanni

Yanni님이 에 댓글을 입력함

커뮤니티 댓글 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

댓글 보기 · 2022년 9월 09일에 게시됨 · Yanni

0

팔로워

0

투표 수

0

댓글


Yanni님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Help Center (Guide)

Same!! Upvoting this and following this request!

댓글 보기 · 2022년 4월 05일에 게시됨 · Yanni

0

팔로워

1

투표

0

댓글


Yanni님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

+1 vote to this

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

댓글 보기 · 2022년 3월 03일에 게시됨 · Yanni

0

팔로워

8

투표 수

0

댓글


Yanni님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Reporting and analytics (Explore)

+1 we need this attribute

댓글 보기 · 2022년 3월 03일에 게시됨 · Yanni

0

팔로워

3

투표 수

0

댓글


Yanni님이 에 댓글을 입력함

댓글Explore 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.

댓글 보기 · 2022년 3월 02일에 편집됨 · Yanni

0

팔로워

2

투표 수

0

댓글