Skip to Main Content
IBM Security Ideas Portal

Shape the future of IBM Security

We invite you to shape the future of IBM, including the product roadmap, by submitting enhancement 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 vote for them if they matter to you,

  1. Post an idea

  2. Vote for 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 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 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.

Post an Idea

To post a new idea - click on the "Add a new idea" button and where asked select the appropriate category this idea relates to. Provide requested information to allow us to get a better understanding of your request.

"Missing" Security Products?

If you cannot find the IBM Security product you are looking for then it is probably located in the IBM Security Private Ideas Portal. Check that site to open an idea.

Idea visibility

All ideas submitted via this portal are visible to all other portal users, though personal information fields remain hidden. If you would rather have your idea visible to only you and IBM then use the IBM Security Private Ideas Portal instead.

Please note: The purpose of the Ideas Portal is to tap the creativity of the IBM Security community so that we can enhance our products for everyone! If you need to report a defect or get help, please use our normal support channel. Click here to open a support ticket.

Want to see all of your IBM ideas in one place? Find them at

Status Under review
Workspace QRadar SOAR
Categories Look & feel
Created by Guest
Created on Oct 3, 2022 - Create a more User Friendly Pop-up

Currently when using the command in scripting, the pop-up error includes the name of the trigger point (rule/playbook), the name of the script, then the String included in the () portion of the command.

Example: Current Error:

Script 'X' from Playbook 'Y' was unable to complete because: HelperFailException: Corrective Action needed to be taken by the user

This causes confusion to the user base (thinking there is an error with the system instead of an intentional stop error that requires their action).

Suggested Example: Error:

Script 'X' from Playbook 'Y' was unable to complete because: HelperFailException: Corrective Action needed to be taken by the user

In doing so, we can develop our own string to explain the error and then direct the User to the steps to resolve without the "noise".

  • Guest
    Oct 20, 2022

    I'll leverage formatting to help separate the noise from pop up information I'm looking to provide (thanks for that). However the part I highlight in red doesn't really have use from a User standpoint (that is what I'm looking to remove for a more friendly user experience)

    Anytime a user sees "Error" with a line of information that isn't pertinent to them "Rule 'X" is unable to update the incident "case" because: helperfail exception"

    From ease of confusion that should be dropped and whatever formatting the script writer opts to leverage can be done in the line alone

  • Guest
    Oct 20, 2022

    you can do it already by customizing the in scripts:
    Example when a mandatory field in the task, with instruction to put data is left empty, after a condition in a workflow/playbook:"\n\n\nDear {}, \n Please validate the mandatory Field for this Task. \nRead the instructions for this Task.\n\n\n".format(principal.display_name))