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 4, 2024

Allow for the use of 12:xx to be used in time fields

Since moving to v10.1, we have noticed that the Workload Designer does not allow us to use the "twelve o'clock hour" in any of the time fields.  This has been tested by our team at stream level as well as within a run cycle, on the earliest start time as well as latest start time.

We opened IBM Case TS016309578, and have been told that things are working as designed.  The only way to get around this is by using 00:xx.  This is confusing to some of our users, as the use of a 24-hour system still includes the ability to use 12:xx time.  Only 12:00am/pm seem to work.  12:01 - 12:59 throw an error when trying to save.

We would like the ability to use "12" when setting up our times, the same as we could in the v9.x Workload Designer.

Idea priority Medium