We created our templates using the old editor. The only thing I don't like with the current fix is that the page to fill the variables does not show instructional text fields.

We use this text to tell what to put into the variables. The great thing about these instructional text fields is that they are not shown into the final document, which makes sure that documentation only useful while editing is not polluting the final text.

Guilherme, variables in the new editor are still broken.
Here's my assessment of the patch that was implemented recently:

1. Old editor variables are fixed now. You can fill out the variables, you can copy and paste the variables, and reference the same variable multiple times.
2. New editor variables can be filled out now, but they are still broken because you can't save the template again after the first save. This is the error I'm seeing:

Replication Method #1

1. Create a new template.
2. Create a new variable, then add another instance of that same variable somewhere else in the template.
3. Save the template.
4. Edit that template.
5. Make no changes, then click "Save", and it will give you an error: "Can't save changes, Multiple template variables which have the same name "var1" but different parameters"
6. It somehow allows you to save initially, but if you ever go back to edit you cannot save, even though nothing has changed.

Replication Method #2

1. These steps require using two different methods of creating multiple instances of a variable.
2. If you copy a variable from the template, then delete everything on the template page, then paste the variable multiple times, it will let you save. but if you paste that variable, then use the macro menu and add the New Variable macro with the same name, it won't let you save.
3. Alternatively, if you start with a clean template and you use the macro menu to create a variable, you can use that method infinitely for the same variable name, and it would allow you to save. but if you add a new variable from the macro menu, then copy paste that macro anywhere, it won't let you save.
4. The error is the same regardless of how you replicate.

The purpose of a variable is to set the data once, and be able reference that data multiple times in the future. It seems that in the new editor variables were programmed without that concept in mind.

The old editor presented a table of all variables for population as a step before dropping into editing the page.  The new fix does not do this, it simply drops into the editor with inline fields.  With long and complex templates, this requires the user to hunt for variable fields to populate. Is this a deliberate change of behaviour, as it makes the templates less usable than they were before?

Cheers

Mark

Hey there,

Robin, from the development team has been working on this case and the definitive fix is now released to the Cloud environment.

Before we close this report, we wold like to confirm if everything is working as expect now!
Could you please clear the browser's cache and check if you're now able to create pages with variables on the new editor?

We'll be looking forward to hearing back from you with the results.

Kind regards,
Guilherme Tworkowski | Atlassian Support

Hello luca2056682004,

The issue with the page properties is known and I opened a public ticket so that progress can be tracked here https://jira.atlassian.com/browse/CONFCLOUD-67823 . ( A possible workaround is to have a variable that shares the same name outside of that macro because then it will use the value inputted across the entire document.)

With regards to the dropdown panel, I appended it as an additional issue in the above ticket as it's a small fix.

If there are any more specific issues, please post them on the new ticket as I want to keep the scope of this one to whether an instance has the wizard.

Hi @Robin,

we just figured out one more bug regarding the "drop-down-list variable":

The width of the button as well as the dropdown-panel is always determined by the option which is currently chosen. If you have very long and very short options, and you chose a short option, the panel will cut off the other, longer options and make them unreadable.

Kindly, Luca

Hi @Robin,

I just figured out, that the variables are not working inside an "Page properties" macro. Once the variable is inside the "page properties" macro, it is broken and only displays "inlineExtension" instead of the variable-options.

Kindly, Luca

Hi @Robin,

I see that something changed, but it is still not working for me.

First I tested it with my existing templates which include variables, not working. Then I created a new, fresh template, assuming it might work if I use the new page style. But still not working!

Once I create a page from the template, it brings me to the page wizard and telling me to fill in the variables. But the variables are not displayed as they should look like. Instead it only says "inlineExtension" in every place a variable is supposed to be.

Please fix the problem.

Kind regards,

Luca

Hi all,

The ability to input variable values for user created templates should be re-enabled for all instances.

If there still are any issues please don't hesitate to follow up.

Thanks again for your patience,

Robin

Hi all, 

I changed the status as there is a fix awaiting release.

