Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-31438

Content Report Table macro should have sorting parameter

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      We are regularly using the "Meeting Notes" feature, which allows to have a Content Report Table listing all meeting notes from a given project. We noticed that the order of meeting notes does not correspond to the order of the meetings, if we do not explicitly sort by the page title column (all page titles start with the yyyy-mm-dd date of the meeting).
      It would be great if there was the possibility to preconfigure the sorting state in the Content Report Table macro. (The default could stay the same, but for meeting notes, I would prefer to have the page title be sorted.)

      Atlassian Update - 27 June 2019

      
Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Confluence. We agree, having a sorting parameter on content report table macro is something that is useful.
       
      This is something we would like to implement, but this suggestion is not currently on the Confluence roadmap. Please remember that jira.atlassian.com is one of many inputs for the Confluence roadmap. We will update this issue as we make further progress on it.  


      Attachments

        Issue Links

          Activity

            People

              aknight@atlassian.com Alex K
              805011b77b59 hans.meine
              Votes:
              229 Vote for this issue
              Watchers:
              148 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: