When a map element (submap or host group) shows a problem indicator inherited from a nested submap, provide a direct navigation action from that problem to the map where the triggering host actually resides – not just the immediate child submap.

Problem

Today, clicking a submap element's problem indicator opens that submap. If the actual problem is several levels deeper, the operator has to manually navigate submap-by-submap to find where it lives. On a multi-level topology this is slow during an active incident – exactly when speed matters most.

Proposed behavior

• In the map element's problem popup/menu (the existing "Status problem" hover/click menu), when the underlying problem originates in a nested submap rather than the current map, add a link/action such as "Go to source map" that navigates directly to the deepest map on which the problem-triggering host is actually placed.
• If a host appears on multiple maps, list all of them (similar to how "Go to submap" already works when multiple submaps are linked) and let the user choose.

Use case

NOC context: an on-call engineer sees a critical indicator on a regional overview map. Instead of clicking through 3–4 layers of "Go to submap" to find the actual host, one click takes them straight to the map where that host lives, cutting time-to-diagnosis during an active incident.

Related issues

• ZBXNEXT-3260 – related context on submap status highlighting behavior.