Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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

Search results

Showing 2

The 'System Down' field is not specified when Storage Insights is used to open a support ticket

When using Storage Insights to create a ticket for a monitored storage system, there is nowhere to specify a value for 'System Down' field. Depending on the device type, the 'System Down' field may be a required field in the IBM Support Portal, in...
21 days ago in IBM Storage Insights 0 Submitted

Virginia Tech: The external agent API endpoint consumes a customer provided tarball, unpacks it and then launches a process using the scripts in the tarball. The tarball is unpacked with whatever file ownership options were passed to tar during its creation. For some applications, this causes problems as the scripts are run as root, but the file ownership is still based on the tar file inputs. The request is to unpack the tarball with customer selectable UGO permissions.

Unpacking the tarball with the appropriate tar flags to ignore the ownership and substitute root or updating the file agent documentation to request the customer producing the tarball use the --owner=root and --group=root options may help customer...
almost 2 years ago in Cloud Object Storage System 0 Submitted