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 Submitted
Categories Administration
Created by Guest
Created on Dec 3, 2025

Simplifying the process of identifying project, component, and stream details from skipped resources at the RM TRS level.

Current Scenario: At present, we can see the project details through TRS diagnostic page. However, when there are thousands of skipped resources, locating the relevant details becomes extremely challenging.

Expected Scenario: We need a more efficient method to quickly identify the associated project, component, and stream details. This will enable faster resolution of report data inconsistencies by running TRS validation specific to the project

Without this necessary improvement, the time it takes to ID a failing Report due to skipped resources associated with a project, component, and stream takes days leaving the customer of the failed report completely frustrated during that time. Also much time is wasted by support personnel chasing down what really is a defect to do impact analysis. 

So while skipped resources exist, these really are treated as unresolved defects. Since there is no commitment to rid the system of skipped resources, then its only reasonable to improve the identification and impact analysis. 

Of course better to eliminate skipped resources and avoid the whole thing 

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