Admin - Trane Support (JH)

Tipene Hughes or Lydia C

Any recommendations on how I can modify your code to check the status of a custom checkbox field and disable the submit button when it is checked / unchecked? 

Hey all - I'm looking to implement something similar, but would like to disable the submit button based on the status of a custom property (specifically a checkbox) that is visible in the form. Does anyone have something they've already implemented?

Thank you for the suggestion Jacob, that worked for me!

I'm now trying to modify this slightly to calculate the average resolution time of these tickets, but can't quite figure it out. Do you have any recommendations to return only tickets that were solved same-day and the average first resolution time?

Elissa - 

My large enterprise organization has the same challenge as Jennifer's. The issue with the trigger you shared is that we have no way to identify what group the ticket previously belonged to, which is instrumental for the "group = support" action. We have many groups per brand that consist of very different groups of resources that support very different products and services. As such, we cannot just assume that a ticket belongs to a given group based on the brand for which the ticket was created (and channel being closed ticket) - we need to know which group or assignee was handling it. Are there any other ways?

As it stands right now, we are forced to tell our end users to create a new ticket when they attempt a follow-up, because the effort it would require to manually distribute these tickets to the appropriate groups would be cost prohibitive for our agents.

We depend on the auto refresh chrome extension (for Views) to meet our very demanding 10 minute first-reply SLAs. It stopped working a month ago and there is no feature native to the product to replace it. My organization needs this.