최근 검색
최근 검색 없음

Tara Astbury
가입한 날짜: 2021년 5월 05일
·
마지막 활동: 2021년 10월 22일
팔로잉
0
팔로워
0
총 활동 수
13
투표 수
4
플랜 수
5
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Tara Astbury
Tara Astbury님이 에 댓글을 입력함
This feature is desperately needed for our group. I'm having a hard time justifying to our mgmt team why we keep the zendesk products without this basic functionality that it is severely lacking. do you have a planned ETA that we can look forward to this, since it was earlier commented that it was going to be released in 2012!
ideally we would prefer comment be moved over as well but i can see the logic behind people wanting to maintain those threads independently.
Our key points that would be most important to us:
- mark the thread as duplicate & link to the original thread (not in the comments but at the top where it's visible)
- carry over all of the votes (not counting duplicate votes from people that voted on both)
- once a thread is marked as duplicate, people can no longer comment or vote on the thread.
*on that note we would REALLY REALLY also like to be able to see who voted for each thread*
댓글 보기 · 2020년 1월 31일에 게시됨 · Tara Astbury
0
팔로워
1
투표
0
댓글
Tara Astbury님이 에 댓글을 입력함
Tara Astbury님이 에 댓글을 입력함
Agreed - I'm working with the trial trying to understand how to implement but the lack of customizing status's is making this difficult to match our processes.
Especially considering we are going to be integrating ZD with Jira, we need to have the ability to track tickets at different durations when it comes to passing back to development vs waiting on customer vs waiting on technical analysts.
댓글 보기 · 2017년 8월 22일에 게시됨 · Tara Astbury
0
팔로워
2
투표 수
0
댓글