最近搜索


没有最近搜索

Anton vh's Avatar

Anton vh

已加入2021年4月16日

·

最后活动2023年12月28日

Consultant and founder - Zendesk and other SaaS implementations - AVH Technologies - avhtech.com

关注

0

关注者

1

活动总数

9

投票

0

订阅

4

活动概览

的最新活动 Anton vh

Anton vh 进行了评论,

评论Writing formulas

I am struggling with the results that keep changing as the 'UPDATE - DATE' filter is updating. The DATE_FIRST_FIX returns the earliest date of updates within the filtered range. 

Usecase:

  • Ticket is updated and assigned to group A in January
  • Ticket is updated and assigned to another group in February
  • Ticket is updated and assigned to group A in March

If my UPDATE - DATE filters are set for the period January to March the first date = January which is correct. If my date filter is set from February to March my first date becomes March. I would like to have it always return in January. 

I have the following:

IF(
  [Changes - Field name]="group_id" 
  AND [Changes - New value]="groupid_a"
  AND DATE_FIRST_FIX([Update - Timestamp],[Update ticket ID],[Changes - Field name],[Changes - New value])=[Update - Timestamp]
  )
  THEN [Update - Timestamp]
  ENDIF

查看评论 · 已于 2022年2月04日 发布 · Anton vh

0

关注者

0

投票

0

评论


Anton vh 进行了评论,

社区评论 Feedback - Ticketing system (Support)

3 Years in the making...and still no solution. You have my vote.

查看评论 · 已于 2021年3月29日 发布 · Anton vh

0

关注者

0

投票

0

评论


Anton vh 进行了评论,

社区评论 Discussion - Tips and best practices from the community

Thanks, what about SLA metrics can they be brought across, and how many tickets can be migrated at a time?

查看评论 · 已于 2021年3月29日 发布 · Anton vh

0

关注者

0

投票

0

评论


Anton vh 进行了评论,

评论Accounts and billing

We are migrating our instance (merging with another instance as a separate brand) and want to keep our subdomain. Can we rename the current instance subdomain and use the current subdomain on the new instance (and brand)? If yes can it be done immediately? 

查看评论 · 已于 2021年3月23日 发布 · Anton vh

0

关注者

0

投票

0

评论


Anton vh 进行了评论,

社区评论 Discussion - Tips and best practices from the community

What would be the best way to deal with the fact that the ticket ids will be different from the original data? The issue is once you import all your tickets a new ticket id will be auto-assigned so any previous communication links, integrations, or references will be broken. If the 'id' value can be provided one could maybe force the old id where it has not already been used by the destination instance and at least limit the number of changes, or should one add the old id to the new external_id field (or a new "old_id" custom field or tag) to at least make it searchable?

查看评论 · 已于 2021年3月16日 发布 · Anton vh

0

关注者

0

投票

0

评论