최근 검색


최근 검색 없음

Rafael Ramirez's Avatar

Rafael Ramirez

가입한 날짜: 2021년 4월 16일

·

마지막 활동: 2021년 10월 22일

팔로잉

0

팔로워

0

총 활동 수

9

투표 수

3

가입 플랜

1

활동 개요

님의 최근 활동 Rafael Ramirez

Rafael Ramirez님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

Indeed. I certainly hope Zendesk will stop ignoring this and start providing better support. It is hard to understand why what was an important and necessary feature was removed from their latest release.

댓글 보기 · 2017년 7월 13일에 게시됨 · Rafael Ramirez

0

팔로워

0

투표 수

0

댓글


Rafael Ramirez님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

That is disappointing indeed. Our organization relies heavily on Zendesk/JIRA integration and multi-brand does not fit our business model. It is hard to understand why an important feature on an older version which was working perfectly fine with multiple instances has been removed from the current version.

Zendesk, we do understand you do not have plans to support this feature but please, do listen to your customers and understand the need that some organizations have for it. We do pay for enterprise for a couple of our accounts and have multi-brand as an option but do not use it as it does not fit our needs. Do consider to bring this feature to your loyal customers who need it and are already paying for multiple accounts.

Thank you.

댓글 보기 · 2017년 6월 07일에 게시됨 · Rafael Ramirez

0

팔로워

0

투표 수

0

댓글


Rafael Ramirez님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

I agree with Jeanne. I understand Zendesk would prefer clients to move to a multi-brand option but it simply does not work for all clients. That is the reason we went for individual Zendesk accounts as opposed to multi-brand. Unless someone from Zendesk could explain further how multi-brand works. Could teams from each specific brand login to Zendesk and see and manage the content of the brand they work for only or could they see and change the contents of other brands as well? What about reporting, would each brand have its own reporting section or would they all be mixed together? What about existing content and history, would it be lost if moving to a multi-brand account?

There are too many factors involved that could easily compromise the current setup.

JIRA integration was working so well in the previous version. Why force people to look for other options? Maybe not all of your clients have a need for multiple accounts but those who do have suffered the impact of the removal of such an important feature.

댓글 보기 · 2017년 5월 02일에 게시됨 · Rafael Ramirez

0

팔로워

0

투표 수

0

댓글


Rafael Ramirez님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

We recently upgraded to JIRA 7 to find out that the latest JIRA app for Zendesk no longer supports multiple Zendesk subdomains. This is quite an issue for us as we have multiple Zendesk accounts that could have easily be linked to their respective JIRA project as Version 2 was able to do. 

I am surprised that the original message in this thread is from January 2015, has 6 comments, and as of April 2017, has no comment or response from Zendesk's staff.

This is quite important to us as we need to be able to link all of our subdomains to their respective JIRA project for escalations.

Will there be a solution to this? How soon? 

 

댓글 보기 · 2017년 4월 25일에 게시됨 · Rafael Ramirez

0

팔로워

0

투표 수

0

댓글


Rafael Ramirez님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Ticketing system (Support)

 

 

댓글 보기 · 2017년 4월 25일에 게시됨 · Rafael Ramirez

0

팔로워

0

투표 수

0

댓글