Disable automatic renmaing of file attachments to the a ticket

[nmoni]

I have preface the question by saying that we just moved to the cloud version of JIRA. Prior to this we were on a privately hosted instance of JIRA.

When I attached a file to ticket for the first time, the file name is attached as is.

When I try to attach the same file name again (we do that to maintain different versions of the file on the same ticket, so each time we attach the file, the contents are slightly different depending on the changes made by different people), the file gets automatically altered to append a GUID at the end of the file name. This causes problems since the various files do not associated together

Is there any way to prevent the rename? The previous version did not have this issue. The previous version allowed all the previous versions to retain the original name and only display the latest version in blue, but the older version were converted to a light gray. Is it possible to get that behavior using the version on the cloud?

[Angélica Luz · Accepted solution]

Hello @nmoni,

Welcome to Atlassian Community!

Testing on my local site, I was able to replicate the same issue. When viewing using the Strip View, the names shows correctly, but when switching to the List View, it shows the difference.

Currently, there is no workaround for that. It would be necessary to create a copy of the attachment and change its name.

There is a known bug related to this issue:

• Attachment link in comment breaks if another attachment with same name is added

 Please, click on “This affects my team” and also watch to receive updates.

Kind regards,
Angélica

[nmoni]

Thank you for that response. I appreciate the transparency with that bug. I am keenly interested in the fix for this issue since this impacts our operations team in a big way.

When I tried to click on the "This affects my team" button, I was made aware that this would expose my profile. I want to avoid that. Hence I am not clicking on that that button. 

Thank you for your help with this issue.

[nmoni]

Is there any progress on this issue? If there are no plans to fix this issue in the foreseeable future (1-4 years), please state that explicitly so that the users can make their decisions accordingly and not hold out hope..