Alert Ownership Locking and Conflict Prevention for Concurrent Users

Introduce an optional alert ownership locking and conflict-prevention mechanism to prevent multiple users from simultaneously taking ownership of the same alert without notification or coordination.

Current Behavior

During testing, the following behavior was observed:

1. User John selected Take Ownership on an alert.

2. The alert Owner field was updated to John.

3. Shortly afterward, user Rose selected Take Ownership on the same alert.

4. The alert Owner field was immediately updated to Rose.

5. Activity History correctly recorded both ownership actions.

6. The alert displayed only the most recent owner.

As a result, ownership follows a last-write-wins model where a subsequent user can overwrite an existing owner without warning, approval, notification, or conflict detection.

Business Problem

In enterprise Operations, NOC, and SRE environments, alert ownership is commonly used to indicate that an engineer is actively investigating an issue.

When ownership can be overwritten by another user:

• Multiple engineers may unknowingly work on the same alert.

• Investigation efforts can be duplicated.

• Accountability becomes unclear.

• Existing owners receive no notification that ownership was reassigned.

• Operational coordination becomes difficult during critical incidents.

Although Activity History records ownership changes, operators typically rely on the current Owner field when determining who is actively working on an alert.