Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Future consideration
Created by Guest
Created on May 24, 2022

Improved relationship explorer

WKC should have a relationship explorer that can easily visualize all links between any governance artifact all the way down to the source data

User Story

As a business user, I need to easily see how different governance artifacts are related to each other in a graphical format that provides the ability to navigate to any section of the hierarchy and shift the visual focus to that section.

1) When a user looks at an artifact, then they can explore and visualize any relationships between governance artifacts: (examples may not be inclusive)
• governance artifact to governance artifact
• governance artifact to data assets
• data assets to data assets
• governance artifacts to projects
• governance artifacts to catalogs
2) When a user chooses an artifact, it then becomes the central focus of the visual; the user is then able to move up, down or across the data hierarchy and expand or collapse the objects in the view.

Needed By Quarter