We've shipped a reliability update to the Jira integration in both CelesteCS Math for Confluence Cloud and CelesteCS Reporting for Confluence Cloud, live now - no action needed on your side, it applies automatically.

What changed:

• Reporting for Confluence Cloud - the Jira Data Provider macro now returns the correct set of issues for every JQL query. Previously, queries could return more rows than expected, with some issues repeated, because of how Jira Cloud's newer search API handles paging internally. This is fixed - each query now returns exactly the issues that match, once each.
• Math for Confluence Cloud - the Jira issue-field functions (JIRAISSUEFIELDVALUES, JIRAISSUEFIELDVALUESBYFIELDID) and Jira issue-counting are more reliable against larger result sets for the same underlying reason.
• Custom field IDs with underscores are now fully supported. If you reference a Jira custom field by its ID (for example customfield_10123) in Reporting's Jira Data Provider fields parameter, this previously failed validation - it now works as expected.

These are backend reliability fixes to functionality that's already documented - see the Jira issue-field functions in our Math function reference and the Reporting Jira Data Provider macro documentation for full usage details.

As always, if you run into anything unexpected with Jira data in your Confluence Cloud reports, let us know.

Try it in your own Confluence: CelesteCS Reporting for Confluence on the Atlassian Marketplace – free trial for Cloud and Data Center. This example also uses CelesteCS Math for Confluence.