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 Future consideration
Created by Guest
Created on Jun 7, 2022

Would like to see an intermediate state between enabled and draft for IWA schedules

Most of our application teams have their schedules set up in the non-prod environments to mimic production, including the run cycles. This simplifies the production promotions as we can copy the objects and change the workstations they run on for production.

However, in most cases they do not want their jobs running in the non-prod environments except when doing specific testing, as doing so can interfere with development, other testing as well as being a licensing concern. They may test individual schedules periodically, and also may run a full end-to-end test of their schedules.

Putting schedules in "DRAFT" state however prevents manual submission. We are working around this currently by having a calendar that is used in the non-prod environments as an exception run cycle to prevent items from being added to the plan except when testing is in progress. By doing this however we are having to manually remove that run cycle when promoting changes to production.

What would be nice to have is an intermediate state, where schedules are not in the plan, but the run cycles can be established without placing the schedule in DRAFT mode. The other facet of this request would be we need a simple way to indicate that testing is going to occur and we need to add schedules in this new state to the plan when it is generated next.

Idea priority Medium