최근 검색
최근 검색 없음

Dave Dyson (gmail)
가입한 날짜: 2022년 11월 11일
·
마지막 활동: 2025년 1월 17일
Zendesk alum - 11 years as customer support agent and manager, content marketing SME, and community management. Currently an Implementation Consultant at goenvoy.co
팔로잉
0
팔로워
1
총 활동 수
168
투표 수
20
플랜 수
77
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Dave Dyson (gmail)
Dave Dyson (gmail)님이 에 댓글을 입력함
In case anyone else is looking at this, I'm finding that if you format your #+number test using the code span or code block formatting options in the ticket composer, the number will not render as a ticket hyperlink.
댓글 보기 · 2025년 1월 17일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
I think the best way around this would be to put related reports into dashboardds, and then shared the dashboards: Sharing and publishing dashboards
댓글 보기 · 2024년 5월 18일에 게시됨 · Dave Dyson (gmail)
0
팔로워
1
투표
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
Thanks Jacob the Moderator for helping me to get this working – and just for future reference, here's how you'd get a clickable hyperlink of the ticket Subject that takes you to the ticket:
<https://yoursubdomain.zendesk.com/agent/tickets/{{ticket.id}}|{{ticket.title}}>
댓글 보기 · 2024년 4월 16일에 게시됨 · Dave Dyson (gmail)
0
팔로워
1
투표
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
I agree with Gareth Elsby Test, and additionally -- can you use higher-resolution screenshots? These are hard to read, even when you open them in a new tab and zoom in. Thanks!
댓글 보기 · 2024년 3월 15일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
Not sure - probably best to contact Zendesk Support in case they can look deeper into this: https://support.zendesk.com/hc/en-us/articles/4408843597850-Contacting-Zendesk-Customer-Support
댓글 보기 · 2024년 3월 09일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
Hi Gabi,
If it doesn't matter what the previous Group assignment was (in other words, you want to count all tickets moving to "the group" regardless of where they came from), then you should be able to omit all the "previous value" lines entirely. The recipe you based this on was looking for tickets that were moved from one specific group to a different specific group, so in that case the previous group was important.
With all your OR statements, most of those are going to ge true for any ticket moved to "the group", and with OR statements, only one clause has to be true for the whole thing to be true.
댓글 보기 · 2024년 3월 05일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
Hi Lloyd,
Unfortunately, you're probably not going to be able to do this in Explore -- although Organization domain is an attribute in the Tickets dataset, it's only going to be available when that organization is associated with a ticket. So if you have any organizations that aren't associated with tickets, they'll be invisible to Explore.
Your better bet will be to use the List Organizations API endpoint, and search for any results that include the following string:
"domain_names":[]
That will only be true for organizations that don't have a domain set.
댓글 보기 · 2024년 2월 29일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글
Dave Dyson (gmail)님이 에 댓글을 입력함
Hi Mark,
Help center language is determined by the user's browser settings:
댓글 보기 · 2024년 2월 29일에 게시됨 · Dave Dyson (gmail)
0
팔로워
0
투표 수
0
댓글