Confluence pages with too many Jira issue macros

This insight checks whether any of your pages exceed the recommended number of Jira issue macros.

Too many Jira issue macros can affect performance of a particular page, but not the entire space. The affected pages will most likely work very slowly or not load at all. Experience for users viewing and editing the page is degraded.

What's the recommendations?

It really depends on how important the content is. Usually, pages with Jira issue macros are on the more important side, so we recommend splitting the page into smaller ones to get below the limit and make the page usable. If the page is old and no longer actively used, delete or archive it. Archiving is available only in Confluence Cloud so you'll need to wait until you migrate the affected pages.

Review affected pages

When viewing this recommendation from the dashboard, select the Download page list.

The downloaded CSV file includes:

• Page URLs of affected pages

• Jira issue macro count for each page

Archive pages after migration

After you migrate to Confluence Cloud, archive the affected pages in bulk.

Archive content items in Confluence Cloud

Split page content into multiple pages

You'll need to manually split your page into multiple smaller child pages so that each of them is below the limit of Jira issue macros.

How to split the page

This will depend on your content. Usually, you can find some high-level categories for your Jira issue macros, like Bugs, Development, Service projects, and so on. Review the macros on your page and organize them into categories.

Splitting the page

Once you know the categories, make multiple copies of the original page, and then remove redundant issue macros from each of them. 

Linking the child pages

After your child pages are ready, you can link them for easy access on the original page by using the Children display macro. It will automatically show and refresh any child pages nested under the parent page.