최근 검색
최근 검색 없음

Kieran Thorpe
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2023년 7월 05일
팔로잉
0
팔로워
0
총 활동 수
43
투표 수
14
플랜 수
14
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Kieran Thorpe
Kieran Thorpe님이 에 댓글을 입력함
Sorry i know this is ages since you asked me to clarify but i missed your response.
as i understand it, Using a webhook will only apply at the point of a ticket update being submitted, this means that any fields we want to intelligently populate based on a previous fields answer cannot be set as required fields, in our cases there are also going to be scenarios where some answers result in it being populated but some that would not - however i would not then want agents to have to option to just leave the field blank.
댓글 보기 · 2023년 7월 05일에 게시됨 · Kieran Thorpe
0
팔로워
0
투표 수
0
댓글
Kieran Thorpe님이 에 댓글을 입력함
Id love to be able to do this too. Using the workaround above isn't feasible as that means I cant set the fields I want to be filled in as required opening us up to sloppy ticket logging.
John DiGregorio - Not sure I'm following what you mean? Could you explain in a little more detail?
댓글 보기 · 2022년 7월 21일에 편집됨 · Kieran Thorpe
0
팔로워
0
투표 수
0
댓글
Kieran Thorpe님이 에 댓글을 입력함
댓글 보기 · 2022년 5월 04일에 게시됨 · Kieran Thorpe
0
팔로워
0
투표 수
0
댓글
Kieran Thorpe님이 에 댓글을 입력함
Kieran Thorpe님이 에 댓글을 입력함
We also need this, it causes us a huge headache as our support team who triage requests and then need to be able to send tickets through to our dev team who work solely in Jira.
Without being able to attach files it makes it super hard for our dev team to verify, write acceptance criteria and do impact assessment with only partial information.
댓글 보기 · 2022년 3월 11일에 편집됨 · Kieran Thorpe
0
팔로워
0
투표 수
0
댓글
Kieran Thorpe님이 에 댓글을 입력함
We would also really like to see this, many of the other mentioned use cases are relevant to us. But from a support point of view, one of the key issues we have is with incident and problem management.
I'm currently stuck with countless incidents open as I wont allow the related problem ticket to be closed until the team have attached a full RCA. It gets messy using follow up tickets and is much easier to add the relevant information to the problem, unfortunately it can take some time to put this together and often the ticket is closed by the time this is done.
alternatively I have to have my agents manually closing the incidents down which defeats the object of the incident/problem linking in Zendesk. This is also made impossible with the current issues we face with bulk ticket updating due to the amount of fields we have available.
댓글 보기 · 2022년 3월 11일에 게시됨 · Kieran Thorpe
0
팔로워
5
투표 수
0
댓글
Kieran Thorpe님이 에 댓글을 입력함
Did product feedback ever get created for the fact all active fields are shown? In our case there are literally hundreds of fields spread across the various business functions that use them and when we come to bulk edit a ticket its almost unusable
댓글 보기 · 2021년 12월 08일에 게시됨 · Kieran Thorpe
0
팔로워
2
투표 수
0
댓글