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 Future consideration
Created by Guest
Created on Oct 10, 2018

Jupyter notebook as a DO dashboard page

Similar to using a notebook as a source for optimization code, allow the user to write a notebook that contains visualization components for a dashboard page.
Ideally, have an ability per cell to hide the cell, the output or both from the dashboard. For instance through some new annotations (`#dd-hide`, `dd-hide-cell`, `dd-hide-cell-output`)
This would allow the user to include comments (markdown cells) or just the output of a cell (e.g. a graph, map, print statement) while hiding the code that generates the output.
The dashboard framework should load the inputs and outputs.
Use a annotation like `#dd-ignore` to filter out cells that are not relevant for the visualization

The gist of the idea is to be able to include certain types of charts and other output that:
a. Is not supported by the default set of available charts.
b. Require code to generate the output.

Examples of usage:
* Folium map visualizations. These are very rich interactive UIs that require a fair bit of coding. It is not realistic that this type of visualization will be able to be supported through some a chart-wizard without coding in Python.

  • Guest
    Dec 14, 2018

    I agree - having this ability to bring in custom visualization would make the dashboards significantly more valuable, even if we start by just displaying two Folium maps side-by-side when comparing multiple scenarios.