最近の検索
最近の検索はありません

Dave Dyson
参加日2024年3月14日
·
前回のアクティビティ2025年2月07日
Zendesk Admin team at Samsara, Implementation Consultant at Envoy (goenvoy.co), Zendesk Community Moderator, Zendesk alum.
フォロー中
0
フォロワー
0
合計アクティビティ
25
投票
8
受信登録
8
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Dave Dyson
Dave Dysonさんがコメントを作成しました:
Agnieszka Czajka Awesome, thanks for the update and we'll be looking forward to it!
コメントを表示 · 投稿日時:2024年6月06日 · Dave Dyson
0
フォロワー
0
投票
0
コメント
Dave Dysonさんがコメントを作成しました:
Agnieszka Czajka hi, is there a rough timeline on when the “next version” that will allow other (presumably custom) roles to change an agent's status?
We have the Admin role locked down to the team that controls the overall setup of our Zendesk instance, but the teams that manage the agents (including monitoring their statuses) is completely separate. So we're in the position of choosing between:
- Granting full Admin access to teams that shouldn't have it
- Increasing red tape and the admin team's workload by asking the WFM team to ask us to change agent statuses when needed
- Saying “sorry” to the WFM team and making them depend on idle timeout which affects metrics.
Thanks for any timeline you might be able to provide!
コメントを表示 · 投稿日時:2024年6月06日 · Dave Dyson
0
フォロワー
0
投票
0
コメント
Dave Dysonさんがコメントを作成しました:
Alina Wright Is there any update on this? We keep tight control over who can manage Zendesk settings (business rules, forms, fields, roles, etc.), but there are times when It would be very useful to allow someone to view the settings without being able to change them.
コメントを表示 · 投稿日時:2024年5月24日 · Dave Dyson
0
フォロワー
0
投票
0
コメント
Dave Dysonさんがコメントを作成しました:
We have a fairly complex set of SLA policies, and it would be helpful to be able to create a view showing tickets that have a specific SLA so be we make sure it's working as intented, and to create a view of tickets that have *no* SLA applied to them, so we can determine why that's the case. Thanks!
コメントを表示 · 投稿日時:2024年5月08日 · Dave Dyson
0
フォロワー
0
投票
0
コメント
Dave Dysonさんがコメントを作成しました:
What will the expected behavior be if the original Group has been deleted, or the original assignee is no longer an Agent?
コメントを表示 · 投稿日時:2024年3月22日 · Dave Dyson
0
フォロワー
2
投票
0
コメント
Dave Dysonさんが投稿を作成しました:
When the API requests breakdown dropdown selector is set to Dailly or Weekly, the Callers and endpoints dropdown can be used to select a specific day or week, and the three tables beneath will refresh to show numbers for that time period.
When the API requests breakdown dropdown selector is set to Yesterday / Hourly, the Callers and endpoints dropdown lists hourly windows, but the tables don't seem to refresh.
More strangely, when I have the API request dropdown set to "Last 7 days" / "Hourly", then select an hourly window, the table are responsive the first time I choose an hourly window. Choosing a different hourly window has not further effect - the table contents don't change. But if I choose "Last 7 days" again from "Callers and endpoints", it adds another row to the "Top 5 callers by volume" table (only that table, the other two tables are unaffected). Every time you select an hourly window after that, nothing will happen, but if you choose "Last 7 days" again it will add another row. You can repeat the process, adding more and more rows, and the extra rows don't go away until you refresh the entire browser page.
投稿日時:2024年3月14日 · Dave Dyson
0
フォロワー
3
投票
2
コメント
Dave Dysonさんがコメントを作成しました:
I can see that choosing a time in the dropdown below the chart highlights the bar it corresponds do, but it would be more useful imho for it to work the other way -- select a bar and that chooses the value the in dropdown for you.
コメントを表示 · 投稿日時:2024年3月14日 · Dave Dyson
0
フォロワー
0
投票
0
コメント
Dave Dysonさんが投稿を作成しました:
Currently, when the API requests breakdown is set to Hourly, the time-axis labels are each long enough that it can be difficult or impossible to determine which vertical bar they correspond to. Conversely, the "tool tip" that appears when you hover over an individual bar shows the date (useful when the chart is set to show daily info), but not the timeframe for that bar (when set to hourly).
This makes it challenging to determine when exactly any API usage spikes are occurring.
(It'd be even better if clicking on one of the bars would immediately give you a breakdown of which endpoints and users are contributing to that time period's usage)
編集日時:2024年3月14日 · Dave Dyson
0
フォロワー
1
投票
1
コメント
Dave Dysonさんがコメントを作成しました:
100% agree, this would be super useful:
- drill in on a specific endpoint to see which users have been calling it the most
- drill in on a specific user to see which endpoints they've been using the most
コメントを表示 · 投稿日時:2024年3月14日 · Dave Dyson
0
フォロワー
2
投票
0
コメント