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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Consider Project Area Associations for Traceability:
Currently, traces from an Item in an config management enabled RM project area to config management enabled project areas in other applications, e.g. QM, are only possible if the RM and the QM project area are associated to each other.
For config management enabled RM project areas this is not the case, though. Even if 2 config management enabled project areas are not associated to each other, traces can be created between these project areas (if the corresponding components are part of the same global configuration).
Request: Do not allow traceability between requirements if the the corresponding project areas are not associated to each other.
Reasons:
a. Consolidate the behaviour of traceability restrictions.
b. Allow additional trace restrictions.
Use Case: We have different RM project areas for different architectural levels. We would like to restrict the traces of requirements in a specific level to only the two adjacent levels, e.g. we would like to restrict Traces from the Level 2 requirements to only requirements of Level 1 and 3.
Idea priority | Medium |
Needed By | Quarter |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.