Deprecating infrequently used macros in Confluence Cloud

[David Michelson]

@Ken Poulton These macros will be unaffected on Confluence Data Center.

[Aidan P_]

I'd like to mimic earlier comments about the Gallery macro depreciation.

Our support team includes a field team that utilizes the Confluence Cloud mobile app.

Databases are currently not available on the Confluence Cloud mobile app. 

The Gallery macro allows for our field techs to quickly view images related to their work. Removing this feature will cause extreme bottlenecks in our workflows.

The amount of cleanup required to mitigate the removal of the Gallery macro will be extremely cumbersome to the point where it would make more sense to onboard onto another tool. 

:-(

[UL]

So the Gallery macro isn't frequently used? We do! 

I don't understand Atlassian's move to depreceate such a basic macro. 
Attaching pictures to a page to show up in a kind of organizable way is a very normal use case, isn't it?

We document RMA cases as single Confluence pages based on a template and generate necessary reports from it ... with pictures.

1. User A sets up the page, attaches the pictures we got from the customer - labeled cust.
2. User B documents analysis findings and attaches pictures made - labeled rma. 
3. User C writes a Failure Analysis Report on that very same page and selects from the attached pictures the ones to show up in the pdf - by labeling these far.
4. User C or D has to do a full 8D-Report - with possibly another selection of pictures here by labeling those 8d.
   
   Pretty simple workflow, making use of Confluence's basic functions like templates, attachements, labels and the gallery macro as well as more sophisticated apps like Scroll PDF.

Again, I'm stunned by the move to depreceate such a basic macro which seems to be a natural link between page and attachments!

[satur]

Hi David

Regarding the deprecation of the Contributors Summary macro, you say "Use the Contributors macro. Note that you will not be able to get the same exact information with the Contributors macro."

I tried switching to the Contributors macro and it gives similar information, but in a poor format. In fact, the information displayed is rather objectively better (tabular format) with the soon-to-be-deprecated Contributors Summary macro than it is with the Contributors macro. What gives? Am I missing something?

[Roger Fedor]

This would affect us because we use Related Labels to build a landing page for our Knowledge Base to display labels under it like a Table of Contents.  The landing page shows a list of what articles were newly created, which ones were recently updated, and a few lists of articles from more commonly accessed labels for quick access. Without this we can't show users a complete list of categories and makes navigating it less effective.  It would be great if this functionality could be preserved by adding a filter for Label List to retain this functionality.

[Christiane K_]

Welcome to another DOWNGRADING of Confluence.

Gallery was a very useful tool to collect all screenshots for a User Manual on one single place. Once upon a time, these images could be linked to and so it was a very good tool to only upload images once and share that image on all needed places.

So again, this will be replaced by a overthaught useless, ignorant to user's need and difficult to handle tool .

Why keep things simple when someone can develop something much more complicate and useless?

[Philippe PEREZ]

Hello Atlassian.
We have to tell we are very disappointed by this : 

Powerpoint, Excel, and Word macros

Upload the file directly to Confluence content or paste a OneDrive smart link to embed files in Confluence.

Uploading the file is NOT the equivalent of the macros that today display XLS as a spreadsheet and PPT as a slideshow.
Instead they will both be displayed as a PDF, with random cropping of large sheets (for XLS) and never-ending scrolling (for PPT with dozens of slides).

That was one of our first concern when we started to migrate to Cloud more than 3 years ago, and at the time we managed to have product owners agreed with us and re-develop first a "spread-sheet" like display of XLS, then later on a "Slideshow" preview for PPT.

And you are telling me that now that we ended our 2 years long migration to the Cloud, you are going to undo what you spent weeks to develop ?

What will happen to the thousands of existing page using the viewls and viewppt macro today ?

[Philippe PEREZ]

"Existing instances of these macros will be replaced with a message that indicates the macro is no longer available with a link to deprecation documentation."

Atlassian: this is totally UNACCEPTABLE !

You can't corrupt thousands of pages like that. 
People already spent hours to adapt the content to the Cloud after we migrated from Datacenter.

They  are going to spend again hours because of the deprecation of legacy editor (by the end of the Year, for those who are not aware !)

You can't expect that customers waste time every quarter to adapt to whatever cut you have decided to do in your code.

Philippe.

[David Michelson]

Hi all,

Thank you so much for your continued feedback. 

We've come to the decision that there is not a suitable alternative for the Excel macro in Cloud, especially for many Data Center customers that want to migrate and are not yet using OneDrive. So, we will no longer be deprecating that macro. You should no longer see "Deprecated" messaging in-product within the next few days.

We are continuing to monitor feedback around the Gallery macro, and appreciate each and every comment!

Cheers,

David
Confluence Cloud Product Manager

[Philippe PEREZ]

Thank you David !

[Ken Poulton]

Save the Gallery!

[Chihara Naruhito]

@David Michelson 

Only Excel macro?

What happen to ppt/word/pdf macro ?

[satur]

Hi

I noticed that the Contributors Summary macro is being deprecated in September 2025 in favor of the Contributors macro. However, the Contributors macro displays the same information as the summary macro, but in a worse format (unlike the tabular display of the summary macro). What's the rationale? Is there some other macro that I'm missing? I find the Contributors metric to be useful to measure the team's contribution to documentation. I appreciate that it's not all about quantity and I have other tools to enforce quality.