Project

General

Profile

Actions

Defect #29913

closed

Adding image with same name as previous one replaces embedded image

Added by Benedikt Breinbauer over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Attachments
Target version:
-
Start date:
2010-01-20
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

Copied from #4618 which is closed but still appeared on Redmine version 3.4.5

Steps taken that produce this behavior,

  1. An issue has an attachment made to it (usually in my case, a screenshot)
  2. Another attachment is made, with the same filename as the one from above.

At this point, the new image replaces the other one, and references to it now point to the new one. What I'd want to see is that the new attachment gets renamed so that it doesn't displace the old one.

Very problematic for issue comments with embedded screenshots: the newer screenshot automatically replaces the old one so makes the old comment confusing/useless without the old original screenshot that the comment was intended for, essentially changing the comment history.

Extra information:

Redmine version                3.4.5.stable
Ruby version                   2.3.7-p456 (2018-03-28) [x86_64-linux]
Rails version                  4.2.8
Environment                    production
Database adapter               Mysql2


Related issues

Copied from Redmine - Defect #4618: Adding an Attachment to an Issue of the Same Name as Another Attachment OverwritesClosed2010-01-20

Actions
Actions #1

Updated by Benedikt Breinbauer over 5 years ago

  • Copied from Defect #4618: Adding an Attachment to an Issue of the Same Name as Another Attachment Overwrites added
Actions #2

Updated by Go MAEDA over 5 years ago

Please see #4618#note-2. Jean-Philippe Lang wrote that the behavior is by design, not a defect.

Indeed, this behaviour was introduced in r1939.
This is especially usefull in wiki pages when you want to update a screenshoot without having to edit the page.

Actions #3

Updated by Go MAEDA over 5 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate
Actions #4

Updated by Benedikt Breinbauer over 5 years ago

Please see the repsonse to this behaviour by design #4618#note-3 which reopened the ticket:

I understand the benefit of being able to update screenshots without having to update the page. But I think the disadvantage of not being able to simply attach a file to an update and reference it without having to worry about unique file names weighs more heavily. Especially considering the difficulties novice users are typically having.

Which is exactly what trips up our users… they are changing comment history by uploading a new image…

Actions #5

Updated by Benedikt Breinbauer over 5 years ago

  • Status changed from Closed to Reopened
Actions #6

Updated by Go MAEDA over 4 years ago

  • Status changed from Reopened to Closed

Closing as a duplicate of #4618.

Actions

Also available in: Atom PDF