Outer Macro | Macros | Status | Tested | Restrictions & Workarounds | Discussion |
---|
future | future | | | Since 6.4, many scenarios are now covered. The most significant restriction future within an include within a future macro. Confluence 5.4.3 or above provides the most scenario coverage. | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-104 |
---|
|
Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-60 |
---|
|
|
future | cache | | | | Since 6.2. Prior to 6.2, cache refresh link does not work inside a future macro. |
future | table-plus, sql, csv, excel | | | | |
future | run, run-now | | | | |
future | cloak | | | | |
future | metadata macros | | | | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-83 |
---|
|
|
future | scaffolding macros | | | | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-83 |
---|
|
|
future | reporting macros | | | | There is a user report Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-64 |
---|
|
|
future | expand | | | Requires release 6.1 and at least Confluence 5.0 | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-74 |
---|
|
|
toc | future on same page | | | | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-59 |
---|
|
|
expand | future | | | | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-62 |
---|
|
Similar results for other expand like macros that selectively show data |
cloak | future | | | | |
deck/card | future | | | Requires 6.1.1. Use future macro for one or more cards. This is the most typical situation. | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-62 |
---|
| , Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-87 |
---|
|
|
localtabgroup/localtab | future | | | Requires 6.4. | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-62 |
---|
|
|
cache | future | | | | It works, but is of little value as cache will capture 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 | | | Confluence 4.x - 5.1 Confluence 5.2 - 5.4.2 Confluence 5.4.3+ with Cache 6.3 or above. | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-63 |
---|
| A workaround is to have the macro requiring resources to be on the page outside of the future macro. Perhaps in a Hide macro with rendering. |
Refined Wiki | future | | | | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-69 |
---|
|
|
future | OfficeConnector - viewxls
- viewdoc
- viewppt
- viewpdf
| | | Requires release 6.1 Resolved with Confluence 5.4.3 and above together with Cache 6.3 or above. - viewppt
- viewpdf
| Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-78 |
---|
|
|
future | JIRA macro | | | | |
future | pagetree | | | Confluence 4.x - 5.1 Confluence 5.2 - 5.4.2: Requires 6.4 Confluence 5.4.3 or above: Requires 6.4 and an Atlassian pagetree plugin fix. See Tracked Atlassian issues. | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-92 |
---|
|
CONF-33388 |
future | page-gadget | | | Confluence 4.x - 5.1 Confluence 5.2 or above: Requires Cache 6.4 or above | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-92 |
---|
|
|
future | code code-pro | | | 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 - will provide 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 |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-114 |
---|
|
|
future | Confluence table sorting | | | Workaround: Use Table Plus Macro. | CONF-35452 |
future | Scaffolding | | | Does not work in edit contents mode | Jira Legacy |
---|
server | JIRA (bobswift.atlassian.net) |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 729d679a-302c-339f-958b-015e107badcd |
---|
key | CACHE-132 |
---|
|
|