We have a team that has created a "Global Template". This template lives in a "Global Space" In this template we are attempting to utilize the Page Tree macro. The expectation is that this template will be used across various teams which work in their own spaces. Within the template the page tree macro has a reference to @parent which should display the name of all of the pages within that same umbrella of pages that the template gets moved to.
The problem is that once the template page has been generated, and the team member moves the page to their own space, the Page Tree macro is replacing "@parent" with "GLB:@parent" which is referencing the global space that the page was pulled from. The fix is as simple as the user needs to go into the macro once it has been moved, and simply remove the "GLB:" portion, and the page tree will begin working again. But my question is there a way to "lock" the field so that it will reference whatever parent it has, no matter which space? I would like to setup this template to be able to move across teams and update dynamically.
Feeling overwhelmed by the demands of work and life? With a 25% increase in the prevalence of anxiety and depression worldwide during the pandemic, for most of us, it’s a resounding yes . 🙋♀️ ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events