최근 검색
최근 검색 없음

Chris Devers
가입한 날짜: 2023년 5월 23일
·
마지막 활동: 2024년 2월 15일
팔로잉
0
팔로워
0
총 활동 수
7
투표 수
3
플랜 수
2
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Chris Devers
Chris Devers님이 에 댓글을 입력함
YES!
This was working for us until April, then poof, gone. Now, when anyone posts a Zendesk ticket URL to our Slack instance, we don't get an unfurl/preview of the ticket, which makes it way, way more annoying to have a troubleshooting conversation about the problem without having to flip back & forth between the two applications.
Another side benefit of the unfurling was the fact that the text from the Zendesk preview became searchable in Slack, so if we needed to search for cases where a particular customer, problem, etc had arisen, it was very fast to find such information. Now that’s gone.
PLEASE BRING THIS BACK!
댓글 보기 · 2023년 5월 23일에 게시됨 · Chris Devers
0
팔로워
2
투표 수
0
댓글
Chris Devers님이 에 댓글을 입력함
I’m seeing a version of the same problem: until a month or so ago, if someone posted a Zendesk support ticket URL into my employer’s Slack instance, the header of the support ticket would be unfurled, and we’d get a preview of the ticket right in Slack, which was great for seeing at a glance what the ticket was about, who it came from, etc. This stopped working for us in April, and after a bunch of back & forth with tech support folks at both Slack & Zendesk, it seems like the problem is that Slack deprecated an API that Zendesk was relying on, and the existing mechanism to do the link unfurling is now non-functional. It would be great to get this back, as it was a huge time saver.
댓글 보기 · 2023년 5월 23일에 게시됨 · Chris Devers
0
팔로워
0
투표 수
0
댓글