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 (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 Submitted
Workspace DevOps Automation
Categories Deploy
Created by Guest
Created on Mar 10, 2026

RELATED IDEAS

Allow custom process/request properties to be injected into inProps for any step

Currently in IBM DevOps Deploy, step scripts (such as Groovy steps) can only access properties provided in inProps by the plugin infrastructure. Properties from other scopes (process, request, or previous step outputs) are not available unless they are resolved using ${p:...} substitution on the server side.

This makes it difficult to programmatically access structured data (for example JSON) within scripts, because the values must be embedded via string substitution rather than accessed through a runtime API.

It would be very useful to allow users to explicitly inject one or more custom properties (process, request, or step output properties) into the inProps object for any step.

For example:

Inject into inProps:
- request/deployReport
- process/deployReport
- createReport/deployReport

This would allow scripts to access them directly:

inProps.getProperty("deployReport")

Such a feature would simplify scripting, avoid server-side substitution issues, and improve support for structured data handling in deployment processes.

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.