Bug: Kanban board caches attachment image after attachment deleted


#1

In Kanban board view, tasks with an attached image display an image on the card.

If the image is subsequently deleted from the task, for example if it was added in errror, the image persists in the Kanban board view, so no longer represents the task.

It should recache the card and remove the image.


#2

Hi @ant.grimley,

I might be misunderstanding your issue, but it seems to work fine for me. I pasted a screenshot into a comment and you can see it in the card in the background:

Then I deleted the “image.png” file by hovering over it in the Attachments section (under the Project section denoted by the paperclip) and clicking the “X”:
image

I’ve had team members try to delete attachments by deleting the comment where the image is displayed in line with other comments rather than by removing it from the attachments section as shown above. This section gets overlooked and the fact you have to hover over the file to see the “X” I think compounds this somewhat.

Here you can see the image is removed after i click the “X”:
image

Another thing I can think of is duplicate images in the task. I have this happen all the time with forwarded emails. If there’s anything listed in the attachments section it’ll pick something.

Lastly, you can also remove an image on a card (this doesn’t really address your issue, it’s just some extra info):
image

Hopefully something here helps you. If not I’d agree you have stumbled onto a bug I haven’t seen myself yet.


#3

Hi @ant.grimley and welcome to the Forum!

I’m getting the same result than @RyanE, the image disappears as soon as I delete it from the task.
Could you confirm what browser you’re using? Also, would you mind checking if you’re having the same problem with another browser?

Againb, sorry for the truble, looking forward ot your reply!


#4

Ah. I see. It is user error.

I deleted the Story where the attachment was in the Task. But doing that does not delete the attachment itself. That makes sense now.

Thanks for your time.


#5

Thanks for keeping us posted @ant.grimley!