最近搜索


没有最近搜索

Anthony Stenhouse's Avatar

Anthony Stenhouse

已加入2021年4月16日

·

最后活动2024年1月22日

关注

0

关注者

1

活动总数

60

投票

12

订阅

25

活动概览

的最新活动 Anthony Stenhouse

Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

查看评论 · 已于 2024年1月22日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Adding our voice to this request. :+1:

查看评论 · 已于 2023年11月09日 发布 · Anthony Stenhouse

0

关注者

1

投票

0

评论


Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Amisha Sharma Thanks to you and the team for rolling this out. I've tested on our end and it appears to be working well.

查看评论 · 已于 2023年6月29日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Being able to add custom fields into the Search results would allow our team to hone in on target tickets when looking up a broad range of subjects. Is there any update on this as a roadmap item?

查看评论 · 已于 2023年5月26日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

评论Team members and groups

Thank you @... I've opened API Access to Export Team-Member Data.

查看评论 · 已于 2023年4月06日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 创建了一个帖子,

帖子 Developer - Zendesk APIs

Following the release of Exporting team-member data feature, having the ability to access this dataset programmatically via the API would be a great next step. Something along the lines of making one API call to generate the data and another to download the data after a period of time. This would avoid the multi-step journey via UI and email or maintaining scripts calling out to the User API.

Use Case: We try to maintain an up-to-date record of Zendesk Agents, including their Roles, Groups, and status. This information serves as a fall-back in the event of any user issues such as an unexpected role change. We currently grabs the necessary data from the Users API, however, we'd love a fully automated method for generating this data and the team-member export would be a great fit (if accessible via the API).

Implementing API access to this report will save users time creating (and maintaining) code which aims to do the same thing, allows for automated versioning of the output for long term storage and enhances overall efficiency.

已于 2023年4月06日 发布 · Anthony Stenhouse

5

关注者

5

投票

0

评论


Anthony Stenhouse 进行了评论,

评论Team members and groups

Hi @...,

We have code that pulls in data from the Users API and it does what we need, however, I'm more so looking for a way to automate generating this team-member data export.

Our current approach has a lot of moving parts, where as this approach looks like it could be one API call to generate the data and another to download the data after a period of time.

Is this do-able or is it on the road-map?

Thanks,

查看评论 · 已于 2023年4月04日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

评论Team members and groups

Can this be obtained via an API request?

I'd like to setup a daily/weekly export to monitor changes and to serve as a backup in the event we see group resets due to Okta issues.

查看评论 · 已于 2023年4月03日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Thank you Amisha Sharma, I've tested a few paths and all seem to be OK, this has resolved a huge blocker for us (and many others).

For adding images into the flow, I was able to get ![img](https://link.to/image) to work when using a snippet, but copy/pasting the image from disk to the webform worked just as well and will likely be the path I recommend.

I'll take this back internally and discuss with our teams about our next steps in moving to AW. I expect we'll do further internal testing and need to change some of our workflows, but I think we're on a much brighter path to success than we were before.

查看评论 · 已于 2023年2月21日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论


Anthony Stenhouse 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Amisha Sharma - Thanks for confirming the code blocks spacing issue has been resolved. I can confirm through testing:

The ability to support new lines via markdown is still an issue for us. If I do a CMD+SHIFT+V then the spacing is preserved but all other formatting is lost:

Some of our team also use text snippets to build out the base of their message, for example:

Hi {{ticket.requester.first_name}},

{Curser-Position-Automatically-Moves-Here}

Thanks,
Anthony

But when attempting to use this in AW it doesn't work due to lack of line break support:

There will be more examples of this use-case across the team, but I think this covers the majority.

The other issue with typing the command to insert image is currently not supported by the technology we use to power our editor. We are following up with them to include this in the supported commands and will update you once we make progress on this one. 

What's the editor name? Is there an issue that can be upvoted on their GitHub/GitLab page?

查看评论 · 已于 2022年11月15日 发布 · Anthony Stenhouse

0

关注者

0

投票

0

评论