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

      The ability to pull in all pages with a given label from anywhere in the system is great. But, a gotcha with this macro is that it is not restrictable to the current, or a given set of spaces. Unless great care is taken with labels (I don't see users prefixing their labels with a spacekey!) the result is a grouping of similar but totally unrelated content, which isn't helpful.

            [CONFSERVER-9354] NAVMAP needs to be restrictable to given spaces

            Adding comment to prevent low engagement close. Still interested in this

            Andrew Laden added a comment - Adding comment to prevent low engagement close. Still interested in this

            13 years and counting.

            We are looking at changing our ITSM system and Jira was one of the candidates until we found out how Atlassian manages Confluence.

            All Label Macros work different, some allow AND (Content by label) most allow OR some allow limiting by space others filter on other stuff.

            It would be preferable if all options where available to all Label Macros.

             

            This one seems like a very easy fix since most other label macros already does this. Jira as an ITSM system just went off the table.

            Mårten Woxberg added a comment - 13 years and counting. We are looking at changing our ITSM system and Jira was one of the candidates until we found out how Atlassian manages Confluence. All Label Macros work different, some allow AND (Content by label) most allow OR some allow limiting by space others filter on other stuff. It would be preferable if all options where available to all Label Macros.   This one seems like a very easy fix since most other label macros already does this. Jira as an ITSM system just went off the table.

            11 years and this still isn't done? Can someone please re-evauate and get this on the roadmap, It should be a trivial change given how all the other macros can limit by space.

             

             

            Andrew Laden added a comment - 11 years and this still isn't done? Can someone please re-evauate and get this on the roadmap, It should be a trivial change given how all the other macros can limit by space.    

            Nine years? Really? Is anyone minding the store? And don't tell me it hasn't gotten enough votes. If you don't care enough to deal with dead simple obvious no-brainer stuff like this, how can we trust you to fix complex problems?

            Carter Snowden added a comment - Nine years? Really? Is anyone minding the store? And don't tell me it hasn't gotten enough votes. If you don't care enough to deal with dead simple obvious no-brainer stuff like this, how can we trust you to fix complex problems?

            maderskog added a comment -

            This really needs to be fixed, it is a great feature, but without space restrictions it becomes useless, asking users to remember they need to name their labels so that they are space-unique is futile when the number of spaces becomes large.
            Also it seems to be a fairly trivial fix if Tim above is right, so pls show some of that agility here and crank out a fix pretty soon

            maderskog added a comment - This really needs to be fixed, it is a great feature, but without space restrictions it becomes useless, asking users to remember they need to name their labels so that they are space-unique is futile when the number of spaces becomes large. Also it seems to be a fairly trivial fix if Tim above is right, so pls show some of that agility here and crank out a fix pretty soon

            I was sent a link to another feature request that seems more or less the same as this (the # CONF-18258).

            Can you guys merge both so that we aggregate watchers and voters. Thanks

            I'll add my vote.

            Somayya

            somayya el gemei added a comment - I was sent a link to another feature request that seems more or less the same as this (the # CONF-18258 ). Can you guys merge both so that we aggregate watchers and voters. Thanks I'll add my vote. Somayya

            Requested in Aug 2007. Hmmm... nearly two years... Yikes.

            I had a look at the NavigationMapMacro source code and it seems like a fairly trivial modification these days to add a space option (and default to the current space).

            < content = labelManager.getContent(label);
            > content = labelManager.getCurrentContentForLabelAndSpace(label, spaceKey)

            -Tim

            Tim Colson added a comment - Requested in Aug 2007. Hmmm... nearly two years... Yikes. I had a look at the NavigationMapMacro source code and it seems like a fairly trivial modification these days to add a space option (and default to the current space). < content = labelManager.getContent(label); > content = labelManager.getCurrentContentForLabelAndSpace(label, spaceKey) -Tim

            I agree with Geoff .

            This could cause

            1. UX issues: Becuase users dont really expect the output to consist of pages containing the labels in all spaces across Wiki (even the one they dont have any idea about).
            2. There could be a suspected performance impact if users configure it with a label that has thousands of uses across multiple spaces.

            Please do consider to fix this to make it more productable especially for huge Confluence instances.

            Thanks and Regards
            Aditee Pandey

            Cisco IT Wiki Support added a comment - I agree with Geoff . This could cause UX issues : Becuase users dont really expect the output to consist of pages containing the labels in all spaces across Wiki (even the one they dont have any idea about). There could be a suspected performance impact if users configure it with a label that has thousands of uses across multiple spaces. Please do consider to fix this to make it more productable especially for huge Confluence instances. Thanks and Regards Aditee Pandey

            GeoffB added a comment -

            Navmap is a great feature in theory but it is severely limited because it doesn't allow restriction to a specific space. It means its only really good for a navigation construct that spans the entire WIKI and all but useless for trying to use this in the context of a single space. Please add an attribute to the navmap macro to allow restriction by space.

            GeoffB added a comment - Navmap is a great feature in theory but it is severely limited because it doesn't allow restriction to a specific space. It means its only really good for a navigation construct that spans the entire WIKI and all but useless for trying to use this in the context of a single space. Please add an attribute to the navmap macro to allow restriction by space.

            Matt Ryall added a comment -

            Thanks for the suggestion, Andy.

            Matt Ryall added a comment - Thanks for the suggestion, Andy.

              Unassigned Unassigned
              8dcf83952363 Andy Brook
              Votes:
              42 Vote for this issue
              Watchers:
              28 Start watching this issue

                Created:
                Updated: