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 Apr 16, 2024

[ELM]: Schedule TRS Feed validation across ELM Application

Context: We are using ELM to generate reports and kpi that we are delivering to our final customers. These reports must be consistent and we must trust on the generated data.

Problem: As we are modifying multiple times our data model on multiple projects (examples: artifact type, attributes, template,...), our users are telling us that their reports are inconsistent and there are missing/duplicate/outdated artifacts... So, we need to react to their issue and run manually the TRS feed Validation and LQE/LDX validation but it can take some times due to our internal process. By consequence, users are blocked for weeks as they can't generate their reports until the validation is done. So, they reject ELM and prefer do their report manually.

Solution: As a solution, we propose to schedule the TRS Feed Validation as we can do it for LQE/LDX data source validation.

Benefits: We will have validated data all the time and users will trust on the reporting. Plus, it will simplify the IT work and we won't be anymore in a reaction mode but in an anticipation mode.

Idea priority Urgent
Needed By Yesterday (Let's go already!)
  • Guest
    Reply
    |
    May 3, 2024
    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 does not fit our plans. There are a couple of reasons why this idea is rejected. It might sound like a good solution but it masks underlaying problem. TRS Validation should be used as temporary relief and all issues when they occur should be reported to the IBM support. Second, there is already an option to schedule TRS Validation using REST APIs. This REST API is added back in ELM 7.0 so that TRS provider side validation or repair can be scripted. Documentation for this API is available on any Jazz server under <application>/doc/scenarios. For example, for the Global Configuration application, you can see the API documentation under https://jazz.net/gc/doc/scenarios. See the TRS Validation API section. 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.