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 Performance
Created by Guest
Created on Nov 24, 2022

Need Paging for Work Item History to prevent System overload because of large number of history

There should exists a possibility to load the history in pages with a definable number of entries per page. Similar to query result page.

We see huge performance problems with opening Work items, when the History is very huge. E.g. 500+ history entries.

If many users at same time are opening such work items, the system load goes dramatically up what brings the server near to unresponsiveness.

History at all is not well scaling for such an enterprise system. Loading one entry needs 500+milliseconds.

The Work Around to limit the number of history entries is not a real solution, because there is no possibility to see all changes if needed.

Because we had several time system outage because of this problem, this is more a architectural issue and this Idea is more a Work Around to prevent the bad performance issue.

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Guest
    Reply
    |
    Dec 13, 2022

    Several CCM enterprise customers are running into this issue. Due to poor implementation of RTC WI history we are unable to prevent CCM crashes. Can this be looked at as a priority please?

  • Guest
    Reply
    |
    Nov 28, 2022
    The EWM RFE Review board looked at this and decided to keep it on the Backlog as an uncommitted candidate for a future release.