Populating Problem Ticket Subject in Explore

I would like an update on this issue as well. This is a really bad look to be ignoring a pretty core functionality @zendesk  1901689631684 Can you please provide an update? Is this feature on the roadmap, or are you still ignoring your customers? I would much rather you peel an engineer of your AI efforts and put them on this.

Definitely need this to help streamline incident management

1901689631684 Is there any update on this please? It is really causing us a lot of additional manual work. It feels like the use of Problems could massively help but with the lack of ability to report and also only being able to add public comments to all tickets if you are solving the problem (rather than also being able to send progress updates) is making this functionality unusable.

I posted this elsewhere, but posting here as well:

+1 on this. I'm a prospective buyer who's currently demo'ing out Zendesk, and to me it seems like table stakes to have the ability to list out your known bugs (Problems) and at a glance, understand how many linked Incidents there are for each bug. I know you can do this by Problem ID, but that gives me no information at a glance because I don't know what bug a Problem ID corresponds to.

This may be a deal-breaker for us – we were really excited about switching to you guys.

Hi All, 
Please include this on your product roadmap. It would really help in Dashboard reporting. Thanks!

+1 For this, we use problem/incident relationship to organize product bugs and enhancements where we have 1 problem ticket under our internal org, and then link client incident tickets to that problem ticket. Without this, it makes reporting and organizing these tickets very difficult.

+1 to this. 

We have recently started using Problem/Incident feature in the hope that we will be able to gain deeper insights into what specific problems causes the most number of incidents etc. The ability to combine problem ticket ID, subject problem ticket and count of related incident tickets will be extremely crucial in the successful implementation of this feature.

Hi,

We appreciate you highlighting the need for a comprehensive reporting view that combines problem ticket IDs, the subject of problem tickets, and the count of related incidents in Zendesk Explore.

Your ability to prioritize workloads based on the volume of incidents associated with specific problem tickets is crucial for efficient problem resolution. We understand the challenge that the current limitations of COUNT(Tickets) and Count(incidents) pose in achieving this.

While this specific functionality is not currently available, rest assured that your detailed use case and the impact of this limitation on your business processes have been noted. We consider all customer feedback in our ongoing product development, and your request will be taken into account as we plan future Explore updates.

Thank you for taking steps to submit this as official feedback. Please continue engaging with the Zendesk Community for updates, discussions, and resources.

Any updates Zendesk? This ask has been requested since 2020, at least (see other feedback post sitting at 74 votes: https://support.zendesk.com/hc/en-us/community/posts/4409217044250-Problem-and-Incident-tickets-need-a-way-to-view-the-subject-and-detail-of-all-incident-tickets-against-a-problem-ticket-or-vice-versa) 

This is desperately needed.

Since we also work with the problem ticket workflow, maintaining Explore dashboards about problem tickets is quite a pain. Since the ticket subjects cannot be automatically populated in Explore, our Explore specialist has to continuously add the titles by hand, e.g. in the legend of a graph, otherwise, no one can make any use of these dashboards. I hope for an update regarding the future roadmap since problem tickets are such an essential feature and something we need to closely monitor in our dashboards.