Allow custom fields in Backlog Dataset
We maintain a sizeable backlog as we manage a lot of back-and-forth in dealing with certain customers. It would be highly advantageous to us to be able to slice and dice these by custom fields. This capability existed within GoodData, but appears to have been lost to us now in Explore.
-
I would also very much like this functionality.
-
This would hugely improve the value of the dataset.
-
This would be a massive benefit to our internal reporting.
-
This level of info would be precious! Our Backlog reports are handicapped, once custom fields are the base of our tickets operation!
-
Agree with all of the above comments. Custom fields are crucial to our team's workflow and we need a way to measure trends over time.
-
This would be hugely valuable, as aforementioned by others here.
Why can't backlog be filtered by Ticket form?
Is there a plan to add more ticket attributes to the backlog Explore data pool to be able to filter by? I attempted to do a calculation on Ticket Form within brands but the data set available to me is extremely limited.
Is Zendesk planning to add at least a few more attributes into the Backlog Explore dataset?
-
I would also like to have this functionality. Would be advantageous for our company
-
Just agreeing with all the comments and upvoting to get more traction. Totally want what Samantha's is asking too around Ticket form. Especially as it's a Standard Zendesk field.
Also want custom fields too.
-
Very very interested too !!!
-
Add ticket form please.
-
This is crucial for us
-
Can't come fast enough for us!
-
+1 We need this to accurately report our backlog using custom fields
-
Two years and no progress. Very disappointing...
-
Without this, there's basically no use case where this dataset is helpful for me personally. Would be great if this was available.
-
The backlog dataset would be extremely beneficial if it could be filtered on specific fields. For example, if the backlog is growing it would be helpful to filter (or add a row/column) by the On Hold Reason so we can determine which team is the cause of the backlog spike.
Please sign in to leave a comment.
16 Comments