최근 검색
최근 검색 없음

Stewart Armbrecht
가입한 날짜: 2022년 2월 01일
·
마지막 활동: 2023년 3월 17일
팔로잉
0
팔로워
0
총 활동 수
12
투표 수
3
플랜 수
5
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Stewart Armbrecht
Stewart Armbrecht님이 에 댓글을 입력함
Continuing to add to the heap of requests on this. The current solution is simply not working in our environment as most CC'd participants simply fail to check their CC'd queue and email notifications are lost in a sea of too many emails from Zendesk. We really need the ability to pull cc'd tickets into existing views and choose which columns to show.
댓글 보기 · 2023년 3월 17일에 게시됨 · Stewart Armbrecht
0
팔로워
1
투표
0
댓글
Stewart Armbrecht님이 에 게시물을 만듦
Recently, we have lost the ability to change the fields displayed for a Jira Issue when creating a Jira Issue in Zendesk.
Steps to Recreate:
- Click 'Create issue' in the Jira App as an Zendesk Admin
- Select a project and issue type.
- Click the 'Configure Fields' button
- Select a Field to display.
Expected Behavior: The Field is selected and displayed permanent for all users.
Actual Behavior: While the field is added to the form. The UI generates an error (below) and the field is not longer visible when you create the next issue in the same project and for the same issue type.
Any idea what could be causing this?
2022년 9월 09일에 게시됨 · Stewart Armbrecht
0
팔로워
4
투표 수
2
댓글
Stewart Armbrecht님이 에 댓글을 입력함
We have not migrated to this feature. Is there any documentation that would explain the legacy functionality around CCs? Specifically, when the system decides to send an email and to whom? We are seeing that some CCs are not getting emails and do not know why. Understanding this is important for us to understand what impact the migration will have. Thanks!
댓글 보기 · 2022년 4월 27일에 게시됨 · Stewart Armbrecht
0
팔로워
0
투표 수
0
댓글