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

      We have cases where we would like to include excerpts into summary pages that are located in different spaces.

            [CONFSERVER-5752] Allow the excerpt-include macro to work across spaces

            Sanet Minnie added a comment - - edited

            This macro allows you to use excerpt across spaces:

            {report-info:value:content "spacekey:somepage" > excerpt |render=wiki}

            Compliments to Charles Hall

            Sanet Minnie added a comment - - edited This macro allows you to use excerpt across spaces: {report-info:value:content "spacekey:somepage" > excerpt |render=wiki} Compliments to Charles Hall

            David Taylor (Inactive) added a comment - - edited

            The fix for this has been made against https://studio.plugins.atlassian.com/browse/ADVMACROS-249 (for the advanced macros plugin) and is currently in tech review. Once the review is successful and the plugin is released, this improvement should be available for new versions (4.2.x, 4.3.x) of Confluence.

            David Taylor (Inactive) added a comment - - edited The fix for this has been made against https://studio.plugins.atlassian.com/browse/ADVMACROS-249 (for the advanced macros plugin) and is currently in tech review. Once the review is successful and the plugin is released, this improvement should be available for new versions (4.2.x, 4.3.x) of Confluence.

            It looks to me like we cannot make this work for the "excerpt in secure space" use case without resolving CONF-7089, or some variant of it specific to the excerpt macro. Otherwise only users with permission to see the secure space will be able to view excerpts from it.

            Richard Atkins added a comment - It looks to me like we cannot make this work for the "excerpt in secure space" use case without resolving CONF-7089 , or some variant of it specific to the excerpt macro. Otherwise only users with permission to see the secure space will be able to view excerpts from it.

            +1 This would be very helpful. As we grow our instance, I often attempt to use this function and then wonder why it doesn't work, before remembering, "oh yeah, Confluence can't do that." We always find a work-around, but it usually involves less-than-ideal information architecture or processes dependent on humans remembering not to duplicate things. Would be great if Confluence could streamline / people-proof this for us.

            Also, as Tobias mentioned, an excerpt-include that respects permissions will be useful for us to include secure information from one space into another, with only the correctly-permissioned users able to see it in when it's included in a more public space.

            Alison Reid added a comment - +1 This would be very helpful. As we grow our instance, I often attempt to use this function and then wonder why it doesn't work, before remembering, "oh yeah, Confluence can't do that." We always find a work-around, but it usually involves less-than-ideal information architecture or processes dependent on humans remembering not to duplicate things. Would be great if Confluence could streamline / people-proof this for us. Also, as Tobias mentioned, an excerpt-include that respects permissions will be useful for us to include secure information from one space into another, with only the correctly-permissioned users able to see it in when it's included in a more public space.

            Just tried the report-info workaround mentioned on the Excerpt Include Macro page – that failed since my excerpts include metadata-from macros (using the Metadata Plugin 2).

            Bill: I agree that this is a bug, not a feature request.

            With almost 97 votes (27th overall for Confluence) and 10 comments this year on an issue that is 6+ years old, it would be nice to hear from Atlassian on the subject.

            Solipsys Atlassian Administrators added a comment - Just tried the report-info workaround mentioned on the Excerpt Include Macro page – that failed since my excerpts include metadata-from macros (using the Metadata Plugin 2). Bill: I agree that this is a bug, not a feature request. With almost 97 votes (27th overall for Confluence) and 10 comments this year on an issue that is 6+ years old, it would be nice to hear from Atlassian on the subject.

            This is especially important to include information from secure spaces.

            RTS Technik added a comment - This is especially important to include information from secure spaces.

            To prevent duplication of information and to make it easier for users to obtain data without having to click to a different page, we need to include excerpts from other spaces. When processes have interactions with different teams, the ability to reference instead of duplicate information is crucial to ensure documentation is correct and up-to-date.

            Deidre East added a comment - To prevent duplication of information and to make it easier for users to obtain data without having to click to a different page, we need to include excerpts from other spaces. When processes have interactions with different teams, the ability to reference instead of duplicate information is crucial to ensure documentation is correct and up-to-date.

            Really really need this at GE, where we are rolling out JIRA for thousands of users.

            Patrick Boyd added a comment - Really really need this at GE, where we are rolling out JIRA for thousands of users.

            Very very true. My point was that IMHO, the macro is broken and not that it just needs some new features. And that bugs should get much higher priority than an "enhancement request" dating from 2006.

            Bill Bailey added a comment - Very very true. My point was that IMHO, the macro is broken and not that it just needs some new features. And that bugs should get much higher priority than an "enhancement request" dating from 2006.

            Bill: It's probably not important if it's a bug or an improvement as long as it's tackled in the near future ...

            Martin Seibert added a comment - Bill: It's probably not important if it's a bug or an improvement as long as it's tackled in the near future ...

              dtaylor David Taylor (Inactive)
              d385a602ce3a Bob Potter
              Votes:
              111 Vote for this issue
              Watchers:
              73 Start watching this issue

                Created:
                Updated:
                Resolved: