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:
Post your ideas
Start by posting 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - incl Orchestration and Performance Management
Cloud Pak for Watson AIOps - incl Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - incl IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - incl Workload Scheduler
Tivoli System Automation - inc Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Increase Maximum Byte Constraint on "Node" (Currently 51 bytes)
Node name currently has a maximum byte size of 51 chars. We have nodes with FQDN's source AWS that require 75 chars. We request that node name be increased to some value at or exceeding 128 bytes to facilitate long node values in the future. Appli...
ProcessID missing in joblogs for windows processes
CASE ID - TS003942595During investigations to identify long running issues of a job, we found that Windows ProcessID is not supplied back to the Job Log, Yet for Linux/Unix processes the ID is provided. This makes tracing the process thats causing...
We would like an option in the IWS reporting tool to display failed jobs (ex: jobs that fail because there are no resources available.) If a job creates any kind of error, (failed/abended/etc.), we want to be able to see it in a report to keep tra...
Extend IWS REST to contain more basic modificaton operations
Please add rest methods for IWS 9.5 to be able easily to do: Add a job into an existing jobstream – that should be a method with few parametersRemove a job from an existing jobstream - that should be a method with few parametersAdd a dependency in...
Enforce Auditing justification and reporting in all interfaces, not just DWC
In 9.4 the ability to enforce the addition of a justification and a change/incident record number (from ServiceNow for instance) to all plan and database changes was added when these actions originate from the DWC. No equivalent ability to enforce...
Ability to add dependencies to individual run cycles
Ability to add dependencies to individual run cycles. Currently can't. See highlighted example below of what is required. We have a jobstream with multiple runcycles, but want one of those runcycle to follow another jobstream, not them all. We hav...
Plugin Powercenter - try to reconnect in case of broken connection
When we submit Powercenter jobs, if the connection between IWS and Powercenter is broken by any external reason the jobs currently end in error on IWS, but continue to execute on Powercenter. Therefore the user always needs to enter on Powercenter...
Do not place IBM confidential, company confidential, or personal information into any field.