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 Jul 11, 2022

Advanced ReqIF Import tagging feature should include some way to identify affected modules

Advanced ReqIF import offers a nice feature that tags artifacts that already exist in the modules in the target environment, but that are not present in the incoming modules from the ReqIF package. However, the only way to determine which modules are affected by this scenario is to open every module you imported and filter for the tags; alternatively, the import report indicates URIs of the tagged artifacts (but not their module), so you could open each of those to find their module. If you are importing multiple modules, both of these approaches are quite tedious. It would be much more usable if the import operation identified modules where the tags were applied - either by tagging the modules themselves or even just listing them in the import report so the user knows where to look.
Idea priority Medium