Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 Planned for future release
Created by Guest
Created on Jun 15, 2023

IBM Runbook Automation (RBA) - conditional logic in the runbook/automation editor

Why is it useful? - Right now RBA allows no custom conditional logic to chain together runbooks/automations, which is handy to build end-to-end automation workflow.

Who would benefit from it? - All customers of RBA, everyone would be able to build more powerful end-to-end automation workflows.

How should it work? - In the GUI editor it could prompt for certain conditionals/loops which you can use to chain them together - could work with automations and/or runbooks.



Runbook: System Maintenance

Automation 1: Logged In Users

Automation 2: Restart DB


execute runbook > execute automation 1 > returns code 4 > don't execute automation 2


In the example above, when executing the runbook if the first runbook returns a certain status code we can conditonally decide not to restart the DB as it would affect logged in users - this would give more flexibility in building automation workflows.

Idea priority Medium