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 Not under consideration
Created by Guest
Created on Feb 10, 2022

Proactive notification/forecast of a job run in plan soon after creation/schedule

Need a proactive notification/forecast of how a job will run in plan as soon as it is created/changed in the database.

e.g. If we are scheduling a 5 mins recurring job by just setting a Start Time as 05:00 GMT (without any carryforward/Until options), tool has to recognize straightaway the job will start at 05:00 GMT and will run until 12:00 PM GMT (until JNEXTPLAN).

Idea priority Medium
  • Admin
    Adriana Pinto-Lista
    Oct 25, 2022

    This idea has been closed for lack of information. Unfortunately, the team does not have enough information to proceed with this request. You can always reopen it or submit a new request in the future. Thank you.

  • Guest
    Mar 3, 2022

    Hello there, we need to understand better the scenario. Are you referring to the case when the EVERY is defined at job level?

    What kind of notification would you need?

    What is the problem that you want to address?

    Thanks, Marco