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.
The attachment to the RFE shows a description on the QM *component* however the sidebar of the GC tree UI shows information about the QM *configuration* of that component, which is a different thing.
We don't show component properties when displaying configuration properties (other than the component name). We doubt that most customers will make use of the component description, so adding it would *decrease* user experience by adding clutter.
A manual solution would be to add/copy the description from your component to your configurations of that component. It's often the case that the description of the two would not be exactly the same; it depends on your development process and the conventions you have implemented.
One small enhancement that could make your use case simpler would be to make the component name in GC sidebar a hyperlink to the component object in the QM application. Would this meet your needs?
I note for future readers that the work to implement this "small enhancement" would be done in each application contributing contributions to GCs; GCM in the sidebar is showing an OSLC compact preview.
The attachment to the original RFE includes these motivations
• Test engineers often need to find the corresponding requirement in GC to troubleshoot why links from test artifact to requirement is not showing
• Test engineers follows the standard process to look for corresponding DNG requirement configuration(s) to ensure they have been baselined in the GC before testing starts
• ETM component Description that we use can provide partial name for test engineer to search DNG configuration in GC
As noted in jazz.net work item comment 1 it's not clear what exactly is being requested: the configuration description, the component configuration, or both.
The content of the OSLC preview (which is displayed in the right-hand panel of the CGM tree view) is provided by the application hosting the local configuration.
So this specific RFE was raised in the context of usage scenarios for test developer / tester, however we would need to coordinate updates across the ELM applications (RM, QM, CCM, AM, GC)
Note that we added more SCM information in the OSLC preview in a 7.0.3 milestone.
When a user selects a local configuration in GCM, the details pane (on the RHS) shows details of the LC as provided by the application that owns that LC.
Is this RFE to include:
1) The description of the LC?
2) The description of the local component of that LC?
3) Both #1 and #2?
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 - ELM Common Services
Component - Global Configuration Management
Operating system - Multiple
Source - None
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 - Integrations
Operating system - Windows
Source - None
Attachment (Use case)