Collin C
-
Total activity73
-
Last activity
-
Member since
-
Following0 users
-
Followed by0 users
-
Votes29
-
Subscriptions23
Activity overview
Latest activity by Collin C-
Collin C commented,
This becomes even worse if you're reporting on multiple multi-select fields, because the duplication compounds. Like, every option of field 2 will be listed next to each option of field 1, like: Ti...
-
Collin C commented,
Why is the bookmark component important to you? What is the use case where this feature is most needed? How frequently do you use it? Bookmarks are essential for creating easy-to-use dashboards w...
-
Collin C commented,
Is there a keyword for searching only the initial comment of a ticket? In all other contexts this is called the "description," but in search this seems to include any subsequent comments on the tic...
-
Collin C commented,
+1, me from 3 years ago. Again had a big issue caused by how Zendesk handles target failures.
-
Collin C commented,
I understand that the internal terms could be confusing to end-users, but I'm in favor of some configuration options so admins can use the terms best suited for their business. For example, "solved...
-
Collin C created a post,
Feature Request: Allow navigation between form editor and form conditions
Feature Request Summary: Currently, you can only view a form's conditions from the ⋮ button on the main forms page. It would be better if you could also access these while editing the form's fiel...
-
Collin C commented,
Yes, this is the one thing I miss from hub-and-spoke. You can prevent agents from viewing tickets outside of their current groups, but I haven't ever seen an instance where it made sense to apply t...
-
Collin C commented,
Hi James, good to know. My use case is related to agent management. For example, if I need to update a property on multiple agents, my workflow is to go down the list, searching the email address w...
-
Collin C created a post,
Search results for user-specific queries should default to "users" tab instead of "tickets"
When searching with user-specific terms like "role" or "type:user," the search results should default to the "users" tab instead of "tickets," which would always have 0 results. An extra click is a...
-
Collin C commented,
Is there a way to get this calculated attribute to work like a "real" timestamp, for filtering? It seems like it's not possible to have a "past 7 days" type time filter based on this attribute.