Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Future consideration
Workspace watsonx.ai
Created by Guest
Created on Nov 21, 2023

Watson Studio add the ability to schedule a job from a Git projects

Today, this can only be run. When the project is in a Git project, it cannot be scheduled. In most cases, the customer would be running from the main branch. This customer is migrating from Watson Studio Local to CP4D and one of the items that is a sticking points is inability to schedule job in Git projects, the client is on 4.6 and we found that this is a limitation as documented here (step 5) for 4.6 and 4.7: https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=projects-creating-managing-jobs#jobs-assets-page.

For now the workaround we got from James Spyker the customer will be using. But for the customer, this is a loss of functionality and adds more steps to schedule a job.

If the scheduled job is more just part of their dev workload (e.g. every night they use a Data Refinery flow to read new data from their System of Record database and update some feature tables for their data scientists to play with) and they are comfortable with it running whatever version of that flow happens to be in their local clone at that time then they can use an external scheduling tool to trigger a cpdctl script to run the job in the project.

Reference internal slack link: https://ibm-analytics.slack.com/archives/CGE3M0118/p1699039554591559

 

Needed By Quarter
  • Guest
    Reply
    |
    Feb 2, 2024

    We are also receive feedback from our clients that this loss of functionality has caused inconvenience to maintain exisiting workflow with git enabled project. Our client has provided the following recommendation for product team's consideration to restore this capability.

    =======

    Watson Studio Projects should not store and sync any code, scripts, parameters, schedules, and metadata related to scheduling jobs while pushing/pulling to Git.

    Make scheduling jobs a user defined process that is only persistent within the individual user instance of the Watson Studio Project.

    Every time a new user pulls a git-enabled Watson Studio Project, they will need to manually configure any jobs schedules to run any Watson Studio Notebooks within the project. Not syncing any code, scripts, parameters, schedules, and metadata related to scheduling jobs in Git should remove any job-related information overlap in Git. Allowing individual users to create jobs within their own project instances gives users the ability to tailor job schedules on an individual basis which is a lot more flexible.