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 Not under consideration
Created by Guest
Created on May 26, 2025

Do not trunkate LPRIMARY_TEXT and DESCRIPTION attributes at LQE

We need to have full, not truncated content of LPRIMARY_TEXT and DESCRIPTION attributes available at LQE.

Currently the data is truncated to 4000 characters - we need to change that. Artifacts have quite often lot more characters. Extend limit to either no limit or at least to minimum 10000 chars.

We use LQE data extensively and due to lack of Module view filtering we have been instructed to use JRS. But all data must be there then. In 7.1 we get some improvement in filtering, but it is not covering all our use cases.

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Guest
    Jun 5, 2025
    As part of the review process, we strive to be transparent about our intentions with each enhancement suggestion. The IBM Engineering team has carefully reviewed this idea, and based on our understanding, it is not a valid use case as exporting LQE data using RB export functionality to act as ETL is not supported. Also, an increasing number of characters from 4k to a larger number could potentially impact performance. We suggest that you use an alternative way to get such data, either using DOORS Next or Publishing. Although we are closing this request, it will be kept in IBM's ideas repository.  We value your feedback and thank you for allowing us to partner with you in developing our products.
  • Guest
    May 28, 2025

    We are exporting data from LQE to other Data Warehouse, and in DW we organize it so that each Module is in own table with Hierarchy. Users can do their queries with SQL there. And to properly use and find data, ALL Content of Artifacts needs to be present, not only 4000 first chars.

    This solution prevents performance issues towards LQE as users do their queries mostly in DW.

  • Guest
    May 26, 2025
    Thank you for submitting idea. IBM Engineering team review board evaluated this request and determined it will need additional information to evaluate this request.

    JRS is used for statistical reporting to providing reports in tabular or chart view. These reports are intended for individual or team sharing. Could you explain your use case why would you need to see large amount of data represented in a table cell as they would not be possible to be represented as a chart?