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

Not possible to populate variables on the new editor

XMLWordPrintable

      Issue Summary

      When creating a page using a template with variables on the new editor, it won't be possible to populate the variables.

      Environment

      • New editor

      Steps to Reproduce

      1. On an instance with the new editor enabled, create a new template
      2. Create a variable on the template and save the template
      3. Create a new page using this template

      Expected Results

      It should be possible for the user to populate the variable

      Actual Results

      The variable is not shown, and no "wizard" is shown before editing the page to populate the variables

      Workaround

      No known workaround at the moment.

            [CONFCLOUD-65790] Not possible to populate variables on the new editor

            Battlebeard (Inactive) made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 457735 ]
            Aaron Shapiro made changes -
            Comment [ It seems like variables are broken in all kinds of ways on the new editor. For example, I type $ and nothing happens. There is no way for me to get a list of the new variables I have created, no way for me to reference them either I guess. This is very concerning as my company just decided to migrate us over to a Confluence / Jira stack in the cloud and now we can't do anything we need to do because it seems like all of the advanced functionality that makes the Confluence / Jira stack so valuable doesn't work in the cloud! The key thing I'm trying to do is create new epics when I create a new requirement page with specific values that we need. I also need to create issues under that epic when I create user stories on the requirements page. Since variables don't work, I can't pass anything into the Jira Issue Macro to do any of this. I'm searching Atlassian / Confluence documentation, it all seems outdated and references the old editor. Then I'm searching google for "confluence Jira variables cloud version" and I'm seeing all kinds if open tickets just like this one for all the different ways variables are broken. I also see that the severity is MINOR and that priority on other tickets is LOW. FOR REAL? LOW PRIORITY ON BROKEN VARIABLES for the CLOUD VERSION? That's how you treat your SaaS customers? This software is industry standard? I was originally excited to do this migration because I'm sick of Sharepoint and word documents and I've been pressing for this move for years and now we make the move and we can't get the cloud version to do what we need. Your product owner should be fired.  ]
            Sunny Xu (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            Sunny Xu (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-67823 [ CONFCLOUD-67823 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 45 New: 46
            Bugfix Automation Bot made changes -
            Support reference count Original: 44 New: 45
            Bugfix Automation Bot made changes -
            Support reference count Original: 43 New: 44
            Bugfix Automation Bot made changes -
            Support reference count Original: 42 New: 43
            Bugfix Automation Bot made changes -
            Support reference count Original: 41 New: 42
            ro🐝n made changes -
            Status Original: In Review [ 10051 ] New: Waiting for Release [ 12075 ]

              rbandzar ro🐝n
              gtworkowski Guilherme T (Inactive)
              Affected customers:
              23 This affects my team
              Watchers:
              61 Start watching this issue

                Created:
                Updated:
                Resolved: