Cannot delete attachments on a cloned object
For our workflows, I'm cloning either tasks or bugs quite often. My issue is that if there is an attachment (video or picture) in the comments of a ticket, and then you clone it, the cloned ticket will have that attachment and I cannot delete it. This is rather frustrating because I don't need the old attachment on a new, cloned ticket. Is this issue known?
Below, you can see my mouse is hovering over the attachment and usually there is a trash bin icon to delete the attachment but here I cannot. This is a cloned ticket (bug) that I just created and the attachment was originally in a comment.
Best,
Drew
2 answers
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.
Hi @Drew Wilson !
The permission angle is already covered above, so I will not repeat it. Worth adding a different option, though, in case the cleanup keeps coming back.
Cloning copies the source work item, so you inherit whatever was on it, including attachments left over from a comment. For work you repeat often, like a recurring bug or task type, that cleanup never really goes away. However, you can avoid it if you use a work item template instead. In this case, new work items will be identical to the clean template, not to an old task where someone already worked before.
For cases like this we use our solution, Smart Templates for Jira. It allows you to save your work item(s) as a template with all its fields, description, and child work items. Then, you can create new Jira issues from that template in a click. Variables handle the parts that change between tickets, such as {{project}} or {{employee_name}}. Nothing from the previous ticket travels along.
Here is what this looks like in practice. This is a work item template we use for onboarding in our team. It includes a set of child work items and checklists (but your template can also consist of just one work item.) Variables are filled in automatically when the work item is created.
I also covered other approaches in my article, Your Guide to Cloning in JIRA: How to Clone Issues in Different Ways. It covers everything from cloning within a project and to another project to automated cloning, bulk cloning, and more. There is a section on the limitations of native cloning and where templates fit better, so it might be a useful read for you.
That's the approach that works for us. Let me know if you have any questions
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.