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 Subscribe
Status Future consideration
Workspace IBM Engineering - Requirements Management DOORS Next
Categories Feature
Created by Guest
Created on Jul 14, 2023

RELATED IDEAS

Change "modified date" field when the artifact is delivered, or add a new "delivered date" field

Hello,

The main purpose of this idea is to make the oslc query "oslc.where=dcterms:modified>=<<your_date>>^^xsd:datetime" more useful. I think the main usage of this query is to find the artifacts that were modified recently, or the newest artifacts on the stream, which is not accurate at the moment due to the fact that the modifications visibility in the stream depend on the delivery date (which is arbitrary to the user that owns the change set), which is not present anywhere in the artifact fields.

It would be very useful to have the modification date update with the date of the change set delivery, or it would be equally as useful to have a new field with the purpose of "remembering" the last delivery date of the artifact in the stream, which should be able to be used in the oslc query shown above.

This feature would greatly decrease run time for programs that take the data using the DNG API as well as decrease the number of API calls for the server due to the fact that now the user knows exactly what artifacts to query instead of going through all artifacts to see what's new.

This would improve performance of DNG and tools involving it all around.

Idea priority High
Needed By Quarter
  • Post comment
  • Guest
    Reply
    |     Feb 12, 2024

    I would not want the modified date to change when delivering across streams because the content of the requirements didnt change. I would perfer a delivery date and not changing the modified date. I think the modified date should match the history in the change set itself. When you go to changed resources and expand the artifact changed there are dates for changes found there. Delivery does not change the artifact so the modified date should not change due to delivery. If this is needed create a new attribute it actually would be great to understand when a change set was delivered to each stream it was delivered to. have this attribute displayed under Changes contained in tab of the chagne set.

  • Guest
    Reply
    |     Jul 14, 2023

    an example:

    A colleague makes a change set 3 months ago, modifies his items in there, and doesn't deliver the change set until today.

    Today when he delivers the change set, practically the newest artifacts are the ones he delivered today, even if the modifications were ready since 3 months ago because the reference for everyone is the stream, not the change set.

    The result is that the artifacts from the delivered change set modified date of 3 months ago are newer than an artifact that was modified and delivered yesterday and this is not reflected at all in any way in DNG unless you go manually to see which change set has been delivered, which is not a good, fast, or efficient way of finding data.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.