Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

Status Not under consideration
Created by Guest
Created on Jul 1, 2014

Enable Incident Entry in Self-Service-Portal

Currently when Incident are entered through the Self-Service-Portal, they result in a Service Reuqest ("Report Issue"). This makes it necessary for the Servicedesk to duplicate the tickets and close the originated Service Request. This again confuses the user who entered the Service Request and now gets informed that this Service Request has been closed, even that it is not already closed but duplicated into an Incident. Users are able to distinguish between Requests and Incidents, and the small amount of "wrong" types can be handled as planned by IBM. Another solution could be that no specific "type" is created but just a "ticket" going to the inbox of the servicedesk, who select if it's an incident or a Service Request.

Idea priority High
  • Guest
    Reply
    |
    Apr 12, 2019

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Workload Automation and Control Desk
    Product - IBM Control Desk

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Control Desk

  • Guest
    Reply
    |
    Jul 31, 2018

    This is a lacking feature that all of our customers request when enabling Self Service. Would be very appreciated if this gets into the final product.

  • Guest
    Reply
    |
    Oct 10, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - ITSM Automation and Control Desk
    Product - IBM Control Desk

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Asset Management
    Product - IBM Control Desk

  • Guest
    Reply
    |
    Jul 1, 2014

    I see value in potentially having a holding Ticket class for the self submitted requests and then an agent determining the actual class to use (SR or INCIDENT), as other help desk systems do this already, but I definitely don't want end users being able to send in Incidents directly as their idea of an incident is often different than what's been established (IE them forgetting their password is not an incident that goes against our SLA, their application being down is).

    I think if a holding ticket class isn't an option and you choose to enable self service users to create incidents, then it needs to be configurable similar to the other options on self service portal so it can be turned off (or ideally, turned on when needed but off by default).