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
Categories Usability
Created by Guest
Created on Jan 10, 2023

in modules prevent base artifact linking via project admin setting

In the system engineering all customers working in DNG with in the module mode. The default requirement engineer works inside a module and is not aware of the background settings in DNG, eg the artifacts are stored in a module folder and there is a difference between a link to an artifact in the module or to the artifact in the folder structure.

Most of the documentation leads the user to link via the link dialog box. But in this dialog box the default link target leads to the folders and so to the base artifacts and not to the modules.

As result often ther is a mix between real module links and base artifact links, which have a different meaning and will be handeld different in reports.

It would be nice to be able to force somehow the user to only create module links.

As an idea this could be implemented via an administrative setting for the DNG instance or the single proejct area. An Admin property, eg default working mode: module based or folder based. If module based is selected: the default settings for the user in the project is: in the link dialog box: Module is the default link target ann in the main Artifact Menu, Module (not All) is the default working mode.

This option would reduse training and onboarding time.
Reduse the confusion of the user, if sometimes an existing lin is seen or not.
Reduce the Quality checks on projects, check if all requirments are linked correctly, eg SYS req to SW req, Req to Test Case, Req to Architecture, ...


with reference to older similar ideas and enhancemnt requests about this topic:

DNG Links explorer & reports doesn't handle Base -v- module links the same way
https://ibm-ai-apps.ideas.ibm.com/ideas/ENGRMDN-I-197

Enhancement 139271
Support preference to linking in module context over linking to base artefact
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=139271

Enhancement 139272
Support constraint to only allow linking in module context and disallow linking to base artefact
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=139272

Enhancement 128939
DOORS NG - Confusion of base and module links
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=128939




Idea priority High
Needed By Quarter
  • Guest
    Reply
    |
    Oct 2, 2024

    another idea that already includes this one: https://ibm-ai-apps.ideas.ibm.com/ideas/ENGRMDN-I-831

  • Guest
    Reply
    |
    Jul 4, 2023

    I would like to extend: if there is only 1 module in a component, this module could already open and not only the "module" view.

    same for the dialog boxes: in general default = module, if only 1 module per component, select this already


    ... and this is from my point of view only a first step. Long-Term IBM has to get rid of the current core vs module artifact stuff and replace it by removing this difference and introducing a defined "reuse" scenario for customers using current reuse.