• Type: Suggestion
    • Status: Resolved
    • Resolution: Fixed
    • Affects Version/s: 1.1.2
    • Fix Version/s: 5.0
    • Component/s: None
    • Feedback Policy:
      Thanks for taking the time to raise a Suggestion for Confluence, Atlassian values your input.

      We receive feedback from a number of different sources and evaluate those when we plan our product roadmap. If you would like to know more about how the Atlassian Product Management team uses your input in our planning process, please see our post on Atlassian Answers.

      Before creating a new Suggestion, please search the existing issues to see if your suggestion already exists.

      The Confluence Product Management Team
    • Last commented by user?:


      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Currently you can revert to a version, but it only has the effect of taking the code from that version and adding it as the latest. The old revision is still accessible, which can be very problematic if the revision reverted from contains highly offensive information or dangerous code (eg: an abused macro, or insulting wording, or pornographic imagry).

      A way to remove revisions permenantly, or at least restrict revisions the same way that spaces are restricted would be benificial.

      The idea of revision security, gives me the idea of CONF-1572


          Issue Links



              • Votes:
                12 Vote for this issue
                9 Start watching this issue


                • Created:
                  Last commented:
                  4 years, 47 weeks, 2 days ago