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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Somewhat a symptom of not having in-tool review. Cannot prevent changes subsequent to review/approval but prior to delivery of a change set. Change set state is either open or delivered. No "Under review-don't make changes" state. Since have to do review outside the tool, hard to know that somebody made more changes. Hard to detect.
Have to do two reviews: The review and then a review that nothing was added after the review. Have to look at all the times of the changes vs the time of review and account for time zone of review. Not all changes have a time stamp associated with it. Links do not have timestamps: Have to go to artifact view to look at history.
Anyone can change a changeset after review. Nothing to prevent someone from making a change. No state during review. Have to do two reviews. One before delivery and one after delivery. Have to do second review based on time. Look at the change set and all the times of the changes compared to the time of the review. But, not all changes have a timestamp related to them, such as Links, so that time-based check doesn't guarantee it wasn't changed after review. Have to look at the history of every artifact. Need way to prevent the changes and a way to audit.
Idea priority | High |
Needed By | Yesterday (Let's go already!) |
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.
https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/doors-next/7.0.3?topic=artifacts-reviews#c_reviews__informal
"You can create a review from within a stream or a baseline."
If you need to ensure that artifacts are not modified during the review process, you should create the review from a baseline.
You could create a separate stream used only for the review process, separate from the "main" stream.
Make the updates in that stream, and when ready for review, create a baseline on that stream and create a review from that baseline.
Once the review is done and the baseline is approved. You can deliver of the approved change sets from that review stream to the main stream.