Template Variables Stopped Working

[Nick Mauck]

I have created several templates across multiple spaces that contain variables in list form.  Some are one word, some are a line of text, some have color circled emojis for criticality, etc.  They all just stopped working, the created from template button opens the template but all the variable fields no longer have drop-down menus.  It's just the name of the template like so (name).  Working with my organizations internal Confluence help desk, they are telling me the following, which makes zero sense to me.

"After more testing and talking with Atlassian, it looks like having a space in the title of the variable is most likely the issue.  It can cause issues with the system code for the variable, which is most likely why you then can't just copy the content to another template and instead would have to start fresh.  So, if you create a new template and add variables with o one variables, it should work."

So I guess my question is do variables have to be one word, no spaces, etc?  Are there any constraints on the text/spaces/characters for variables?

[Suketa]

Hello 

On my side it was, the root cause was the logo added (at the creation or after) to the blueprint...

Regards

[KINAY Mizuho[Ricksoft]]

Hi there,

I have similar issue but maybe a bit different.

For me, when the variable is in a expand macro, then the variable doesn't appear when I applied the template.

If the variable is outside of a expand macro, then it works as expected.

[Craig Nodwell]

Hi @Nick Mauck welcome to the community.  I cannot find any documentation that says there can't be spaces in a variable name however .... It is pretty common practice in programming to not include a space in a variable name so maybe it's just a miss on the docs.  I would stay with the common practice of never placing a space in a variable name and avoid any potential problems downstream when you go to use that variable.  I'd stay away from special chars as well and use plain text maybe even adopt all lower case ... that part is up to you but I would also suggest to follow some sort of internal set standard.

[Zack Garner]

@Craig Nodwell ,

To tack onto what @Nick Mauck was saying, specifically a space in the variable name produces no dropdown menu when the create from template macro is used.  Special characters inside of the list selection for a variable within the template creation allow the dropdown menu but none of the selections are rendered for create from template macro.  However, when you perform the action outside of the preview, nothing renders correctly.  A friend of mine found this [CONFSERVER-82493] which was created.  It was created 2 hours ago so it hasn't been looked into further yet.