Add Job-to-Connection Mapping Visibility in the CP4D Jobs Tab

Cloud Pak for Data users and administrators need the ability to identify which project-level or platform-level connection is being used by each job directly from the CP4D Jobs tab. Currently, when reviewing jobs, there is no clear or centralized way to determine which connection a job depends on without manually inspecting.

This creates an operational visibility gap, especially in environments with many jobs and multiple shared connections. Administrators need to understand job-to-connection relationships for troubleshooting, access management, impact analysis, connection lifecycle management, and audit readiness.

The requested enhancement is to add clear connection visibility within the Jobs tab so users can quickly determine which connections are associated with each job.

Ideally, the Jobs tab should include a column, expandable details section, or related metadata view that shows:

• The connection name used by the job.

• Connection status, where available.

• Whether the connection is active, missing, deleted, expired, or inaccessible.

• Ability to filter or search jobs by connection name or connection type.

• Ability to export job-to-connection mapping details for audit or operational review.

This capability would help administrators quickly answer questions such as:

• Which jobs are using a specific connection?

• Which jobs will be impacted if a connection is changed, rotated, disabled, or deleted?

• Are any jobs failing because they rely on an expired, missing, or unauthorized connection?

• Which jobs depend on shared platform-level connections?

Adding job-to-connection mapping visibility in the CP4D Jobs tab would improve troubleshooting, reduce manual investigation, support better governance of shared connections, and make it easier to manage changes to data source credentials or connection assets across the platform.