Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Repair Jira Macros

...

Outer Macro

MacrosStatusTested

Restrictions & Workarounds

Discussion
futurefuture(warning)(tick)

Since 6.4, many scenarios are now covered. The most significant restriction is Future within an Include within a Future macro.

Confluence 5.4.3 or above provides the most scenario coverage.

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-104

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-60

futurecache(tick)(tick)

Since 6.2. Prior to 6.2, Cache refresh link does not work inside a Future macro.

future

table-plus, sql, csv, excel

(tick)(tick)

futurerun, run-now(tick)(tick)

futurecloak(error)(tick)

futuremetadata macros(tick)(tick)
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-83
futurescaffolding macros(tick)(tick)(warning) Does not work in edit contents mode
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-83
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-132
future

report-table, report-variable

(error)(tick)
Jira Legacy
CACHE-146
CACHE-146
futureother reporting macros(tick)(tick)
There is a user report
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-64
futureexpand(tick)(tick)

Requires release 6.1 and at least Confluence 5.0

Note

For Confluence 7.0 and later versions, when you use the future macro embedded with an expand macro multiple times in a page, it does not expand and collapse as expected. This is because of a known issue - CONFSERVER-40562.


Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-74
tocfuture on same page(tick)(tick)
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-59

expand

future(tick)(tick)

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-62

Similar results for other Expand like macros that selectively show data

cloakfuture(tick)(tick)

deck/card

future(tick)(tick)

Requires 6.1.1. Use Future macro for one or more cards. This is the most typical situation.

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-62
,
Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-87

localtabgroup/localtab

future(tick)(tick)Requires 6.4.

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-62

cachefuture(warning)(tick)

It works, but is of little value as Cache captures the rendered body without the rendered data from the Future macro. Each rendering of the page will result in the Future macro getting the data in the background again.

macros requiring web resources

Examples:

  • show-if, hide-if and similar
future(warning)(tick)

(tick) Confluence 4.x - 5.1

(warning) Confluence 5.2 - 5.4.2

(tick) Confluence 5.4.3+ with Cache for Confluence 6.3 or above.

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-63
A workaround is to have the macro requiring resources be on the page outside of the Future macro. Perhaps in a Hide macro with rendering.
Refined Wikifuture

(warning)




Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-69
future

OfficeConnector

  • viewxls
  • viewdoc
  • viewppt
  • viewpdf


  • (tick)
  • (tick)
  • (error)
  • (error)
(tick)

Requires release 6.1

Resolved with Confluence 5.4.3 and above together with Cache for Confluence 6.3 or above.

  • viewppt (tick)
  • viewpdf (tick)

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-78


Note

The Cache macro used with the Office Connector macros has a compatibility issue in Confluence version 7.9.0. Refer and watch 

Jira Legacy
serverSystem JIRA
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-346
 for updates.


futureJIRA macro(tick)(tick)

futurepagetree(warning)(tick)

(tick) Confluence 4.x - 5.1

(tick) Confluence 5.2 - 5.4.2: Requires 6.4

(tick) Confluence 5.4.3 or above: Requires 6.4 and an Atlassian pagetree plugin fix. See Tracked Atlassian issues.

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-92

CONF-33388

futurepage-gadget(warning)(tick)

(tick) Confluence 4.x - 5.1

(tick) Confluence 5.2 or above: Requires Cache for Confluence 6.4 or above

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-92
future

code

code-pro

(tick)(tick)

Fixed in Confluence 5.8.5.

Workaround: Make sure the page has a Code or Code Pro macro outside of a Future macro. This brings in the necessary web resources correctly.

Or install the patched version of the Code macro plugin.

CONF-35014 - provides a fix for the Code macro for future versions of Confluence

newcode-macro-plugin-2.1.5.1.jar - a patched version of the code macro for Confluence 5.3 and above

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63
keyCACHE-114

futureConfluence table sorting(tick)(tick)

Some Confluence release level restrictions.

Workaround: Use Table Plus macro.

CONF-35452

Jira Legacy
CACHE-105
CACHE-105

future

excerpt-include

excerpt

(error)
Avoid putting the Excerpt macro within a Future macro if you need to access the data using excerpt-include.
Jira Legacy
CACHE-183
CACHE-183
chartfuture(error)
The Chart macro excepts all data to be available immediately, so a delayed rendering via Future is not going to work.

...

Issues related to Future macro

Jira Legacy
serverSystem JIRA (bobswift.atlassian.net)
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
jqlQueryproject = CACHE and resolution = null and component = future
serverId729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63