Recent searches
No recent searches
![Jay Nelson's Avatar](https://secure.gravatar.com/avatar/ed5a037cf26a40385633a18cca627a73?default=https%3A%2F%2Fassets.zendesk.com%2Fhc%2Fassets%2Fdefault_avatar.png&r=g)
Jay Nelson
Joined May 13, 2021
·
Last activity Aug 03, 2022
Following
0
Follower
1
Total activity
19
Votes
2
Subscriptions
9
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Jay Nelson
Jay Nelson commented,
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?
View comment · Edited Jul 29, 2022 · Jay Nelson
0
Followers
0
Votes
0
Comments
Jay Nelson commented,
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.
View comment · Posted Mar 09, 2022 · Jay Nelson
0
Followers
0
Votes
0
Comments
Jay Nelson created a post,
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.
Posted Mar 08, 2022 · Jay Nelson
7
Followers
9
Votes
8
Comments
Jay Nelson created a post,
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.
Posted Mar 08, 2022 · Jay Nelson
3
Followers
4
Votes
1
Comment
Jay Nelson created a post,
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.
Posted Mar 08, 2022 · Jay Nelson
8
Followers
7
Votes
4
Comments
Jay Nelson commented,
@Simon you need to add the /hc/en-us/ to ensure you are navigating to the help center.
View comment · Posted Dec 22, 2021 · Jay Nelson
0
Followers
0
Votes
0
Comments
Jay Nelson commented,
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.
View comment · Posted Sep 01, 2021 · Jay Nelson
0
Followers
1
Vote
0
Comments
Jay Nelson commented,
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/>
View comment · Posted Apr 08, 2021 · Jay Nelson
0
Followers
1
Vote
0
Comments