59a6bb4911c4 the fix only addresses the issue mentioned specifically in the ticket where there is no wizard to input values when creating a page from a user created template that contains variables. 

I did not get a chance to test the fix before it was rolled back. Can you advise if the fix will include the following features that were present in the old editor, or just the pre-edit form, as only the first is currently available and this issue appears to only address the last in the list?

• Add a new variable from the Insert menu
• Add a new variable using the / notation
• Insert an existing variable in template editing using markup $variablename so the variable can be referenced more than once in a document
• Add variable values using a pre-edit form requesting input of variable values

Hello,

A follow up update, the fix has been temporarily turned off to investigate another issue that this may have introduced. 

I keep this issue up to date on the progress.

Regards,

Robin

Hi all,

Here with an update, the ability to input variable values for user created templates should be enabled for all instances.

If there still are any issues please don't hesitate to follow up.

Your patience is highly appreciated,

Robin

Hi @Robin Bandzar

Please provide some sort of update to this issue.  This is impacting us pretty heavily at this point in time, I'm sure with everyone else that uses templates as well.

This issue is apparently affecting my team as well.  None of us realized it a few weeks ago, but when we tried to use one of our templates today, I decided to dig deeper and found this Jira ticket on the issue.

What is the latest ?  When will this be fixed ?  Why isn't there a workaround?  We should be able to transition back to the old editor shouldn't we ?

I still show the issue today (8/13/2019) @ 8:27 ET.Any update?

Any updates?  We're experiencing this issue as well and it's impacting our business process.  

Hi @Robin B.,

as it seems to take longer for you to fix it, I do have a request for you:

In one of our cloud versions ("mattes-wiki") we can still use the old page editing mode, in two of the newer instances we can't (these are "byght" and "ubdg") since they only offer us the new page editing mode. They have this difference although they show us the same confluence version.

As I said, these two ("byght" and "ubdg") are not usable for us right now! Is it possible to activate the old editing mode for us?

Luca

Hi luca2056682004,

Yes you are correct it is still under technical review, I am very sorry for the delay.

The developers that I have as reviewers are juggling many things and I am not exactly the fastest person, so the back and forth timeframe between feedback and me addressing the feedback is a bit longer than it should be.

When it does start rolling out for instances I will try reaching out to you personally to make sure you are part of the group that gets it first.

Sorry again,

Robin

Hi @Robin B.,

do you have a new update for us? It still seems to be under technical review?!

This is very important for us, as we can't use our two of our three cloud-instances at all right now. All the important templates in our imported space are not working any more.

Regards, Luca

Hi all,

Sorry for the late update, it is still under technical review.

On Monday the changes hopefully will be in our codebase for QA review.

And then following that, if all goes well, instances should start receiving the changes.

Thanks again for your patience.

Regards,

Robin

Are there any updates on this issue?

Hi all,

Here with an update, the code changes are put up for review. 

Also, I would like to apologize for not meeting the estimate that I had originally set out.

I hope that you can understand that I was trying my best and just very eager.

The next update will be when the changes start being available to users.

Hi flavio.meyer1, first the changes would have to be reviewed by other fellow developers. That's when I would mark the ticket to be in 'Review'. Afterwards, it would be on our internal instances where we use our own products for some time as an extra measure of defense.

The time frame can be affected by a variety of external factors as well.

Given all of that, I want to give an estimate of end of next week to mark the start of rolling out the ability to input values for variables.

In the scenario that I was too optimistic I will also provide an update explaining that.

Thanks again for your patience.

Hello Robin

First of all, thanks for your update

I am pleased to hear that an Atlassian developer has found time to fix the bug that was reported last December.

Do you know how long it would take to bring the fix from internal system to the production? 

Hi all, Appreciate everyone's patience on this issue. I am currently working on it and hope to have the fix ready for internal testing this week.

Will give an update once the fix is ready for production.

Hello all, 

I figured out that if you create your own Blueprint/Template and add a variable, they work. This issue seems to only affect the "out of box" blueprints. 

This is holding my company back from creating documentation, any idea when this will be fixed?

Hello there. Can someone please provide an update on this issue?