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.
Improve support for migration of UCD objects across instances
Tools team is currently supporting active development of UCD processes for several hundred applications. We would like to manage and deploy UCD objects using standard automated development practices. Unfortunately, the available processes are incomplete or completely manual. Here are the enhancements we are looking for
• Provide APIs for exporting and importing application template, component templates, and generic processes as well as uploading the plugins • Add description field to the system properties API • Support upgrade type of ‘use existing processes' for importing generic processes which call other processes (currently all related processes are also updated) • In the process log/system log, show all the changes made during the import instead of just showing the version differences (properties, property definitions, post processing scripts, plugin step versions.) For example, take a look at how UCR documents an import • Provide options for reverting/backout the import process at a template level and generic process level
NB, the SafeEdit feature may be useful in reasonably steady-state environments, but only applies to component templates.
Here is the workflow we are looking for. Development (processes, templates, system properties) is done in a separate instance of UCD. Ready-for-test objects are versioned in GIT and published to UCD object components. Snapshot of those components are deployed to a UCD acceptance environment for testing, then deployed to the UCD production environment.
Do not place IBM confidential, company confidential, or personal information into any field.