Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Nov 17, 2022

Overlay warnings when mainframe components are deployed over another users change

Using our previous deployment system, anything a components existed in an enviornment and another user was going to overaly it with their deployment, a warning would be thrown and if the user decided to proceed, the origonal developer whos component was overlayed was notified. This way developers were aware they were not testing the code they thought they had deployed. This capability would need to be at the individual load module level since mainframe deployment are almost always uniqueue. What I mean by that is the fact that each build usually has different programs in it.

Idea priority Medium
  • Admin
    Osman Burucu
    Jan 12, 2023

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Admin
    Osman Burucu
    Dec 7, 2022

    We think the problem stated will be solved by using right git branching strategies and effective process to govern changes. If 2 developers pull from the same branch and add their changes, they are less likely to end up in merge conflicts and hence their changes can be added on top of one another. Because of this, 2 changes worked by 2 different developers on the same program aimed for same release, then this shouldn’t be an issue at all. For testing changes in isolation, they could dedicate a separate environment in UCD where all programs can be tested with unit testing scope without any need to maintain the overall integrity of the environment

    Why changes aren’t traced through JIRA/RTC/EWM/GitHub/GitLab/<your choice of issue tracking tool> board and why conflicting changes can’t be primitively found much earlier in the SDLC phase to avoid such conflicts?

    Looking forward to your feedback.

  • Guest
    Nov 17, 2022

    I am surprised this hasn't already been identified and part of the product.