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.
Fix bug in UrbanCode Release that writes favicon.ico errors to logs
UrbanCode Release v126.96.36.199 has a bug that causes errors and associated java Exception stack traces to be written to the var/log/stdout and var/log/ucrelease.log when some http(s) interaction with the application can't resolve the favicon.ico file....
Once the plan or task is paused for certain amount of time, it shouldn't be included in actual duration; actual duration should be "elapsed time" and total duration should be what currently the actual time is.
There should be pause and play feature with the deployment plan. For Example there is a release going on and we need to pause the release so that we can deploy some of the task next day. Also, once the plan or task is paused for certain amount of ...
To trigger jenkins job from UCR by passing parameter from UCR GUI
We need to pop up all the parameter's for a jenkins job from UCR GUI so that we can trigger the jenkins job from UCR deployment plan. Also it should orchestrate weather the job was successful on jenkins or it got failed. It should also publish the...
UCR needs to be able to send information back to Jira regarding deployment statuses
JIRA is being used as the approval system for our releases. UCR needs to be able to send information back to Jira regarding deployment statuses to keep the sub-tasks current with the deployment statuses.
Urban Code Release needs to be able to connect to JIRA to pull Key Details from Epics, Tasks, Sub-tasks, etc.
Urban Code Release needs to be able to connect to JIRA to pull Key Details from Epics, Tasks, Sub-tasks of said tasks, etc. For our pipeline these are the Jira Task Key and a sub task key (CICD). UCR needs to be able to set the property request fi...
logs and status of ansible jobs that are triggered from UrbanCode Release should be published on UCR GUI
The ansible jobs are being triggered from UrbanCode Release do not publish ansible logs and it does not tell you whether the jobs are completed successfully or not. For us it does not make any sense to trigger jobs from UCR and then to check logs ...
Do not place IBM confidential, company confidential, or personal information into any field.