You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi All,
I am looking to upload DIFFERENT files with same name but it keeps creating new versions of it due to name being the same. Is there anyway to alter this behaviour have have either: auto unique rename or an alert if a version of file already exists?
Hi @Aqib_sherwani
This is an extract from the documentation
If you upload a file with the same name as an existing attachment on the same page, Confluence will overwrite the existing attachment. Version history is kept for all attachments. See Manage Filesto find out more.
Any changes you make to the source file will not affect the copy that was uploaded to Confluence. To update the Confluence copy, you need to upload the new version of the file.
So, there is no option to change this behaviour.
Why you want to do this?
Regards, Dominic
Not to hijack but I have some examples of why I'd want this.
Use case 1:
As a designer, I want to upload images to Confluence to solicit feedback.
As a designer, I want to update designs to the same file locally but keep a visual history of all changes on the Confluence page.
As a designer, I don't want to keep renaming a file locally just so it doesn't get overwritten on Confluence.
Use case 2:
As a designer, I want to upload screenshots taken with Skitch.
As a designer, I want all of my screenshots to appear as different images, not overwrite each other.
Having a system that either warns if you have the same filename being uploaded, renames the used files automatically or just allow multiple uploads with the same filename would be immensely helpful to some of us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Use case 1:
If you upload a file, the "old" file isn't gone. Every attachment has it's own history.
Use case 2:
I'm not aware, that there's a plugin which could display every version of an attachment. If you are on server, I'm sure it would be possible to write an user macro, which would display every version of an attachment.
Regards, Dominic
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would also vote for the possibility to add multiple files (pictures) with the same filename.
E.g. Auto-generated plots that are shown on a confluence pages have the same filename.
Azure Wiki renames the uploaded files to by itself. But this is also not good in every case. Maybe a suffix for each file, like a number or timestamp. Or a user switch, if files should be overwritten or timestamped?.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is expected behaviour.
If you want multiple files attached rather than multiple versions of the same file, give them different names.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Confluence should give a warning message when the files are overwritten by uploading another file with the same filename.
I hit a problem that 1) running a script to generate different images with different settings (still having the same filename), 2) pasting the images into two different places in the same page (to compare the result of the different settings of the script), and finally 3) seeing the same image in two places in the page, which confused me a lot.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.