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 Links
Created by Guest
Created on Oct 7, 2022

Show inlinks from baselined source modules

Initial situation:
We have two modules A and B, each containing an object a and b respectively. This is a simplified representation of the situation that exists in development. The two modules correspond to modules that are processed in different development cycles. The use of a baseline set that contains both modules A and B is thus excluded. This is because several baselines of module A may be created, and a baseline set should not necessarily contain the last of these baselines, but an older one.


Creation of the link:
A baseline 1.0 is created from module A. Object b is linked to object a [1.0], i.e. to the version in the baseline. From b it is possible to navigate to a[1.0], and from a[1.0] back to b. a in the current version has no link.
This corresponds to the expectation.


Baseline of the 2nd module:

Now a baseline 1.0 is created by Module B.

Expectation:

1. from b can be navigated to a[1.0], and from a[1.0] back to b.

2. from b[1.0] can be navigated to a[1.0], and from a[1.0] back to b[1.0].


Observation:

1. bilateral navigation between b and a[1.0] is possible, corresponds to the expectation

2. from b[1.0] it is possible to navigate to a[1.0], from a[1.0] there is - contrary to expectation - no way back to b[1.0]


Explanation:
The observation corresponds to the documented behaviour of DOORS. When creating a baseline, outgoing links become "one-way" links (half links), which are displayed with an empty triangle: it is still possible to navigate from this baseline to the target object (which may be in the baseline of another module), but not back from there.


Idea:
Since the information about which versions of objects are linked is apparently available in the tool, it is incomprehensible why this information is not used to be able to navigate back and forth between baselines. We see that this kind of navigation works in baseline sets. However, since already created (older) baselines cannot be included in a baseline set, we cannot use them in our situation. We need a comprehensible representation of why it was decided not to be able to navigate between baselines outside of baseline sets.

Idea priority Urgent
Needed By Yesterday (Let's go already!)