Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Under review
Workspace StreamSets
Created by Guest
Created on Aug 26, 2025

UI Modifications: Job details visible on engine details page and also on logs. Data collector details visible on Job instance page.

The customer wanted following modifications on the Platform UI:
1. On the engine details page, under running pipelines section, currently only the pipeline details are shown in UI, such as pipeline name, type, status, last reported, etc. The customer wanted to have an additional column displaying "job name" associated with the pipeline. They also wanted to add "table name" if possible (For example, which table it is loading data from). This is important because if multiple jobs are running across same pipeline, it shows the same pipeline name appear multiple times in that section without giving the clarity of which jobs are running along with it. 
2. On the same engine detail page, the customer also wanted to have a right click setting to open the pipeline link into a new tab. The reason this is required because currently if they click on the pipeline link it takes them to job instance page --> monitor job (and check further details). Because the right click -open to new tab is not available they have to go back again to check on the second pipeline to check on the job details and monitoring. 
3. On the engine page, logs section, the customer wanted to have job details shown along with the pipeline details. Currently only pipeline names are visible on the logs.
4. On the Job Instance page, currently jobs and associated labels are shown along with version, last modified on, job status, pipeline status. If there are multiple prod data collectors running and due to failover the data collector changes, there is no way to identify which data collector its currently running on from the job instance page unless you click on the job and go on the next page to check it. The customer wanted to check that from job instance page directly. Having additionally columns such as, current data collector, last data collector the job was running on, this would be helpful in debugging and troubleshooting making it more efficient and less time consuming process due to switching pages on the UI. 

Needed By Quarter
  • Guest
    Oct 7, 2025

    The customer also wanted to get the UI with collector names on pipeline canvas, and in the job section, they wanted to see the ID along with the names of the jobs. Basically, the ID's are not very helpful to understand what job/engine/collectors its running on. Henceforth, having the names along with id's will be beneficial.