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 a notification 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
In UrbaCode deploy there are two possible ways of authentication:userid/password and token Both authentication mechanisms are not considered secure enough to trigger deployments from an external pipeline.
Provide the ability to assign "All Teams" to an object in UrbanCode Deploy
Our team uses UrbanCode Deploy for software deployments. However, we have several components and templates that are 'shared' among all users of the product. With current functionality, every team that wishes to consume one of these objects must be...
Add a toggle option to hide deployment steps that haven't been executed for any reason (versions/flow design/components/etc) at the top of the deployment log page. Additionally, store this as a user preference so customers don't continuously need ...
Credentials are transmitted to server in plain text: Open; Justification: An adversary can strip SSL and intercept plain text credentials using sniffer tools like fiddler, burp suite. Credentials thus obtained may be used to gain unauthorized access to the application
Justification : An adversary can strip SSL and intercept plain text credentials using sniffer tools like fiddler, burp suite. Credentials thus obtained may be used to gain unauthorized access to the application
All comments should be retained when the 'Save Edit Mode' feature is enabled
If the 'Safe Edit Mode' and the 'Require a Comment For Process Design Changes' setting is enabled, it is necessary to comment each process change (in the Draft Process). We usually save the Draft Process more than one time before it gets promoted....
Our UCD deployment process has 30 steps and current success/fail status is causing confusion with the deployers knowing which steps run and which did not. We have a number of conditional steps that will run or will not run depending on the switch ...
Allow agent logs to be accessible from UCD server UI according to name pattern defined in agents log4j
Currently the "request agent logs" feature from UCD server UI only supports the agent log files in format agent.out.<INDEX>. We are working with teams which updated the agent log4j to alter the log file name to a daily naming syntax, e.g. ag...
Do not place IBM confidential, company confidential, or personal information into any field.