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.

Add a new idea Subscribe
Status Future consideration
Workspace IBM Engineering - Systems Design Rhapsody/RMM
Categories Rhapsody Client
Created by Guest
Created on Nov 14, 2019

RELATED IDEAS

Metadata updates introduced by model changes should be easily identified in RTC client

When a user makes a change in a Rhapsody RMM model that results in metadata changes to other files NOT modified by the user, those files will appear in the RTC client as outgoing changes that will be included in the change set and delivery. For each such file, the user needs an easy way to identify that this outgoing change only contains metadata and thus it is safe to include that file with the delivery of his actual work.
This state should be apparent to the user when looking at the RTC Eclipse outgoing changes window (separate change-set for metadata changes alone?) , without requiring the user to run DiffMerge etc. A file that contains metadata changes AND user changes should not be identified in this way.

Idea priority Urgent
  • Post comment
  • Guest
    Reply
    |     Feb 22, 2022

    Additionally, when working in a regulated environment we can be audited on source code changes.

    What I have observed is that after doing a simple change in a big model (like changing the data type of an attribute), I can see 20 or 40 files modified with changes unrelated with my update.

    In case of an audit I am not able to justify that those 40 files changes have no impact on the behavior of the application.

    So it would be really useful to avoid those metada changes, or to store them in a separate file.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.