This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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
Specific links you will want to bookmark for future use
Currently we need to manually select and delete expired risk list entries. We would like to see an option to enable this for a lisk and have the daily maintenance job wipe the expired entries from the list.
Allow functionality to navigate left/right in a data table using keyboard keys, specifically in the case selection page.
Currently in 5.7 you can navigate up/down/left/right in any data table using the keyboard keys however in 6.3 you can only up/down on the overall page with the keyboard, you cannot up/down/left/right in a table result. The main place we would like...
Increased functionality of the "Close to" and "Not Close to" operators
When using the "close to" operators in a condition, would like the ability to specify whether or not the tolerance is only positive or only negative, in addition to the current setting which always works in both a positive and negative direction.
We use CPP tags to show which investigator is assigned to a case, even if that investigator was not the last one to transition the case. When an investigator conducts a bulk transition, they are not able to change the CPP tag through the bulk tran...
Allow the application of users local time on timestamps in data export
Safer payments generated timestamps are stored in UTC and are converted using the users preferences (my account) when displayed in the UI (queries or case management). When export dating the raw data is used and timestamps are exported in UTC. Thi...
Allow for random sampling of alerts from the case selection page. We conduct monthly QA processes that require us to pull a random selection of cases worked by each investigator. Currently we need to download all alerts worked by an investigator a...
Allow references to specific byte ranges within an attribute for comparison. For example, consider building a counter with the intent of identifying a BIN attack/Credit Master attack/enumeration attack. Generally speaking, these attacks will origi...
Separate the Intercepted by existing rules row within rule generation.
We identified in May that the “Intercepted by existing rules” row within the rule generator does not appear to be functioning correctly. Rather than providing stats surrounding transactions which were intercepted by the model revision, it actually...
Keeping the case numbering for each SP instance after restart or restore
as-is: If all cases that generated on low active SP instance was archived, and then the SP instance restarts, the case id for cases generated on this SP instance starts from 1.
Archived cases might be used for investigation and that would be help...
Do not place IBM confidential, company confidential, or personal information into any field.