Content
View differences
Updated by Alexander Coles 6 months ago
## **Problem**
When work packages are updated, webhooks (including Slack notifications) incorrectly show the original work package **author** instead of the **user who made the update**. This causes confusion as teams cannot identify who triggered the notification.
### **Discovered in Production**
I'm a sysadmin running OpenProject in production and noticed this issue when users complained that Slack notifications were showing the wrong person for work package updates.
## **Root Cause**
The bug was introduced in commit [e3adc26](https://github.com/opf/openproject/commit/e3adc266780196297e459715af2e2e569bacd7a3) (Nov 13, 2019) when the webhook event handler was changed to pass the `work_package` object instead of the `journal`. The journal contains the updater's `user_id`, which was being lost.
### Note for QA
This is only reproducible at an API level - so the fix will need to be verified by a dev.
### Environment information
**OpenProject installation type**
* n/a
**OpenProject version**
_dev_
When work packages are updated, webhooks (including Slack notifications) incorrectly show the original work package **author** instead of the **user who made the update**. This causes confusion as teams cannot identify who triggered the notification.
### **Discovered in Production**
I'm a sysadmin running OpenProject in production and noticed this issue when users complained that Slack notifications were showing the wrong person for work package updates.
## **Root Cause**
The bug was introduced in commit [e3adc26](https://github.com/opf/openproject/commit/e3adc266780196297e459715af2e2e569bacd7a3) (Nov 13, 2019) when the webhook event handler was changed to pass the `work_package` object instead of the `journal`. The journal contains the updater's `user_id`, which was being lost.
### Note for QA
This is only reproducible at an API level - so the fix will need to be verified by a dev.
**OpenProject installation type**
* n/a
**OpenProject version**
_dev_