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
Workspace IBM MAS - Mobile
Categories Service Requestor
Created by Guest
Created on Nov 27, 2025

The Similar Service Requests query should include SR's that I raised

An Operator raises a Service Request and nothing happens immediately. They still have the same problem so they raise what is effectively a duplicate SR, currently nothing appears in Similar Service Requests because the query excludes SRs where the user is both the Reported By and Affected By person. OK, they can be trained to check View Requests, but this needs to have a lot more information and then you are trying to visually spot that the record is a duplicate which is difficult, besides it could have a lot of records making that process more difficult still, so it is easier just to submit the duplicate SR.

After a week between raising the first SR and the duplicate SR, the user has probably forgotten that they had raised the same SR previously.

The whole purpose of showing Similar Service Requests is to stop duplicates being created. In which case the query should be extended to include where the user is both Reported By and Affected Person.

 

Idea priority Medium
Needed By Not sure -- Just thought it was cool