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 (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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Remove requirement to set Automation level on every Volume policy
Currently, with VM policies, you can add or ignore every variable in the policy menu. By this i mean that i can have a policy blocking instance types, and i don't have to also select Manual or Automatic. I can leave that section blank and allow other automation policies to drive that.
However, with Volume Policies, the toggle for generating actions and the lever for Recommend/Manual/Automatic are required no matter what. If i want to block 500 GP3 volumes from going to GP2, i have to also set the action automation. But if i want a policy automating 200 of those, the first policy remains the most conservative and therefore blocks automation.
Do not place IBM confidential, company confidential, or personal information into any field.