This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Scenario:
I have an approved WO that has a task. The task has:
An approved labor actual with non-zero hours
Inherit Status Changes=Yes
I can go ahead and cancel the WO, since the WO doesn't have any approved labor actuals with non-zero hours:
However, when I look at the cancelled WO, I'm surprised to see that the task is still APPR.
If anything, I would have thought one of the following would have happened:
A. Maximo would prevent me from cancelling the WO, because the task has an approved labor actual with non-zero hours.
B. Or, Maximo would cancel the task too, despite the fact that it has an approved labor actual with non-zero hours.
It's unintuitive to me that Maximo cancelled the WO but left the task as APPR. Especially since the task is set to Inherit Status Changes=Yes.
I know there are rules about cancelling WOs (tasks are technically WOs), but I can't imagine why we'd want an approved task while the main WO is cancelled. (We'd never want workers to execute a task when the WO is cancelled.)
Could IBM consider changing that behavior -- so that a cancelled WO can't have approved tasks?
Support says it's not a bug: TS007779764
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.