View all clashes related to a selected object

1. Problem to solve: There is no way to select an object in the iModel and see the clashes associated with it. The workflow only runs one way - selecting a clash row highlights the object but you cannot do the reverse. On large federated projects with tens of thousands of clashes across many clash jobs, this makes it impractical to understand the full clash picture for any given element.

2. User needs: Coordinators need to interrogate clashes object-by-object across all clash jobs in a project, because a single element (e.g. a communications duct) commonly appears in multiple jobs for different reasons (pavement clash, drainage clash, etc.).

3. High-level requirements:

• Selecting one or more objects in the iModel filters the Clash Detection list to clashes involving those objects.

• Filtering works across all clash jobs in the project, not just the active one.

• Each result indicates which clash job it came from.

• Multi-select supported; clear way to toggle the spatial selection filter off.

Reach: Likely applicable to most iTwin clash users industry-wide, as the limitation affects any project with overlapping clash jobs.

Impact: Fills a major workflow gap. Today, identifying every clash on a given object requires manually scanning thousands of rows across multiple jobs — often not feasible, so issues are missed. This change would turn a multi-hour manual cross-reference into a single click.

Business impact: Removes one of the most-cited frustrations with iTwin clash management on large projects, improving NPS and reducing the risk of teams reverting to other coordination tools (e.g. Navisworks) for clash review.

Prerequisites: User must have a federated iModel with at least one completed clash detection job.