OneDev handles attachment move in this case. Can you please let me know the reproducing steps?

you're right, in most cases it works. Sorry, for not being elaborate enough. I just looked through a ton of issues just being moved..

however, in rare cases it still hangs in the old project

• create an issue in project parent/A (id = 98)
• add attachment and reference it in a comment/describtion
• got to issue list, select and "move selected issues" to project parent/B (id = 194)
• open issue in project parent/B

-> the reference within the comment/description was updated and now links to

/~downloads/projects/194/attachments/490cc170-90f0-4f0b-b5b9-cedda47b8371/logs_prozesse.zip?v=1743744294760

when I look in the attachments folder it's still at the old project

/site/projects$ ls -l 194/attachment/permanent/49/
total 16
drwxr-xr-x 2 onedev root   4096 Nov 14 09:56 49035c09-b8b2-4088-be33-a55ca1f438e0
drwxr-xr-x 2 onedev onedev 4096 May  9 14:07 491743b4-427c-4b9a-9088-089cb1d0d4cf
drwxr-xr-x 2 onedev root   4096 Dec 17 15:42 4949b7c6-1e21-4537-8d34-b3689f21ee0a
drwxr-xr-x 2 onedev root   4096 Mar 11 16:24 49f73330-f83e-4cb2-afeb-c89fac10b588

/site/projects$ ls -l 98/attachment/permanent/49/490cc170-90f0-4f0b-b5b9-cedda47b8371/
total 9112
-rw-r--r-- 1 onedev root 6531945 Apr  4 07:24 logs_prozesse.zip

that only happens randomly, and I can neither say it's based on file extension nor anything else. In some cases 3 out of 4 attachments get moved and 1 doesn't.

we did move many issues in bulk though

The attachment may take some time to move if many issues are moved. If you can get me a reliable reproducing procedure, it will help a lot.

Sorry, I just can't come up with a reliable scenario.