Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Sep 8, 2020

Define access rules based on “Team” resource instead of Orchestration Service and also create the “Delete” capability.

Our company uses UrbanCode Deploy Blueprint Designer for environment provisioning. We have many teams and different functions and we would like to restrict users to visualize, edit, create or delete environments and other resources of the teams they don't belong to. As all the environments were currently associated to the same Orchestration Service (Terraform), all the users can access all the environments regardless their teams.

Use Case
System: UrbanCode Deploy Blueprint Designer Actor: user joao.mesquita (Function: Developer) Use cases for the system - Destroy Environments Scenario: Destroy environments from the same orchestration service but created by a different team. Steps include: - Access Environments section - Select an environment clicking on “Action” column - Select “Destroy environment”
RFE ID 145107
RFE URL
RFE Product UrbanCode Deploy
Idea Priority Urgent
  • Guest
    Apr 5, 2021

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