Summary
The future Future macro works fine well with many macros, however, there are numerous cases where the interactions of the future macro Future macro with other macros will does not produce the desired expected result. The background rendering of the content can prevent more advanced macros from behaving as expected. Similarly, some advanced macros can interfere with the communications needed by the future Future macro to display the content that is rendered in the background. Fixes have been provided for some of the most prevalent use cases and more will can be considered in the future based on user need. Even though there are a number of interoperability issues, the benefits for some of the most common scenarios warranted delivery. Plus interoperability is significantly better than the old future plugin provided.
This page is intended to document interoperability with other advanced macros. In some cases, there are restrictions or work-arounds for using the macros together. In other case, improvements are needed in the implementations to work better together. Feedback from users with experience with other macros not listed here will help everyone to be able to use the support more effectively. Please vote and open new issues if necessary.
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 is Future within an Include within a |
future macro Future macro. Confluence 5.4.3 or above provides the most scenario coverage. | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | cache | | |
| Since 6.2. Prior to 6.2, |
cache Cache refresh link does not work inside |
a future macro (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | scaffolding macros | | | Does not work in edit contents mode | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | expand | | | 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. |
| |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| toc | future on same page | | |
| |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
expand | future | | |
| |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcdSimilar results for other |
expandExpand like macros that selectively show data |
| cloak | future | | |
|
|
deck/card | future | | | Requires 6.1.1. Use |
future macro Future macro for one or more cards. This is the most typical situation. | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
localtabgroup/localtab | future | | | Requires 6.4. | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| cache | future | | |
| It works, but is of little value as |
cache will capture Cache captures the rendered body without the rendered data from the |
future macro Future macro. Each rendering of the page will result in the |
future macro 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 for Confluence 6.3 or above. | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd A workaround is to have the macro requiring resources |
to be on the page outside of the |
future macro Future macro. Perhaps in a Hide macro with rendering. |
| Refined Wiki | future |
|
|
| |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | OfficeConnector - viewxls
- viewdoc
- viewppt
- viewpdf
|
| | Requires release 6.1 Resolved with Confluence 5.4.3 and above together |
with with Cache for Confluence 6.3 or above. - viewppt
- viewpdf
| |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd
| 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 |
|---|
| server | System JIRA |
|---|
| serverId | 8382ec9d-abb6-3a29-8d72-95b9a5732a63 |
|---|
| key | CACHE-346 |
|---|
|
for updates. |
|
| 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. | |
(bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | code code-pro | | | Fixed in Confluence 5.8.5. Workaround: Make sure the page has a |
code or code-pro future Future macro. This brings in the necessary web resources correctly. Or install the patched version of the |
code will provide code (bobswift.atlassian.net) | | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId |
|---|
|
|
729d679a302c339f958b015e107badcd |
| future | Confluence table sorting | | | Some Confluence release level restrictions. Workaround: Use Table Plus |
Macromacro. | |
| future | excerpt-include excerpt |  |
| Avoid putting the |
excerpt future macro | Future macro if you need to access the data using excerpt-include. | |
| chart | future | |
| The |
chart | Chart macro excepts all data to be available immediately, so a delayed rendering via |
future is | Future is not going to work. |
|
| Legend | Status |
|---|
| Works |
| Works with some restrictions or workarounds |
| Does not work in most cases |
 | Unknown |
Issues
...
related to Future macro
| Jira Legacy |
|---|
| server | System JIRA (bobswift.atlassian.net) |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| jqlQuery | project = CACHE and resolution = null and component = future |
|---|
| serverId | 729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63 |
|---|
|