Content
View differences
Updated by Wieland Lindenthal over 1 year ago
### Steps to reproduce
~~The The steps to reproduce are still to be discovered. It was observed on the private work package~~ ~~#53384~~ ~~where package <mention class="mention" data-id="53384" data-type="work_package" data-text="#53384">#53384</mention> where I asked for some clarifications. I can confirm that the file link was created by a different user than the one who gets named in the Activity log. It is interesting that there are hours in between the upload of the file and the status update. Were there down times of the background workers, maybe? Or why did the aggregation happen so late? And why wasn't it assigend to the correct acting person?~~ person?
### What is the buggy behavior?
* User A uploads files to a file storage storages and creates the link.
link
* We wait for a time that is bigger than the journal aggregation time (so more than the default 5min)
* User A renames the file within the file storage itself
* User B goes to the Files tab of the work package (and thus pulls in the latest changes on the linked files into OP's file meta info cache)
* User B updates the work package's status or any other journaled attribute
### What is the buggy behavior?
* hours later. The journal entry for updating the status also aggregates the creation of the file links. So it looks as if user B had created the file links, which is not true.
### What is the expected behavior?
1. The linking of files should have been attributed to user A.
###
~~The
* User A renames the file within the file storage itself
* User B goes to the Files tab of the work package (and thus pulls in the latest changes on the linked files into OP's file meta info cache)
* User B updates the work package's status or any other journaled attribute
### What is the buggy behavior?
*
1. The linking of files should have been attributed to user A.