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

      This is for cases when customers are not using the standard Confluence dashboard.

      User would like to have a Popular Content macro that they could use to create popular content streams similar to the one on the Confluence Dashboard.

            [CONFSERVER-25791] Add "Popular" tab to the Recently Updated Dashboard Macro

            Atlassian Update - 26 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.

            Kind regards,
            Confluence Data Center

            George Varghese added a comment - Atlassian Update - 26 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Confluence Data Center

            +1 to integrate the Most Popular Pages to the Recently Updated Dashboard Macro.

            We use the Custom Dashboard AddOn to display any page as a dashboard, ie. without the left space navigation & have a group-based scheme to have different dashboards for different user groups (Beginner/Reader Only, Standard, Advanced, Individual, Admin). Integrating the most popular pages gives us more room for other components.

            Jan-Peter Rusch added a comment - +1 to integrate the Most Popular Pages to the Recently Updated Dashboard Macro. We use the Custom Dashboard AddOn to display any page as a dashboard, ie. without the left space navigation & have a group-based scheme to have different dashboards for different user groups (Beginner/Reader Only, Standard, Advanced, Individual, Admin). Integrating the most popular pages gives us more room for other components.

            need to see popular but only for spaces user is linked to.

            Olivia Sumlin added a comment - need to see popular but only for spaces user is linked to.

            We would also like to be able to insert Popular by itself just as we do favorites or other options.

            Michelle Vincent added a comment - We would also like to be able to insert Popular by itself just as we do favorites or other options.

            We really need this too. Same issue as Stefan and Broadcom Support.

            Chris Gregg added a comment - We really need this too. Same issue as Stefan and Broadcom Support.

            I think the dashboard is just an unnecessary hassle. Please make all the dashboard components available as macros such that users can easily build their own dashboard and utilize the same information.

            Stefan Braunewell added a comment - I think the dashboard is just an unnecessary hassle. Please make all the dashboard components available as macros such that users can easily build their own dashboard and utilize the same information.

            We need this too. We use a page in a space as the dashboard. The global.vm just does an include of that page. The $mode variable used by the recently-updated-dashboard macro cannot be manually overridden, so we can't see "Popular" on our dashboard.

            Why is it important to manage the dashboard as a page in a space? Version history. Easily customized layout. Can be edited by admins for that space, not just confluence-administrators. Can be editing in the Confluence native editor. Can be backed up by space export. Soooo, lots of reasons.

            Filtering popular by space would be nice to have, but is not required for the specified use case.

            Broadcom Support added a comment - We need this too. We use a page in a space as the dashboard. The global.vm just does an include of that page. The $mode variable used by the recently-updated-dashboard macro cannot be manually overridden, so we can't see "Popular" on our dashboard. Why is it important to manage the dashboard as a page in a space? Version history. Easily customized layout. Can be edited by admins for that space, not just confluence-administrators. Can be editing in the Confluence native editor. Can be backed up by space export. Soooo, lots of reasons. Filtering popular by space would be nice to have, but is not required for the specified use case.

            This wasn't done because the popular stream cannot be filtered by space (yet). I've filed an issue for this: CONF-26272

            dave (Inactive) added a comment - This wasn't done because the popular stream cannot be filtered by space (yet). I've filed an issue for this: CONF-26272

            The use case is simple. The standard dashboard delivers a stream of popular content including the number of likes and the number of comments. Without using the standard dashboard you cannot see this information. So when there is a use case for Confluence's standard dashboard, there should be a use case for sites not using the standard dashboard as well.

            Stefan Fleckenstein added a comment - The use case is simple. The standard dashboard delivers a stream of popular content including the number of likes and the number of comments. Without using the standard dashboard you cannot see this information. So when there is a use case for Confluence's standard dashboard, there should be a use case for sites not using the standard dashboard as well.

            BillA added a comment -

            what's the use case for this one, folks? Where do people want to put this macro?

            BillA added a comment - what's the use case for this one, folks? Where do people want to put this macro?

              Unassigned Unassigned
              jmasson@atlassian.com John Masson
              Votes:
              37 Vote for this issue
              Watchers:
              32 Start watching this issue

                Created:
                Updated:
                Resolved: