Add Audit Trail for Component Ownership and Rename Changes in Stream History

Issue Summary

The request concerns a gap in the auditability and traceability of IBM EWM SCM component changes within stream history.

Background

Several support cases, including BMC tickets 667909 and 740265, have occurred because users accidentally changed the ownership of a component from a shared Stream to an individual user account.

Although ownership changes are restricted to administrators, mistakes still happen.

Problem 1: Component Ownership Changes Are Not Traceable

When a component's ownership is changed to a personal user:

• The component becomes invisible to all other users.
• The Stream's Operation History only displays an "" entry.
• The history does not identify:
  • Who changed the ownership.
  • When the change was made.
  • Who the new owner is.

As a result, administrators have no reliable way to determine what happened when a component suddenly disappears from a stream.

Problem 2: Component Rename Operations Are Not Traceable

When a component is renamed:

• The new name immediately appears everywhere the component is used.
• This includes historical artifacts such as snapshots and baselines.
• Neither the Stream history nor the Component history records:
  • That a rename occurred.
  • Who performed the rename.
  • When the rename happened.
  • What the previous component name was.

This makes it difficult to investigate unexpected changes or understand the historical evolution of a configuration.

Previous Investigation

The issue was reported to IBM through support case TS022786098.

IBM's response was:

• The behavior is known.
• An internal enhancement request already exists.
• The current workaround is to restrict ownership and rename privileges to trusted users.
• If additional functionality is required, it should be submitted as a Request for Enhancement (RFE) rather than treated as a defect.

Requested Enhancement (RFE)

The requested enhancement is to provide a complete audit trail for component modifications.

Specifically:

1. All component modifications should be recorded in the Stream Operation History.
2. Ownership changes should show:
   • Previous owner
   • New owner
   • User who performed the change
   • Timestamp
3. Rename operations should show:
   • Previous component name
   • New component name
   • User who performed the rename
   • Timestamp
4. These events should be visible in every stream where the component is used.
5. The history must remain available even if the component later becomes inaccessible.

Business Impact

Without this capability:

• Root-cause analysis of missing or inaccessible components is difficult.
• Accidental ownership changes can disrupt multiple users.
• Renames can alter the visible history of configurations without leaving an audit trail.
• Administrators lack the transparency required for governance and troubleshooting.

In one sentence: The RFE requests comprehensive audit logging for component ownership changes and renames so that streams provide a reliable, user-visible history of all component modifications.