Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-12663

Ability to freeze pages from future changes

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      I have had a discussion with some colleagues who currently use Twiki and are evaluating Confluence. Currently pages cannot be 'frozen' to prevent future modification.

      Scenario: a monthly status page contains dynamically generated information from other sources. eg a jira issue list. After 6 months we want to see the first report, but it is executing the jiraissues list again and shows current data.

      I use the jiraissues macro as an example, but any dynamically retrieved value (eg metadata, SQL etc) could equally be used. I wonder how hard it would be to for example 'save' the post-rendered page content that could be retrieved and rendered 'as was' rather than 'as is'.

      Such 'frozen pages' could be available in a similar way to page revisions.

      Tinylink support could could also be extended to support not only 'frozen pages' but also revisions, allowing 'permanent tinylinks to always resolve given content at a point in time.

            [CONFSERVER-12663] Ability to freeze pages from future changes

            Sen Geronimo made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3580378 ] New: JAC Suggestion Workflow 3 [ 4329245 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3185887 ] New: JAC Suggestion Workflow 4 [ 3580378 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3037824 ] New: JAC Suggestion Workflow 2 [ 3185887 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2534106 ] New: JAC Suggestion Workflow [ 3037824 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2294291 ] New: Confluence Workflow - Public Facing v4 [ 2534106 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2189208 ] New: Confluence Workflow - Public Facing v3 [ 2294291 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1919355 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2189208 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1752769 ] New: Confluence Workflow - Public Facing v3 [ 1919355 ]
            jonah (Inactive) made changes -
            Description Original: I have had a discussion with some colleagues who currently use [Twiki|http://www.twiki.org] and are evaluating Confluence. Currently pages cannot be 'frozen' to prevent future modification.

            Scenario: a monthly status page contains dynamically generated information from other sources. eg a jira issue list. After 6 months we want to see the first report, but it is executing the jiraissues list again and shows _current_ data.

            I use the _jiraissues_ macro as an example, but any dynamically retrieved value (eg metadata, SQL etc) could equally be used. I wonder how hard it would be to for example 'save' the post-rendered page content that could be retrieved and rendered 'as was' rather than 'as is'.

            Such 'frozen pages' could be available in a similar way to page revisions.

            Tinylink support could could also be extended to support not only 'frozen pages' but also revisions, allowing 'permanent tinylinks to always resolve given content at a point in time.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-12663].
              {panel}

            I have had a discussion with some colleagues who currently use [Twiki|http://www.twiki.org] and are evaluating Confluence. Currently pages cannot be 'frozen' to prevent future modification.

            Scenario: a monthly status page contains dynamically generated information from other sources. eg a jira issue list. After 6 months we want to see the first report, but it is executing the jiraissues list again and shows _current_ data.

            I use the _jiraissues_ macro as an example, but any dynamically retrieved value (eg metadata, SQL etc) could equally be used. I wonder how hard it would be to for example 'save' the post-rendered page content that could be retrieved and rendered 'as was' rather than 'as is'.

            Such 'frozen pages' could be available in a similar way to page revisions.

            Tinylink support could could also be extended to support not only 'frozen pages' but also revisions, allowing 'permanent tinylinks to always resolve given content at a point in time.
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-12663 [ CONFCLOUD-12663 ]

              Unassigned Unassigned
              4065af06a75f Andy Brook (Javahollic Software)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: