최근 검색
최근 검색 없음

Trust Payments Ltd.
가입한 날짜: 2022년 6월 21일
·
마지막 활동: 2024년 4월 15일
팔로잉
0
팔로워
0
총 활동 수
24
투표 수
6
플랜 수
9
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Trust Payments Ltd.
Trust Payments Ltd.님이 에 댓글을 입력함
I agree with much of the comment above on missing features and note Export is not really discussed too much. Is this still due for General Release? When is General Release due?
댓글 보기 · 2023년 4월 26일에 게시됨 · Trust Payments Ltd.
0
팔로워
0
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
Exactly that, I agree with Tim. My previous post is still pending approval, I guess because I included an image. Here it is in text only:
Hey Erin, thanks for this. So are you saying that other parts of the reporting dataset for tickets, such as on the below image will dynamically reflect any custom statuses?
Are our custom statuses now going to be an attribute within the metric sets?
How about when we are reporting on ticket timings and their moving from one status to another - are they all now going to include the custom status where applicable?
댓글 보기 · 2023년 4월 25일에 편집됨 · Trust Payments Ltd.
0
팔로워
2
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
Hey Erin, thanks for this. So are you saying that other parts of the reporting dataset for tickets, such as on the below will dynamically reflect any custom statuses?
Are our custom statuses now going to be an attribute with the metric sets?
How about when we are reporting on ticket timings and their moving from one status to another - are they all now going to include the custom status where applicable?
댓글 보기 · 2023년 4월 25일에 편집됨 · Trust Payments Ltd.
0
팔로워
2
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
Trust Payments Ltd.님이 에 댓글을 입력함
I understand lots of people wanted this changed (and I agreed, as long as configurable by us which one - subject or requester - is displayed. Our teams are wholly used to the requester now and so we wanted to approach this change like any other. Upfront comms from Zendesk with date, we do internal comms, implementation is smooth.
But no - today, suddenly it's changed. No comms, no warning. No apparent configuration to change back to requester.
Zendesk, appreciate you finally responding to this thread and making changes, however this isn't good enough comms wise for us to manage our teams properly
댓글 보기 · 2023년 3월 07일에 게시됨 · Trust Payments Ltd.
0
팔로워
0
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
The original poster here seemed to include an image , which I'm unable to view on the post still...
Having read through the thread, I'm still confused about how I can have the following 2 KPIs (can be simple numbers rather than graphs). It's a simple dashboard and so I'm trying to achieve the following...
1. Tickets created (easy and in place using standard metric)
2. Of those tickets in KPI 1, which are currently SOLVED or CLOSED.
Everything I try seems to give me total crated / solved on any given time period, rather than KPI 2 being a subset of KPI 1.
Hope that's clear and that someone can help :-)
댓글 보기 · 2022년 6월 28일에 게시됨 · Trust Payments Ltd.
0
팔로워
0
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
Any update please Salvador Vazquez or @... - keen to understand latest as have just expanded use of ZD in our organisation. So, view will soon become a challenge for us. (cc Dermot Clerkin, account manager - and Ashley M from my side)
댓글 보기 · 2022년 6월 21일에 게시됨 · Trust Payments Ltd.
0
팔로워
0
투표 수
0
댓글
Trust Payments Ltd.님이 에 댓글을 입력함
Totally agree, this is a critical feature and is preventing us from creating efficient reporting processes internally. This coupled with no Explore API leaves us hand-tied to properly manage performance. Unusual for an enterprise level tool such as this and not something we were made aware of when buying the tool!
댓글 보기 · 2022년 6월 21일에 게시됨 · Trust Payments Ltd.
0
팔로워
2
투표 수
0
댓글