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 Submitted
Categories Documentation
Created by Guest
Created on Dec 2, 2024

Inconsistent Recording of Backlinks in DOORS Next Generation (DNG) Audit History in GC enabled projects.

CM Enabled Projects with Global Configurations

In a CM enabled project that uses Global Configurations:

  • Backlinks are not created or stored in DNG. Instead, these links are managed and stored in LDX.
  • Consequently, the creation/deletion/modification of such links does not update the audit history of the DNG artifact.
  • Users cannot see the backlink creation/deletion in the artifact's audit history.

This inconsistency creates a gap in traceability and auditability.

Example:

  • In a non-CM enabled project, if a user links an EWM work item to a DNG artifact, the DNG artifact's audit history will reflect the backlink creation.
  • In a CM enabled project, performing the same operation results in no audit history entry in DNG for the artifact, even though the link exists and can be resolved through LDX.

Expectation:

Backlink creation/deletion should be consistently recorded in the audit history of DNG artifacts, regardless of whether the project is CM enabled or not. Users should be able to trace and audit the creation of backlinks directly within DNG artifact history to ensure uniformity, consistency, improve traceability and maintain the integrity of the audit history across all types of DNG projects.

Current Limitation:

Currently, it is not possible to check the other end of the link in the artifact history, making it difficult to track the relationships between artifacts across projects.

Recommended Solution:

Update the DNG audit history mechanism to consistently record backlinks, regardless of project configuration (CM or non-CM enabled). This would provide a comprehensive and accurate history of all changes and relationships between artifacts.

Idea priority High
Needed By Week