Aldorock apps for Atlassian

Tree Copy for Confluence

Copy a page and everything under it, in order, with label filters, renamed titles, variables, and links that point at the copies.

Getting started

  1. Install Tree Copy for Confluence from the Atlassian Marketplace. It adds Copy this page tree to every page's "…" menu (under Apps) and a Tree Copy tab to every space.
  2. Open the page at the top of the tree you want to copy and choose Copy this page tree. Or open the Tree Copy tab of a space and pick the page there.
  3. Choose the destination: a space and the page the copy goes under. Set a title prefix, suffix or find-and-replace so the copies do not clash with the originals, add variables, and decide what to copy.
  4. Preview the list of pages with their new titles, then Copy. The run shows progress page by page; links in the result open the copies.

What is copied

ThingBehaviour
PagesThe chosen page and all its descendants, parents before children, same order, up to 500 pages and ten levels deep per run. Body content is copied by Confluence's own copy, so macros, tables and layouts survive.
TitlesFind-and-replace first, then variables, then prefix and suffix. Confluence allows one title per space and adds a number such as " (2)" to a copy whose title already exists, so change titles when copying inside the same space; the preview warns you.
LabelsCopied when "Copy labels" is on.
AttachmentsCopied when "Copy attachments" is on, including images embedded in the page.
Links between copied pagesRe-pointed to the copies when "Re-point links" is on: page links and smart cards whose URL names the page id. Links to pages outside the copied tree, or to pages the filters skipped, keep pointing at the originals; so do links inside macro parameters, editor URLs (/wiki/spaces/KEY/pages/edit-v2/…) and tiny links (/wiki/x/…).
Page restrictionsCopied with the pages when "Keep page restrictions" is on (the default). Turn it off to make the copies as open as the destination.
Legacy-editor pagesCopied as they are; variables and links inside them are not changed, and the run lists them.
Permissions, comments, page historyNot copied. The copies are new pages owned by the person who runs the copy.

Label filters

Copy only pages with labels keeps descendants that carry at least one of the labels; Skip pages with labels drops descendants that carry any of them. A skipped page takes its whole subtree with it. The page you start from is always copied. Filters are evaluated as each page is reached, so the preview shows the full tree and the run shows what was skipped and why.

Variables

Write {{customer}} anywhere in a title or in page text and give customer=Acme in the Variables box (one name=value per line). {{name|fallback}} uses the fallback when no value is given. {{today}}, {{today+7}} and {{today-1}} insert ISO dates. Variables found in titles are asked for before the copy starts; variables in page text are replaced when each copy is finalised.

Long trees and failures

The copy runs in short slices and continues automatically while the dialog is open. If Confluence refuses a page (for example when you lack permission under the destination), the run stops at that page and shows the reason. Fix the cause and press Retry from the failed page; nothing already copied is copied again. Runs are kept for 30 days in the space's Tree Copy tab.

Permissions

The app acts as you. You need to be able to view the source pages and to create pages under the destination. What you cannot see is not copied.

Where is the data stored?

Run records (the list of pages, new ids and progress) live in Forge storage inside your Atlassian site's region for 30 days. Page content never leaves Atlassian; the app has no servers of its own. See Privacy.

Changelog