# Epic OP-10869 - Provide means of informing the user about concurrent changes / events

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-10869

## Detailed specification

### Motivation and background information

### Acceptance criteria

### Out of scope

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap |  |
| Date |  |
| Votes |  |
| List |  |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Designer |  |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

When editing a project, work package, wiki page or similar, users are not notified or parallel changes on resources until they try to hit save. For wikis and work packages, optimistic locking is in place to at least prevent concurrent modifications. On other pages, changes are simply being replaced.

This is a potentially huge effort, but a use-case that is commonly resulting in confusion and/or frustration due to changes being lost and might warrant a discussion.
