Future Macro - Interoperability
Summary
The future macro works fine with many macros, however, there are numerous cases where the interactions of the future macro with other macros will not produce the desired 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 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 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 will help everyone to be able to use the support more effectively. Please vote and open new issues if necessary.
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. | CACHE-104 - Getting issue details... STATUS CACHE-60 - Getting issue details... STATUS |
| 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 | | | CACHE-83 - Getting issue details... STATUS | |
| future | scaffolding macros | | | Does not work in edit contents mode | CACHE-83 - Getting issue details... STATUS CACHE-132 - Getting issue details... STATUS |
| future | report-table, report-variable | | | CACHE-146 - Getting issue details... STATUS | |
| future | other reporting macros | | | There is a user report CACHE-64 - Getting issue details... STATUS | |
| future | expand | | | Requires release 6.1 and at least Confluence 5.0 | CACHE-74 - Getting issue details... STATUS |
| toc | future on same page | | | CACHE-59 - Getting issue details... STATUS | |
expand | future | | | CACHE-62 - Getting issue details... STATUS 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. | CACHE-62 - Getting issue details... STATUS , CACHE-87 - Getting issue details... STATUS |
localtabgroup/localtab | future | | | Requires 6.4. | CACHE-62 - Getting issue details... STATUS |
| 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:
| future | | |
| CACHE-63 - Getting issue details... STATUS 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 |
| CACHE-69 - Getting issue details... STATUS | ||
| future | OfficeConnector
| | Requires release 6.1 Resolved with Confluence 5.4.3 and above together with Cache 6.3 or above.
| CACHE-78 - Getting issue details... STATUS | |
| future | JIRA macro |
|
| CACHE-298 - Getting issue details... STATUS - We see that the results are not being loaded when Jira macro is used within future macro. Tested confluence version: 6.12.2 and add-on version: 7.9.0 | |
| future | pagetree | | |
| CACHE-92 - Getting issue details... STATUS |
| future | page-gadget | | |
| CACHE-92 - Getting issue details... STATUS |
| future | code | | | 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 - 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 CACHE-114 - Getting issue details... STATUS |
| future | Confluence table sorting | | | Some Confluence release level restrictions. Workaround: Use Table Plus Macro. | CACHE-105 - Getting issue details... STATUS |
| future | excerpt-include excerpt | | Avoid putting the excerpt macro within a future macro if you need to access the data using excerpt-include. | CACHE-183 - Getting issue details... STATUS | |
| chart | future | | The chart macro excepts all data to be available immediately, so a delayed rendering via 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
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.