Customizing view of Incident tickets within Problem ticket

This is a very much needed improvement.

Hello all, 

We are working on capabilities to customize related lists for tickets and custom objects both. This means that we are working on adding it as a priority later in our planning cycle for 2025. We are going to leave this post open for comment to allow others to provide their feedback and use cases, however please note as is stated in our Community Guidelines that we can not commit to a release date on any one piece of feedback we receive in the community.

+1 for this one. We utilise this functionality a lot to track major issues and outages. Being able to see more useful data under the Incident view would assist greatly in cross-departmental collaboration. 

Upvote!

This feature would be a significant improvement. Our QA and Support teams use Zendesk for tracking bugs reported by customers in production.

When we confirm a bug, we create a Problem ticket and attach each reported incident. We would like to be able to customize the information that is shown in the incident ticket list. Namely, the organization of the requestor to allow us to quickly identify which customers are affected.

+1 to the above. I would like to add that the Linked tickets should also show in real time. I have noticed that if you were to update one of the tickets, it doesn't show it was updated in the Linked tickets view. For example, change a ticket to pending, it will still show as the previous status

Post Title: 

Customize the Incidents view

Feature Request Summary: 

When entering a Problem, then opening the related Incidents, I want to be able to filter/sort and customize this view.

Description/Use Cases: 

When our Product once in a while have a Problem (and sometimes multiple), and we see a lot of reports, we would like to collect them all and be able to mass reply to them.

Business impact of limitation or missing feature:

This is huge. We usually have at least one (not uncommon to have 5) "open" Problems at a time.

Other necessary information or resources:

Mirroring what other folks have said - at the very least we need the organization in there.

Bumping. Not being able to customize this view really limits the functionality. 

During a live critical incident, the Problem Ticket is mission control. As a support manager, I need to be able to tell our dev teams which customers, servers, applications, etc., are affected in real-time. 

This is such a big miss in requirements when rolling out the incident view from a problem ticket. The biggest use case for leveraging problem/incident tickets is wanting to stay organized and in control when there are widespread issues impacting your customers, and those issues can span across more than 1 customer in a lot of scenarios. Organization is a must-have column in this view to get a quick understanding of where the tickets are primarily coming from. This seems like such an easy improvement, and I'm disappointed to discover that this has been an outstanding request for nearly a year and a half. 

From a B2B service model perspective, it is essential to at least have in the views the organization.