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
Post 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 product management 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 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.
Watson Assistant New Experience needs JSON import/export function
The Watson Assistant New Experience is missing the JSON import/export function that the Classic Experience had. When switching between New and Classic experiences, the Assistant data is not migrated, therefore you cannot switch to the Classic expe...
The Watson Assistant New Experience needs a way to enable and disable an Assistant without having to delete and recreate it when needed. My business case is that I create Assistants for annual events. We only need the Assistant active during the e...
In order to support full CI/CD of our Watson assistant based product, we should have the full ability to deploy a version without any manual UI actions needed. Currently, the API does not support any version control.
Update cursor to provide more contrast in JSON editor
A few versions ago, we were able to see the cursor in the JSON editor within a dialog node, but now it's very difficult to see so it makes editing very difficult. Can the cursor be changed to provide more contrast so we can find it.
When using Watson Assistant search, we can find node names, but we can't find which nodes have a jump to a particular node. This would be helpful to know what nodes are jumping to a particular node. This could be implemented in one or the other (o...
When changing Intent name, offer to change corresponding dialog nodes
When we change an intent name, then all the dialog nodes that use it have errors because the old intent name no longer exists. We suggest that when an intent name is changed, then the option is provided to also change where it is used in dialog.
Currently, if we have "seasonal" intents, we have to pull them out and save them somewhere. There is no way to turn them off at certain times of the year. It would be helpful to have an on/off switch for intents. Better yet would be a means to hav...
Ability to delete disabled nodes when turning off MCR
Currently, when you turn off MCR (Multiple Conditioned Response) it will disable the separate responses instead of deleting them. This means they are kept in the skill/module but won't be visible in the Watson Assistant UI (can be seen in the down...
The API currently does not support handling of carriage character. While our UI does handle this, in cases where customers copy/paste data, we are unable to handle unless we build a custom handler to remove carriage characters. While we can implem...
Do not place IBM confidential, company confidential, or personal information into any field.