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.

ADD A NEW IDEA

Clear

Ideas

Showing 1172 of 7039

Evolve link types constraints in DOORS NEXT to configure link types between modules names

In DOORS Classic, for a specific module (named by its name), it is possible to define the authorized links to another module (by its name). Goal: configure link constraints for the users to avoid errors.UseCase in DOORS Classic: right click on a m...
about 2 years ago in IBM Engineering - Requirements Management DOORS Next / Feature 0 Future consideration

Enforce Link Constraints when User changes Artifact Type

Enforced Link Constraints enable consistency of trace and trace reports. Link constraints are assigned to artifact types. Since a user can change an artifact type, the link constraints for the new type should be applied during the change. Should a...
over 1 year ago in IBM Engineering - Requirements Management DOORS Next / Usability 0 Future consideration

Cross-component ReqIF

DOORS Next can export a component with its internal links to a ReqIF file. But it can't export two DOORS Next, and more importantly : the links between these two components. This enhancement could allow users to use ReqIF to export DOORS documents...
almost 3 years ago in IBM Engineering - Requirements Management DOORS Next / Usability 1 Future consideration

Export a GC stream or baseline without history and import to another RM instance

Export a GC stream of RM streams (or GC baseline of RM baselines) without change history so that a Customer can import the data into their own instance of ELM maintaining navigable links between the artifacts
about 1 year ago in IBM Engineering - Requirements Management DOORS Next / Feature 0 Future consideration

Doors Next create link (linking artifact text with hyperlinks): Allow another default value as 'No Traceability Link'.

Enhance the create link feature (linking artifact text with hyperlinks) to define an existing link type as the default Link type (currently 'No Traceability Link' is the default value and cannot be modified).
9 months ago in IBM Engineering - Requirements Management DOORS Next / Usability 0 Future consideration

Fine-Grained Read Access Permissions

Similar to the way that EWM can "Restrict" read access to certain work items, or streams or components, etc. We need the ability to restrict read access to certain Components/Streams/Folders/Artifacts within ERM and ETM. Unless a user is within an...
9 months ago in IBM Engineering - Requirements Management DOORS Next / Administration 0 Future consideration

Audit trail for deleted artifacts

Deleted artifacts are gone with no trace they existed. Project History should log deletes, including ID, Name, user, and time of delete. This allows the distinction between artifacts that cannot be found vs artifacts deleted.
over 6 years ago in IBM Engineering - Requirements Management DOORS Next / Feature 4 Not under consideration

New attribute for DNG Review Sessions

To enhance Reviews filtering and reporting capabilities, it would be beneficial to introduce an attribute capturing the review "Context". Specifically, the GC or originating stream from which the Review was created.
5 months ago in IBM Engineering - Requirements Management DOORS Next / Usability 0 Future consideration

Accept Changes : Ignore All Option in Accepting Changes instead of Selecting One by One

Hi, During Accept Changes Process, specific change-sets need to be selected rest of them needs to be marked as Ignored for dependent change-sets. From a User Perspective, they want Ignore all button to Ignore all dependent change-sets
over 1 year ago in IBM Engineering - Requirements Management DOORS Next / Feature 1 Future consideration

ReqIF should not fail when an artifact with an image in GC resolves.

DNG should allow an option to ReqIf that when being executed in from a local config and that config includes embedded resource(s) exists but resides in a different configuration to either include embedded resource(s) [copy/include] or proceed with...
2 months ago in IBM Engineering - Requirements Management DOORS Next / Feature 0 Future consideration