Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-2789

Ability for Pages to have multiple Parents

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • 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.

      It would be kinda nice for a page to have multiple parents.
      I havent thought much about what complications this would introduce (other than what to show in breadcrumbs).

      But if you are using Hierachy as categorisation - sometimes the one page fits into two categories... (maybe more)..

      Maybe there is a better way of solving this other than via parenting..

          Form Name

            [CONFSERVER-2789] Ability for Pages to have multiple Parents

            Charles Miller (Inactive) added a comment -

            Giving pages multiple parents would be pretty confusing, and we're unlikely to implement it.

            It makes more sense to stick with a simple tree structure, and rely on categories/labels to handle more complex categorisation.

            Charles Miller (Inactive) added a comment - Giving pages multiple parents would be pretty confusing, and we're unlikely to implement it. It makes more sense to stick with a simple tree structure, and rely on categories/labels to handle more complex categorisation.

            Caesar Wong added a comment -

            In JSPWiki, there is an "alias" and "redirect" function, which I believe could be created as a macro in Confluence? eg.

            {redirect=space:page} {alias=space:page}

            The alias method is pretty much the same as the

            {include} method described above, so I guess it is OK not to have that, but the redirect option will also allow the flexibility of not having to actually do the lookup for an {include}

            , and hence use up less resources, without losing any of the benefits required (ie. that it is recognised in the hierarchy as a separate page.

            The only difficulty is in how to edit the page that redirects, since as soon as you load it, it will redirect

            Caesar Wong added a comment - In JSPWiki, there is an "alias" and "redirect" function, which I believe could be created as a macro in Confluence? eg. {redirect=space:page} {alias=space:page} The alias method is pretty much the same as the {include} method described above, so I guess it is OK not to have that, but the redirect option will also allow the flexibility of not having to actually do the lookup for an {include} , and hence use up less resources, without losing any of the benefits required (ie. that it is recognised in the hierarchy as a separate page. The only difficulty is in how to edit the page that redirects, since as soon as you load it, it will redirect

            Nick Faiz [OLD] (Inactive) added a comment -

            Yes, the common content would be put into a separate page. It could then be included by different pages, each in a different hierarchy - composition working with inheritance, if you like.

            Nick Faiz [OLD] (Inactive) added a comment - Yes, the common content would be put into a separate page. It could then be included by different pages, each in a different hierarchy - composition working with inheritance, if you like.

            Nick Minutello added a comment -

            Do you mean have a different page and use

            {include}

            ?

            Nick Minutello added a comment - Do you mean have a different page and use {include} ?

            Nick Faiz [OLD] (Inactive) added a comment -

            Hi Nick,
            I guess the include page is a bit of a workaround for this one - although it doesn't place the included page in the Breadcrumbs.

            e.g.

            {include:Release Notes 1.3.4}

            Nick Faiz [OLD] (Inactive) added a comment - Hi Nick, I guess the include page is a bit of a workaround for this one - although it doesn't place the included page in the Breadcrumbs. e.g. {include:Release Notes 1.3.4}

              Unassigned Unassigned
              3b1ae0ec93c9 Nick Minutello
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: