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

Jay Nelson
参加日2021年5月13日
·
前回のアクティビティ2022年8月03日
フォロー中
0
フォロワー
1
合計アクティビティ
19
投票
2
受信登録
9
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Jay Nelson
Jay Nelsonさんがコメントを作成しました:
Any reply to April's comment on March 17th?
The Triggers and Macros allow for functions to add Followers easily, but now if a user has followed to many items or wants to unfollow tickets, they have the pain to open each and every ticket to perform this action. This is extremely time consuming.
When will at least Followers functions be added to the bulk edit functionality?
コメントを表示 · 編集日時:2022年7月29日 · Jay Nelson
0
フォロワー
0
投票
0
コメント
Jay Nelsonさんがコメントを作成しました:
But for a user to generate an OAuth token that matches their user and scope, we would need to enable password API auth. This would allow all users to generate a token during this time period.
Would your recommendation be as an Admin to leverage an API token and generate a user a personal OAuth token and scope then provide it to them?
The concern still comes back to ensuring that ticket visibility does not reach past that specific users Groups. Where as I have seen if I am generating this, will it carry my visibility or theirs.
コメントを表示 · 投稿日時:2022年3月09日 · Jay Nelson
0
フォロワー
0
投票
0
コメント
Jay Nelsonさんが投稿を作成しました:
Currently today Zendesk API Tokens do not offer enough security to allow non-admin teams to have access to tokens. As Zendesk does not validate a specific user to a token, or what a token has permission to do, all tokens are Admin level.
This is caused by a user only needing to know an admin email address and the token. If they replace their email with the admin email, they are now an Admin instead of the role that was designated to their user.
投稿日時:2022年3月08日 · Jay Nelson
7
フォロワー
9
投票
8
コメント
Jay Nelsonさんが投稿を作成しました:
Currently triggers can source Requester Custom Fields as part of their conditions. It would be great to source Current User Custom Fields as part of the available rules.
Example: A user to fully disable their email based notifications if they selected Email Type to None.
投稿日時:2022年3月08日 · Jay Nelson
3
フォロワー
4
投票
1
コメント
Jay Nelsonさんが投稿を作成しました:
We often find the need for different trigger handling based on users groups. This means that the 'Current user is (agent)' is to broad of a condition.
Example - Having an action on if the current user is part of support vs if the current user is part of the sales team.
It would be nice if there was an available condition for if the current user belongs to a group.
投稿日時:2022年3月08日 · Jay Nelson
8
フォロワー
7
投票
4
コメント
Jay Nelsonさんがコメントを作成しました:
@Simon you need to add the /hc/en-us/ to ensure you are navigating to the help center.
コメントを表示 · 投稿日時:2021年12月22日 · Jay Nelson
0
フォロワー
0
投票
0
コメント
Jay Nelsonさんがコメントを作成しました:
It would also be useful if Zendesk offered a Chrome extension that would allow for ticket links opened outside of the existing Zendesk UI to join into the same Zendesk browser tab.
The idea that Zendesk has a single tab for tickets is quite misleading when tickets are more frequently opened from outside of the UI.
コメントを表示 · 投稿日時:2021年9月01日 · Jay Nelson
0
フォロワー
1
投票
0
コメント
Jay Nelsonさんがコメントを作成しました:
Will there ever be support for pathing on the host mapping? This would allow for usage of multiple tools during transitions and make the platform more versatile.
https://subdomain.domain.com/>
コメントを表示 · 投稿日時:2021年4月08日 · Jay Nelson
0
フォロワー
1
投票
0
コメント