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 Apr 4, 2025

Filter on attributes in artifact history

Context:
When browsing the history of the artifact, all of the modification appear, with no priorities. Every little modification is mixed with the important modifications.

Problem:
Some modifications are unimportant and cloud the important ones, that we need to analyze.

Impact:
Every time we have to analyze the history of a module, an artifact, or a changeset, we have to spend a lot of time on irrelevant evolutions. It is very frustrating for users, and raises the costs of impact analysis.

Goal of the idea:
To simplify impact analysis, reducing costs and user frustration

Why it is useful ?:
Impact analysis are usually done with urgency, every delay has a big impact on the costs and deadlines of programs. It is also a frequent activity in product lines contexts.

How should it work ?:
We would like to be able to filter the history, on which attributes have been modified. That way, we can quickly sort through the history and find the important modifications we are looking for.
It would be even better if we could read the full version of an artifact at the time of a modification. That way, when trying to reconstruct the order of modifications, we can easily see what version we were working on at past times, and not only what was modified. It could be accessed by clicking on a modification, for example.

Idea priority High
Needed By Month
  • Guest
    Apr 3, 2026

    Yes - this is something we would really love to see! It take forever to try and find the important details to trouble shoot an issue on a work item in the history tab because of all the noise with irrelevant informationÂ