최근 검색
최근 검색 없음

Matt Toenjes
가입한 날짜: 2023년 2월 17일
·
마지막 활동: 2024년 10월 29일
팔로잉
0
팔로워
0
총 활동 수
9
투표
1
플랜 수
4
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Matt Toenjes
Matt Toenjes님이 에 댓글을 입력함
Tatsuro Nomura For your point 4. Exporting csv or excel file, this might be able to help you https://support.zendesk.com/hc/en-us/community/posts/8130491925530-New-request-list-experience-Export-csv-Button
However, I definitely agree this would be nice to have built-in feature!
댓글 보기 · 2024년 10월 29일에 게시됨 · Matt Toenjes
0
팔로워
0
투표 수
0
댓글
Matt Toenjes님이 에 댓글을 입력함
We just had the same problem after renaming groups in Zendesk. This is a horrible design flaw and causes tons of frustration when new groups have to be renamed. +1 to have this product defect fixed.
댓글 보기 · 2024년 8월 29일에 게시됨 · Matt Toenjes
0
팔로워
0
투표 수
0
댓글
Matt Toenjes님이 에 게시물을 만듦
Additional placeholders for custom fields.
It would be nice if there could be a placeholder for custom fields (and non-custom fields) to display a custom field's:
- Display name
- Description
- Title shown to customers
- Description shown to customers
For example, we have a custom fields that collects information for enhancement requests and sends it to an email address. For example there is a custom field called "What is the impact to your business?" and it is a free-text field to fill out.
While we are able to accomplish this by sending an email with this information:
What is the impact to your business? {{ticket.ticket_field_1234}}
But it would be nice if we could set it to something like:
{{ticket.ticket_field_1234.displayname}} {{ticket.ticket_field_1234}}
This way we would not need to change the email trigger if we ever update the Description or Display names.
2023년 6월 22일에 게시됨 · Matt Toenjes
0
팔로워
2
투표 수
0
댓글