• 7
    • 3
    • 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.

      Hello,

      in our confluence installation we have many spaces. One of the big spaces has a fixed tree structure. On certain tree levels we have moderators that are responsible for their area (means for all the pages below a certain page - descendants).
      Due to the size of the area a moderator would like to see recently created and updated pages of his area. One of the options would be to use labels, but a lot of people do forget to label their pages and those pages should also be found and reviewed by the moderator.
      We would like to have recently-updated macro supporting similar parameters like metadata-report macro: in particular root and pages options (http://confluence.atlassian.com/display/CONFEXT/Metadata+Plugin#MetadataPlugin-Macrokeywords).

      Up to now, recently-updated macro is only usable for small spaces with a few edits.

      Thanks,
      Yuri

      Atlassian Update - January 2019

      Hi all,

      Thanks for your interest in this issue. We appreciate that this request may bring many benefits to you. However, we're unable to implement all the suggestions.

      We don't plan to work on this for the foreseeable future, but we will review this suggestion again in 12 months time and provide an update if the status changes.

      Confluence Server Product Management

            [CONFSERVER-9005] recently-updated macro to support confluence hierarchy

            I came across this post from Kristian Holbek whilst trying to solve this problem: https://community.atlassian.com/t5/Confluence-questions/Recent-Update-macro-for-Page-and-children-only/qaq-p/670735

            It worked well enough for me and may help others.

            Essentially, use the Contributors Summary macro with the following: 

            • Group By: pages
            • Columns to Display: lastupdate
            • Sort By: update
            • Include Page Hierarchy: descendants
            • (other parameters up to you)

            The tabular layout may not appeal to everyone, though.

            Richard George added a comment - I came across this post from Kristian Holbek whilst trying to solve this problem: https://community.atlassian.com/t5/Confluence-questions/Recent-Update-macro-for-Page-and-children-only/qaq-p/670735 It worked well enough for me and may help others. Essentially, use the Contributors Summary macro with the following:  Group By : pages Columns to Display : lastupdate Sort By : update Include Page Hierarchy : descendants (other parameters up to you) The tabular layout may not appeal to everyone, though.

            labedzkim added a comment -

            +1

            labedzkim added a comment - +1

            +1 for PayPal

            Katie Crick added a comment - +1 for PayPal

            almost 14 years  

            Dennis Mersjann added a comment - almost 14 years  

            The ability to narrow the 'recently updated' list from the whole space to the child pages is a functionality we would like to see.

            Jeff Shepherd added a comment - The ability to narrow the 'recently updated' list from the whole space to the child pages is a functionality we would like to see.

            +1

            Sari Ahokas added a comment - +1

            +1

            +1

            13 years for a small feature...

            Maryia Yermakovich added a comment - +1 13 years for a small feature...

            +1. The alternative is to split a space with lots of shared content into separate spaces. That's not desirable.

            Given that the last update was now just over a year ago, and it stated, "we will review this suggestion again in 12 months time," I'm hoping you all at Atlassian would be willing to reconsider. This is a relatively small feature request with a lot of benefit.

            Brian Stults added a comment - +1. The alternative is to split a space with lots of shared content into separate spaces. That's not desirable. Given that the last update was now just over a year ago, and it stated, "we will review this suggestion again in 12 months time," I'm hoping you all at Atlassian would be willing to reconsider. This is a relatively small feature request with a lot of benefit.

            +1

              Unassigned Unassigned
              e8c00d057bf9 Yuri Ziryukin
              Votes:
              229 Vote for this issue
              Watchers:
              131 Start watching this issue

                Created:
                Updated: