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 Future consideration
Created by Guest
Created on Jan 5, 2021

Epic - Solutions History

While closing a ticket the helpdesk engineer enters an adhoc solution. When user reopens the ticket and it moves through the normal process flow, the solution provided earlier is rewritten. If this is not an approved solution this is not saved anywhere in the Failed Solutions history of the record as well. There is no way to identify what solution was provided in the first place.

Requirement is to have a process/method to reset this solution(symptom/cause/resolution) field and save it in history for future reference.

Idea priority Urgent
  • Guest
    Reply
    |
    Feb 8, 2021

    We are looking for a way to determine which solution(s) were not successful in previous attempts when a ticket is reopened.
    We are looking for a means to store the failed solution. Currently only approved solutions are attached to the ticket as failed solution. We want a mechanism to track the earlier Symptom,Cause,Resolution entries (even if it is not an approved solution).

  • Guest
    Reply
    |
    Feb 5, 2021

    Can you please confirm the exact expectation for this requirement? When a ticket is re-opened, you are looking for a way to determine which solution(s) were not successful in previous attempts. Meaning failed solutions are stored? Can you please confirm? Thanks a lot.

  • Guest
    Reply
    |
    Jan 21, 2021

    Steps:
    1) Helpdesk engineer Resolves (Meant resolved when typing closed in RFE)the ticket by entering "Symptom,Cause&Resolution".
    2) Ticket status is now resolved
    3) End user however is not satisfied with the resolution and reopens the ticket
    4) The old solution provided by the Engineer is probably not complete.
    5) The engineer again works on the ticket and fills in "Symptom,Cause&Resolution"
    6) The original solution provided is overwritten or is lost completely as the engineer might have deleted it. There is no way of finding this information.

    Requirement is to save this solution in a history table linked to ticket so that all the solutions thus provided for each ticket is available for view.

  • Guest
    Reply
    |
    Jan 21, 2021

    We need some more details about the term "reopen" in order to be in the position to assess this request: can you please detail exactly the steps performed here?