Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Future consideration
Workspace Targetprocess
Created by Guest
Created on Sep 5, 2025

Better integration of extended domain entities added by Solutions with native entities

There are some very helpful solution packages in TP that add new entities.  However, these often integrate poorly with native entities.  For example, we added the Product and Component structure which provides product versions.   These add capabilities that are not available in releases.  Product Versions are very useful for software products, especially ones we aren't developing internally.  However, they also lack some of the capabilities that are available in Releases.  Currently, our instance has Products, Product Versions, Releases, Packages and Builds.  Releases and Builds are native, the others were added via Solutions.  They all relate to similar concepts but each has particular capabilities missing in others - Project/Process-specificity, Workflows, Assignments, relationships to other entities, Planned dates, ability to be seen as "Current" or "Past" - all of these differ among this set of entities. 

It would be so much more powerful if your Solutions team took the time to think through how these might work together.  Some of the Solutions seem to have been added to address some specific request, without thinking through (or documenting) how they would be incorporated into an existing data model.  This is further complicated by the limitations of all extensible domain entities (for example, a custom field of type TP entity can't use an Ext Domain, many of the automation conditions and actions don't work with these extensible domain entities, and they often cannot be used in lanes of views as might be wished for). 

In addition to improving the data model to better incorporate these, we would value better documentation on best practices in using these packages.  The Solution documentation is often very thin (and the quality varies from one solution to another).  It can be really difficult to get anyone to explain how they are intended to be used since the support people seem to not have information themselves about Solutions.

I know your team is up to improving this!

Idea priority High