The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Please reopen CONFSERVER-22874 and make page version history use immutable versions of images

jason_s
June 6, 2022

As of Confluence 7.13.0, you can upload a new and completely different version of an image, and it will not change the page history: if you are working on a page named Foo and it is currently at version 2, and you upload a newer version of an image, 

This is a serious bug. It means that the items in the page history are not immutable, and they can change image content, without any way to go back and audit and see exactly what the page looked like as of a particular point in time.

Please reopen CONFSERVER-22874, which was identified in 2011 but dismissed as "Not a bug".

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
June 6, 2022

The Community is not a place to ask for this, it's not where Atlassian looks for getting features or ideas, and it's definitely not anything they look at as a source for "please reopen".

The behaviour you describe is not what Confluence is designed for, hence the "close, not a bug" response.  I don't think you're going to get any traction on this one here.

TAGS
AUG Leaders

Atlassian Community Events