Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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
Categories Usability
Created by Guest
Created on May 27, 2026

Make content links in text artifacts configuration aware in the same way as trace links

When using the “ctrl+space” feature to find artifacts that are glossary terms in other components’ configurations in the same global configuration, the content link created by the tool refers to the initial stream of the component, rather than the configuration specified by the current global configuration.

This behaviour is inconsistent with the behaviour of the "glossary term search feature" triggered when pressing "ctrl+space"; by selecting "Search other components" the user is guided to add artifacts that are glossary terms in other components' configurations, but the URL selected is always the one from the initial stream. If the initial stream is used for only component properties and holds no artifacts, this will cause the content link to not work properly.

This means that the if a glossary term artifact is found in a sub-stream of the initial stream, the "glossary term search feature" finds it, but when the content link is created in the text field of the primary text of the artifact, neither the rich hover nor clicking the link will work.

Please see attached presentation for a step by step illustration of the issue.

Idea priority High
Needed By Yesterday (Let's go already!)