Skip to Main Content
IBM Data and AI Ideas Portal for Customers

Shape the future of IBM!

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Submitted
Workspace Watson Assistant
Created by Guest
Created on May 17, 2021

Support a more robust yet responsive SDLC within the Watson Assistant studio

Rather than suggest a solution (we have multiple ideas, I’m sure IBM and community would have many others) thought it better to state our problem.

Our needs:

  • We need to speedily develop and promote conversation fixes to production to respond to problems with our dialogs

  • We need to release new, larger conversations when they are QA’d. This takes longer than the quick fixes above.

  • We need to be able to test large new conversations against test environments and data, both so we don’t trigger production events, and also for data privacy reasons – you know, the usual reasons.

Our reality:

  • We have a separate skill for “Test” and “Prod” as we can only associate one webhook to each skill, so this is how we QA against test data and environments

  • To make a quick fix we have to either make in prod skill, and then manually replicate the same changes in test skill, or make the change in test and manually replicate in the prod skill.

    • We cannot copy the whole test skill to prod as this would make new conversations that are still being developed “live” for customers

    • We cannot copy the prod skill back to the test skill as this would wipe out the conversations that are in development

    • So we have to do it twice and hope we remember/get it right. Which some times we won’t

Some solutions that could help include:

  • Providing a compare tool to verify the differences between skills

  • Allowing dynamic assignment of webhooks

  • Supporting better tagging and replication of objects within a skill

Like I say, we don’t mind how its solved, but it is a real problem.