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
Categories Administration
Created by Guest
Created on Apr 3, 2019

Requirement to maintain Incrementing prefix pattern in RQM post migration from DOORS CLASSIC

Our unique ID solution for RQM is currently lacking, especially compared to what DOORS Classic was capable of. This impacts our ability to migrate projects that previously had test cases stored in DOORS Classic. DC allowed for a prefix to be assigned to a module and then automatically appended the next available numeric value to the prefix. For example, if a new test case is created with prefix “7XYZ-HC” and it is the 26th test case to be created in that module, its identifier would be “Y7XYZ-HC-0026”. The next test case created within this project would be 7XYZ-HC-0027, and so forth. In order for us to fully be able to migrate projects without disrupting how their archived artifacts are named, we need the ability to add a prefix to the test case identifier.

Idea priority Urgent
  • Guest
    Reply
    |
    Mar 11, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Internet of Things
    Product family - Engineering Lifecycle Management (ELM)
    Product - IBM Engineering Test Management (formerly Rational Quality Manager- RQM)
    Component - Administration

    For recording keeping, the previous attributes were:
    Brand - Internet of Things
    Product family - Engineering Lifecycle Management (ELM)
    Product - IBM Engineering Test Management (formerly Rational Quality Manager- RQM)
    Component - Migration

  • Guest
    Reply
    |
    Apr 5, 2019

    Test cases in RQM do not belong to a specific test plan (the equivalent to a DOORS module). Test cases can be reused in multiple test plans.
    One option would be to have the prefix set for a test case custom category.

    This could work in the following way:

    - Admin users define a test case custom category as an "automatic ID" custom category and define the prefixes as the enumerated values for this category
    - Users create a new test case and then setting the value (prefix) of that category
    - Users save the new test case, RQM updates the value for the category with a incremental number based on that category. The value of that category becomes prefix-ID, where ID starts at 0001 and is incremented for each new test case in that category.
    - Users could later modify the category value (prefix) for this test case, then when the test case is saved the new prefix is used. The new value of that category becomes prefix-ID, with the new selected prefix, where ID starts at 0001 and is incremented for each new test case in that category. Previously use prefix-ID is "lost" and cannot be reused.
    - A new permission in the project area admin page would be available to restrict the modification of the 'automatic ID" custom category to a set of defined users.