최근 검색
최근 검색 없음

Ahmed Esmat
가입한 날짜: 2021년 4월 16일
·
마지막 활동: 2022년 11월 07일
팔로잉
0
팔로워
0
총 활동 수
57
투표 수
20
플랜 수
22
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Ahmed Esmat
Ahmed Esmat님이 에 댓글을 입력함
Hello,
We are the post trigger for status updates and it is working fine when the Jira issue is linked to a single Zendesk Ticket. However, when we link multiple Zendesk tickets, none of them gets updated when the Jira is updated. Is there a solution or a workaround to this?
Regards,
Ahmed
댓글 보기 · 2022년 11월 07일에 게시됨 · Ahmed Esmat
0
팔로워
0
투표 수
0
댓글
Ahmed Esmat님이 에 게시물을 만듦
lookup relationship fields is a great feature, but not fully integrated in workflows (macros, triggers, and automations). I have done some testing and found out If it is of user type:
- Cannot be used in views to filter on “(current user)”
- Cannot be used in trigger actions to send emails
- Cannot be sent an email in automations
Hope this is considered as an immediate requirement!
2022년 10월 06일에 게시됨 · Ahmed Esmat
2
팔로워
6
투표 수
2
댓글
Ahmed Esmat님이 에 댓글을 입력함
That is what I am looking for. But I have done some testing and found out If it is of user type:
- Cannot be used in views to filter on “(current user)”
- Cannot be used in trigger actions to send emails
- Cannot be sent an email in automations
So, that is not a complete solution/feature!
Is there any solution to this?
댓글 보기 · 2022년 10월 09일에 편집됨 · Ahmed Esmat
0
팔로워
3
투표 수
0
댓글
Ahmed Esmat님이 에 게시물을 만듦
It is required to extract the integration log messages along with the details for analysis and reporting. This is expected to be done through both the UI and API calls.
They can only be browsed here:
https://.zendesk.com/admin/apps-integrations/integrations/logs
2022년 9월 02일에 게시됨 · Ahmed Esmat
0
팔로워
1
투표
0
댓글
Ahmed Esmat님이 에 댓글을 입력함
"In a upcoming release, this will change so that views will use the schedule that is applied to the ticket."
What is the ETA?
댓글 보기 · 2022년 6월 10일에 게시됨 · Ahmed Esmat
0
팔로워
0
투표 수
0
댓글
Ahmed Esmat님이 에 댓글을 입력함
The ability to edit closed tickets is extremely needed to be able to alter ticket fields values and tags. Use cases include modifying custom field values when they change, and correcting wrong values. Another use case is switching a custom ticket field type from free text to a drop-down field.
댓글 보기 · 2022년 3월 29일에 게시됨 · Ahmed Esmat
0
팔로워
3
투표 수
0
댓글
Ahmed Esmat님이 에 댓글을 입력함
The ability to edit closed tickets is extremely needed to be able to alter ticket fields values and tags. Use cases include modifying custom field values when they change, and correcting wrong values. Another use case is switching a custom ticket field type from free text to a drop-down field.
댓글 보기 · 2022년 3월 29일에 게시됨 · Ahmed Esmat
0
팔로워
7
투표 수
0
댓글
Ahmed Esmat님이 에 댓글을 입력함
Adding a ticket tag that starts with "jira_" also adds a label to the linked Jira issues. But how can it be removed from Jiras when removing it from the ticket?
댓글 보기 · 2022년 3월 23일에 게시됨 · Ahmed Esmat
0
팔로워
0
투표 수
0
댓글
Ahmed Esmat님이 에 게시물을 만듦
We need a custom ticket field that lists the agent groups and names similar to the Assignee field. This would help if consultancy is needed from L3 or Dev teams without re-assigning the tickets. This is different from Follower since it may contain many other internal users and cannot filter on a single value.
2021년 11월 02일에 게시됨 · Ahmed Esmat
2
팔로워
1
투표
1
댓글