Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-3324

Support replacement of page template variables in wiki links and macro parameters

    • 2
    • 4
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      When using page templates, variables are not recognized when they are inside of wiki constructs (e.g. [@@],

      {@@}

      ).
      Here is an example of a template page, with variables that work and variables that don't:

      Variables where they do not work:

      inside link page title#@pageLink@
      inside include macro {include:@contentPageName@}

      Variables where they do work:

      inside plain text Some random text @variable@

            [CONFCLOUD-3324] Support replacement of page template variables in wiki links and macro parameters

            Hello everyone,

            We are currently shifting the efforts from templates to additional customization options for Confluence Cloud.

            While we will not be closing this suggestion, this means that we will be pausing the implementation for new features related to templates, but will keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy.

            Thank you for your understanding.

            Wish you the best,
            Giuliano C.
            Atlassian Team

            Giuliano C. added a comment - Hello everyone, We are currently shifting the efforts from templates to additional customization options for Confluence Cloud. While we will not be closing this suggestion, this means that we will be pausing the implementation for new features related to templates, but will keep the maintenance and continue to fix bugs that have higher priorities as per our Bug Fixing Policy . Thank you for your understanding. Wish you the best, Giuliano C. Atlassian Team

            Hi all! My name’s Avni and I’m the Product Manager that works on the template feature. Thanks a lot for your feedback. As we’re continuing to improve templates, understanding use cases like these always helps us figure out the most important items to prioritize in our roadmap. 

            For this specific request, we don’t currently have short-term plans but are actively investigating what we could do. We’ll keep this ticket updated as we know more.

            Thanks again for your feedback!

            Cheers,
            Avni Barman | Atlassian Product Manager

            Avni Barman (Inactive) added a comment - Hi all! My name’s Avni and I’m the Product Manager that works on the template feature. Thanks a lot for your feedback. As we’re continuing to improve templates, understanding use cases like these always helps us figure out the most important items to prioritize in our roadmap.  For this specific request, we don’t currently have short-term plans but are actively investigating what we could do. We’ll keep this ticket updated as we know more. Thanks again for your feedback! Cheers, Avni Barman | Atlassian Product Manager

            srisreeni added a comment -

            Under consideration, we will review and slot into our roadmap in future

            srisreeni added a comment - Under consideration, we will review and slot into our roadmap in future

            Also very disappointed in this missing feature.

             

            @Kim Poulsen I'd love to give your user macro a try, yet we use Confluence Cloud, so we do not have access to the user macros functionality 😭

            Carl DiClementi added a comment - Also very disappointed in this missing feature.   @Kim Poulsen I'd love to give your user macro a try, yet we use Confluence Cloud, so we do not have access to the user macros functionality 😭

            With our Page Tree Creator you can use tags (variables) in the page title, on the page and also in macro parameters.
            Give it a try: Page Tree Creator Marketplace link
            or try our Live Examples

            EPS Software Engineering AG added a comment - With our Page Tree Creator you can use tags (variables) in the page title, on the page and also in macro parameters. Give it a try: Page Tree Creator Marketplace link or try our Live Examples

            I'm wanting the ability to use this in external links, also. For instance, if an external system's record ID is entered as a variable we would want to populate several links to that external system with this value. (e.g. example.com/logo/$ExtId, example.com/contacts/$ExtId, google.com/search?q=$ExtId, etc.)

            Dakota Duff added a comment - I'm wanting the ability to use this in external links, also. For instance, if an external system's record ID is entered as a variable we would want to populate several links to that external system with this value. (e.g. example.com/logo/$ExtId, example.com/contacts/$ExtId, google.com/search?q=$ExtId, etc.)

            The fact that this is considered a suggestion rather than a basic feature baffles me as well. I went through the process of creating a template that used some JIRA chart macros, and originally I thought I must have the syntax wrong when I referenced a template variable to represent my JIRA project. It really surprised and disappointed me that I wasted a lot of time setting up the template only to realize that I will have to individually modify the same value in 6 different places within my page (in the macro code) to represent the JIRA project EVERY time. Yuck. With literally hundreds of projects, I thought it would be a nobrainer to set up a template that every team could easily use. Very disappointed.

            Carrie Aversa added a comment - The fact that this is considered a suggestion rather than a basic feature baffles me as well. I went through the process of creating a template that used some JIRA chart macros, and originally I thought I must have the syntax wrong when I referenced a template variable to represent my JIRA project. It really surprised and disappointed me that I wasted a lot of time setting up the template only to realize that I will have to individually modify the same value in 6 different places within my page (in the macro code) to represent the JIRA project EVERY time. Yuck. With literally hundreds of projects, I thought it would be a nobrainer to set up a template that every team could easily use. Very disappointed.

            I have attempted a workaround in a user macro. I have posted it here: https://answers.atlassian.com/questions/141785/answers/30948374
            It is not ideal in the sense that JIRA macros rendered in a user macro $body does not work alongside with sectioned layouts.
            But it may have it's purposes anyhow.

            Kim Poulsen added a comment - I have attempted a workaround in a user macro. I have posted it here: https://answers.atlassian.com/questions/141785/answers/30948374 It is not ideal in the sense that JIRA macros rendered in a user macro $body does not work alongside with sectioned layouts. But it may have it's purposes anyhow.

            This seems like a very basic feature.

            Jake Gibson added a comment - This seems like a very basic feature.

            Jens,

            I'm not sure it is an improvement, it is more a feature lost.

            I have created several page templates for which the page creator was invited to set the JIRA project KEY in a variable and it was automatically injecting this value in JIRA filter gadgets and creating a link to project repository.
            And the user was able to rework on the called gadget at the page template level and at the page level too.

            Today the mitigation to obtain the same behaviour is to develop a Blueprint, and not entirely because the user won't be able to modify the filter at the blueprint level. For the end users it is hard to swallow.

            Best Regards, hope we will soon have back the capability to inject $variable inside macros.

            Cyrille Martin added a comment - Jens, I'm not sure it is an improvement, it is more a feature lost. I have created several page templates for which the page creator was invited to set the JIRA project KEY in a variable and it was automatically injecting this value in JIRA filter gadgets and creating a link to project repository. And the user was able to rework on the called gadget at the page template level and at the page level too. Today the mitigation to obtain the same behaviour is to develop a Blueprint, and not entirely because the user won't be able to modify the filter at the blueprint level. For the end users it is hard to swallow. Best Regards, hope we will soon have back the capability to inject $variable inside macros.

              Unassigned Unassigned
              jens@atlassian.com jens
              Votes:
              225 Vote for this issue
              Watchers:
              136 Start watching this issue

                Created:
                Updated: