Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Created by Guest
Created on Aug 5, 2025

Extend Incident Restriction Filter capability to allow custom Alert Fields to be used

Access Control (RBAC) is generally aligned to categories such as affected customer/environment, security restrictions etc. 
Source data allowing classification is present in the Alerts (and used successfully to enable Restriction Filters in the Alert views). Typically these are non-standard fields applied under the "Details" grouping.

Automation policies can be written to e.g. assign a resolver group based on this data during Incident creation but since this has to be specified manually. This is impractical for environments with e.g. large numbers of customers. It also may not be possible to achieve a 1-1 mapping for some criteria (e.g. security classification). 

Filtering on alert fields is possible within the Incident viewer, but it is not possible to save these filters as Restriction filters. 

Meeting the requirement could be achieved by:
1) Enabling Incident  filters based on arbitrary/custom Alert fields to be used as Restriction filters
2) Extending Incident automation policies to allow extraction of arbitrary alert data into Incident metadata AND enabling incident restriction filters to be written against such metadata fields.

Idea priority High
  • Guest
    Oct 8, 2025

     

    
    
    In principal it should be possible to use each customer attribute for restriction filters.
    
    Alert Raw Data - details sample (extract from JSON):
    
    "details": {"eventID": "d701a8ec-a42d-71f0-1a5c-06970e650000","sourceOBM": "everest.sysm.ts-ian.net","eventState": "OPEN","eventKey": "HPBsmIntVROps:45f8e1ea-6d5a-49a8-b8b1-e24a49f65d95:1","timeCreated": "2025-10-08T10:01:36.036Z","timeReceived": "2025-10-08T10:02:05.005Z","TsCompany": "T-Systems International GmbH","TsCustomerLinkId": "","TsSecureLevel": "","TsIncidentAssignment": "MIS.XXXX.SK.YY.ZZ.AAA","TsLocationFullname": "DE_FRANKFURT-AM-MAIN_XXXXXXXX"},
    
    mainly the TsIncidentAssignment  attribute is essential, but also other customer defined attributes may be of value
    e.g. TsCompany, TsSecureLevel, TsLocationFullname