Jira work items macro stuck on “Searching…” when used inside Page Properties / included content (leg

[Jira Admin]

Hi all,

I’m running into a strange issue with the new Jira work items macro in Confluence Cloud, and I’m not sure if this is a bug, a limitation, or something I’m doing wrong.

Problem:

We’re using Confluence Cloud for our documentation. The structure is roughly, e.g;

• Release notes page with:

  • Expand macros for different sections

  • A Page Properties macro to capture release metadata

  • Sometimes, content is reused via the Include page

• Inside these sections, we show Jira issues for that specific release.

What works

• If I use the Jira legacy macro (old Jira issues macro) inside this structure (including inside the Page Properties macro), the Jira issues render correctly.

• If I use the new Jira work items macro at the top level of a page (not nested inside Page Properties / Include / etc.) with the same JQL, it also renders correctly.

What doesn’t work

When I put the new Jira work items macro in a nested context, it just shows “Searching…” and never displays any issues. For example:

• Inside a Page Properties macro table cell

• Or inside content that is brought in via Include page, which then might be inside an Expand macro

In the same spot:

• Legacy Jira macro → works fine

• New Jira work items macro → stuck on “Searching…”

Permissions don’t seem to be the problem:

• The same user can see the issues when:

  • Using the legacy macro in that spot, or

  • Using the new Jira work items macro at the top level on the page.

Steps to reproduce (simplified)

1. Create a page.

2. Insert a Page Properties macro.

3. Inside the Page Properties table, in one cell, insert a Jira work items macro with a valid JQL (one that returns issues when used elsewhere).

4. Publish the page.

Actual result:
The Jira work items macro shows “Searching…” and never loads any issues.

Expected result:
The Jira work items macro should render the issues the same way it does when used at the top level, or as the legacy Jira macro does in the same location.

Questions

• Is this a known limitation or bug with the new Jira work items macro when it’s nested inside:

  • Page Properties,

  • Include page / Excerpt,

  • or inside Expands and other container macros?

• Is there any supported pattern or workaround for using Jira work items together with Page Properties for release notes/reporting scenarios?

• Should we keep using the legacy Jira macro in nested contexts for now?

Any confirmation, workaround, or official guidance from Atlassian or others who’ve hit this would be really helpful.

Thanks in advance!

[Dan Breyen]

Hi @Jira Admin welcome to the community.  I tried your steps and I can't recreate the behavior.  For troubleshooting, have you tried using a different browser, or different PC?  Do others experience the same behavior? 

I took a quick look on Atlassian's Jira Site and found a few issues that could possibly be related.    CONFCLOUD-76245 CONFCLOUD-80421 

But nothing exact, feel free to browse out there for more content.  

Since you're the Product Admin, you can open a Work Item with Atlassian Support and have them weigh in on that.  I'd say look at Jira and try those few things, and if you're still having issues contact Support with very detailed steps to recreated it and they can investigate further.

Hope that helps.