Does anyone know if this new template works with the

plugin?

I want much more flexibility in defining variables in my templates I am very frustrated with the limited usability of variables as they exist today. Simple things like default values intended to provide context to the users of the template are grossly lacking.

Additionally, why do I still need to know wiki markup when entering information into JIRA? It too should have a rich editor for both issue creation and comments. After all, if you are removing the need for people to know the wiki markup syntax everywhere else, and even removing the ability for them to inspect the markup and fix annoying things like the extra spacing that is sometimes generated through the use of your rich editor, a personal pet peeve, then you should at least be consistent across your family of products.

I originally posted the rest of this comment at https://confluence.atlassian.com/display/DOC/Form+Field+Markup+for+Templates

Why on earth are we so limited in the ability to specify default values (or options) for a template variable. No white space between the AT signs...really? Additionally it seems that many people would like the ability to enter a value for a template variable without it being inserted into the page but then be able to use that variable later. Below are a few examples of how this could be accommodated with what seems like relative ease:

// e-mail address with link
|| Contact | [mailto:@contact|list({cdata}address1@domain.com{cdata},{cdata}address2@domain.com{cdata})@] ||

// prompt user for variable but don't insert until later
@var|prompt({cdata}Some important data:{cdata})@

Perhaps we wanted to use the variable to create a link somewhere else such as [right here|@var@]. Or perhaps the variable is just going to be used, @var@, multiple times in the document and the template author wanted to gather all of the values for template variables early on.

// textarea with default value
h1. Overview
@overview|textarea(15,200)|default({cdata}This section should contain an overview of the proposed feature{cdata})@

While I don't really like the idea of having to use a cdata macro it does provide for a clean way of allowing spaces inside of a given area where you might not generally allow spaces.

Fantastic Matt, thanks for the update

I'm unsure who told you that rich text editing for creating and editing templates was being pushed from 4.3 because it is in 4.3 You can try it today in the Confluence 4.3 Beta 1 release.

At the bottom of the link Sandro included, it says that this feature has now been pushed from 4.3 to 4.4

http://www.communardo.de/home/techblog/2012/06/27/wikipage-to-page-template-since-confluence-4/

"A representative from Atlassian told me on a User Group Munich Meeting a week ago that Rich Text Editor editing of page templates was postponed from version 4.3 to version 4.4 of Confluence, so it may take another year"

We haven't had an official update on this issue in over 3 months. Please provide an official update on this issue - when will we see this resolved?

This issue is causing serious headaches at our company. We have held off upgrading to Confluence 4.x because of this, but it has been a contentious issue.

There is a little workarround for the Confluence 4 page template problem:
http://www.communardo.de/home/techblog/2012/06/27/wikipage-to-page-template-since-confluence-4/

Until this feature arrives: what is the markup/macro code to use the new (like based) popular content feature introduced with 4.2.5?

I would like to use it in a custom dashboard (via $helper.renderConfluenceMacro("

") but cannot do so due to this information missing from the documentation).

My idea of improvements that Confluence 4.3 must have:

1. Create template from existing page / Update template from existing page
2. Create template using the new Rich Text Editor
3. Copy XHTML source format from page and import XHTML source format into space template

Hopefully the release of version 4.3 will be very soon with a good solution.

As of the status of this issue, is there already a fix, is it in progress or resolved??? This issue is still open, but it will be in release 4.3..? So whats up?

atreadway it will be available in the first beta release.

I'll report for the record that this isn't in the EAP.