Could you please explain why we can't delete attachment version that contain comments?

[Alexey Aleinikov]

It's not possible in Confluence to delete the attachment version with comments. We've reproduced this issue in Confluence 7.13.1 and even Confluence 6.13. Is this a bug or a feature and will it be fixed in the future? An example is provided in the video https://monosnap.com/file/eg8WHCU6Hh6tFq85D8m5GoRNPTQ26P.

[Nic Brough -Adaptavist-]

Could you tell us what errors you get in the logs?  (Not in a video - just the plain text)

[Alexey Aleinikov]

Here are the logs:

https://docs.google.com/document/d/1yC-Qdg4xaAmHoDl9v9ot2ax_IhVTm5-ihMZ_R1Y0VmY/edit

[Alexey Aleinikov]

Btw, we got this bug when we tried to delete exactly the latest attachment version with comment replies.

[Alexey Aleinikov]

Also, the latest attachment version with comment replies can't be previewed after we try to delete it, see video https://www.screencast.com/t/DdfndCOTCvbt

[Nic Brough -Adaptavist-]

Hmm.  I think this needs to go to Atlassian, as it looks like a bug in hibernate.

I would want to check your database is configured correctly, as there is a warning about propagation at the end, but I don't think that is causing the problem, and the admin configuration checks would be warning you if they were.

[Alexey Aleinikov]

"I would want to check your database is configured correctly, as there is a warning about propagation at the end, but I don't think that is causing the problem,"

I've checked on fresh Confuence instances with H2 and Postgres DB and in both cases this issue occurs

[Alexey Aleinikov]

"Hmm.  I think this needs to go to Atlassian, as it looks like a bug in hibernate."

What should we do next with this bug?

[Nic Brough -Adaptavist-]

I'd want to generate the support/troubleshooting support file and raise it over at https://support.atlassian.com/contact

[Alexey Aleinikov]

What is a "support/troubleshooting support file"? Is it just a question in https://support.atlassian.com/contact/#/?

"I'd want to generate the support/troubleshooting support file and raise it over at https://support.atlassian.com/contact"

Could you please do it? Or I should do it? Do you need any additional information from my side? 

[Nic Brough -Adaptavist-]

I'm not your Confluence admin!  I can't do any of this!

You might find it easiest to log in as an admin though, you can go to Admin -> General config -> Troubleshooting and support tools -> Get help, and there's a little wizard that will run you through creating the call

Whichever way you want to do it, creating a call manually, or via the wizard in the application, have a read through https://confluence.atlassian.com/doc/troubleshooting-problems-and-requesting-technical-support-776659671.html - it's quite helpful in pre-empting what support may come back to you with!

[Alexey Aleinikov]

"I'm not your Confluence admin!  I can't do any of this!"

But this issue is not related only to my Confluence instance. This bug occurs in any instance even if Confluence is fresh i.e. newly installed also my colleagues also reproduced this bug.

Also tested this issue in H2 and Postgres DB and in both of them this issue occurred.

[Nic Brough -Adaptavist-]

That's of no relevance to who should report it.

There's no point in me reporting it - the Confluences I've got admin on (and also the ones I do not) don't have this problem as far as I can tell, so me reporting it would be a waste of everyone's time.