Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 (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

  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 (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.

Add a new idea Subscribe
Status Under review
Workspace Workload Automation
Created by Guest
Created on Mar 11, 2026

RELATED IDEAS

Fix incorrect display of cancel status on rerun jobs when the original job is cancelled.

Why is it useful?
There is a display logic error in Monitor Workload when handling cancelled jobs that have reruns. Currently, if a job has multiple reruns (e.g., one original job + two reruns), and the user cancels the original job, the cancel status incorrectly appears on the latest rerun job, while the original job's status remains unchanged (e.g., still shows as Failed/Error). This misleads users about which job instance was actually cancelled and creates confusion in job history tracking and auditing.

Who would benefit from it?
Operators, schedulers, and support teams who rely on accurate job status information for troubleshooting and reporting.

How should it work?

When a user cancels a specific job instance (whether original or rerun), the cancel status should be applied only to that specific instance.

Other rerun instances should retain their original final statuses (e.g., Failed, Success, etc.).

The job history display should accurately reflect which instance was cancelled without altering the status of unrelated reruns.

Idea priority Medium

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.