Duplication of information inside a macro

[Olivia Makin]

I have macros on reporting pages in confluence that pull data from Jira via JQL to build a report. Today these macros are duplicating the tickets it is pulling in, the page has run fine until now. 

[Maree Milne]

Hey Olivia

Atlassian have confirmed it's a bug and it's been raised here [CONFCLOUD-85064] [SLLV] Duplicate records showing on Jira Work Items in Confluence - Create and track feature requests for Atlassian products.

Cheers

Maree

[Sami Shaik]

@Maree Milne , thank you for coming back with the ticket; that is the piece this thread was missing. For anyone landing here later: the duplicate rows in the Jira macro on 4 September were a platform-side bug, now tracked as CONFCLOUD-85064, so the two questions to ask are whether your page is showing it today and, if it comes back, whether the ticket is still open. Vote and watch it rather than rebuilding the macro; the fix arrives from Atlassian's side, and the ticket is where you will hear about it first.

[Sami Shaik]

@Olivia Makin , glad it cleared, and @Maree Milne , since you saw the same thing on the same day on a different site, that pattern matters: two sites, same symptom, same window, no page or macro change on either side, gone without anyone touching it. That is a service-side blip in the path the Jira macro uses to fetch results, not a configuration problem on your pages. @Jovânio Junior  split (JQL versus render layer) and @Tomislav Tobijas ask for the macro name are still the right first questions when it happens on one site only, when it happens on two at once, the answer is "wait and check status," and you did the right thing.

Two things worth doing so the next time takes two minutes rather than a morning:

1. Check Atlassian's status page before touching the page. The Jira and Confluence status pages list incidents by day; a same-day entry, even one that does not mention macros, is usually the explanation. If your org has Atlassian Guard or Enterprise, org admins now also have System Health in Atlassian Administration (Insights, then System Health), which is generally available since August and shows site-level incidents with optional email alerts, so the person who owns the reporting pages can be told rather than find out.
2. Rule out the one page-side cause that produces the same symptom. The Jira macro pages its results, and if the JQL sorts on a field that is not unique (ORDER BY priority, ORDER BY updated when many items share a timestamp, or no ORDER BY at all), a row can land on the boundary of two pages and appear twice, and it will do so inconsistently from one render to the next. The fix is a tiebreaker on a unique field: ... ORDER BY priority DESC, key ASC. If the duplicates ever come back on one site only and the status page is clean, that is the first edit to make.

If it recurs on both your sites again, a Support ticket with the page URL, the macro's JQL and the timestamp is worth raising, because two independent reports on the same day is the kind of evidence that gets a platform issue acknowledged.

[Maree Milne]

We're also seeing this issue, have you already raised a support ticket with Atlassian? (and did you get an outcome?)

[Olivia Makin]

Just reviewed our confluence pages again this morning and it looks like it has resolved itself. 

[Lucienne Flynn]

We're seeing the same issue intermittently across multiple Confluence pages.

Different users can view the same page at the same time, with one user seeing duplicated entries while another sees the expected results.

The issue appears to resolve itself temporarily, then reoccurs later.

We've logged a support ticket with Atlassian Support.

[Sami Shaik]

@Lucienne Flynn , thank you for adding this, because it changes the picture and I want to correct my earlier framing rather than leave it standing. I described @Olivia Makin  and @Maree Milne  reports as a one-off that cleared on its own. Yours is intermittent and per-user: two people viewing the same page at the same moment, one seeing duplicates, the other the correct result. A JQL sort or paging problem would show the same wrong result to everyone, so that mechanism is ruled out for your case, and @Tomislav Tobijas  caching instinct from earlier in the thread is the one that fits: a per-user result being served from a stale or partially assembled cache rather than the live Jira query.

Two things that will help the ticket you have filed:

1. Capture the discrepancy while it is live: both users open the page, take screenshots including the browser's local time, and one of them hard-refreshes. If the refresh clears it for that user only, that is the evidence Support needs that the wrong result is cached per session, not generated by Jira.
2. Ask Support to confirm whether the affected pages share a macro configuration (same JQL, same field list, same row count) and whether the affected users share anything (region, browser profile, Confluence site vs. another site in the org). Intermittent plus per-user usually has a shape in that data.

If you get a root cause back, please post it here; three separate reports on one thread in a week is enough that other admins will land on it.

[Tomislav Tobijas]

Hi @Olivia Makin ,

On top of what Jovanio shared, can you maybe share a screenshot*, or just which macro we're talking about here? I'm assuming we're looking at the native one. 👀
*note that this is a public forum, so keep that in mind when sharing and confidential info

Also, you could check with your colleagues if they are seeing the same thing via their accounts. We could be looking at a caching issue or something 🤔

Also, I guess you could reach out to your IT department or Confluence admin to take a look. If nothing, they could open a support ticket Atlassian Support here for official team to take a look.

Cheers,
Tobi

[Jovânio Junior]

Hi Olivia,

Since the macros were working correctly until today, I’d first try to determine whether the duplication is coming from the JQL result itself or from the Confluence Jira macro rendering.

A quick way to isolate it would be:

Copy the exact JQL used by the macro.
Run it directly in Jira.
Check whether the same issue keys are duplicated there.

If Jira returns each issue only once but Confluence shows duplicates, then the problem is likely on the macro side rather than in your filter logic.

I would also try using the Refresh option inside the Jira macro itself, not just refreshing the browser page. Jira macros can use cached results, so forcing the macro to refresh can help rule out a stale rendering/cache issue. Atlassian documents that the macro keeps cached Jira results and that the macro-level refresh requests fresh data from Jira.

Since you mentioned this started suddenly and affected macros that were fine before, I would also test:

one of the affected JQLs in a brand-new Jira macro;
the same macro on a temporary Confluence page;
whether the duplicated rows always involve the same issue keys.

If the JQL is clean and a newly created macro also duplicates the results, I’d capture the affected page, JQL, duplicated issue keys, and the approximate time it started, then raise it with Atlassian Support. That would point more toward a recent Confluence/Jira macro regression than a configuration problem.

Hopefully that helps narrow down whether the issue is in Jira or in the macro rendering.