Cannot delete attachments on a cloned object

Hi @Aaron Pavez _ServiceRocket_

Thanks for the quick reply! I am not an admin. However, normally I can delete attachments on tickets where I am the reporter.

That might be true on one space. But all spaces can have different permissions scheme.

This could be the case. If not, let us now if your admin sees everything ok. then we can dig for problems.

Regards

The variable probably isn't the space, it's that one attachment, and there's a test that separates the two in about a minute.

Jira splits attachment deletion into two permissions and they behave very differently. "The Delete own attachments permission allows users to remove attachments they've added to a work item." The other is "The Delete all attachments permission allows users to remove attachments from any work item in a space."

Your own description points at the gap. You said you can normally delete attachments "on tickets where I am the reporter", and being the reporter is not what that permission is scoped to. It is scoped to attachments you added. On your own tickets that is usually the same set of files, so the two look identical until something separates them. A clone separates them: you are very likely the reporter of the new ticket, while the inherited attachment was uploaded by someone else on the original. That reading comes from the permission wording, and the clone docs don't spell it out, so treat it as the thing to test.

So here's the test. Attach anything of your own to that same cloned ticket. A screenshot will do. If you can delete the one you added but still not the inherited one, the difference is the attachment's origin and Aaron's space-by-space theory can be set aside for this case. If you can't delete either, then it is the scheme after all and his question about which space you're in becomes the right one.

Either way you'll know which conversation to have with your admin, and "please grant Delete all attachments on this project" is a much easier ask than a general one.