Supported Integrations
Reports, Charts, Templates, CQL & Export for Confluence integrates natively with Confluence Cloud and supports Jira data where the two products are connected.
Native Confluence Integration
The app is built as a Confluence Cloud macro and uses the Confluence REST API and CQL to access content. All report data is fetched live from your Confluence instance - no external connectors, no third-party services.
What CQL Can Target
CQL (Confluence Query Language) gives you precise, rules-based access to all Confluence content types and metadata fields.
| Content Type | CQL type Value | Description |
|---|---|---|
| Pages | type = page | Standard Confluence pages |
| Blog Posts | type = blogpost | Blog entries in any space |
| Attachments | type = attachment | Files attached to pages |
| Comments | type = comment | Inline and page-level comments |
| Space | Accessed via space field | Filter by one or more space keys |
Confluence Spaces & Pages
- Spaces - query content from any space you have access to; filter by space key (
space = "ENG") - Pages - filter by page ID, title, label, creator, last modifier, status, or date range
- Blogs - access blog posts the same way as pages, using
type = blogpost - Attachments - list and inspect file attachments, including file name, size, and parent page
- Labels - filter content by one or more labels (
label = "decision") - Ancestors / Descendants - use the
ancestorfield in CQL or the Include Children toggle to scope reports to a page tree
Confluence Permissions Respected
The app fully respects Confluence's native permission model. Reports show only content the viewing user is authorized to access.
| Scenario | Result |
|---|---|
| Viewer has access to all queried spaces | Full results displayed |
| Viewer has access to only some spaces | Only permitted content appears |
| Viewer has no access to a space | That space's content is excluded entirely |
| Page has content restrictions | Restricted pages are excluded from results |
Note: Two users viewing the same report on the same page may see different results - each viewer sees only the content they are permitted to access.
Jira Integration
If your Confluence Cloud site is connected to Jira Cloud, some Jira-related metadata fields may be available through Confluence's linked content features.
| Integration Scenario | What's Available |
|---|---|
| Jira issues linked to Confluence pages | Linked Jira issue references may appear in page metadata |
| Confluence pages in Jira-connected spaces | Standard Confluence fields (space, type, creator, labels, dates) are fully available |
| Jira-specific fields (e.g., issue status, assignee) | Not directly available - these live in Jira, not Confluence |
Important: The app queries Confluence content, not Jira directly. Jira issue data (status, priority, assignee) is not available as report fields unless it has been explicitly surfaced in Confluence page metadata.
What Confluence Data CQL Can Target - Full Reference
| CQL Field | Description | Example |
|---|---|---|
type | Content type | type = page |
space | Space key | space = "ENG" |
title | Page or blog title | title ~ "Release Notes" |
label | Assigned labels | label = "urgent" |
creator | Original author | creator = currentUser() |
contributor | Any contributor | contributor = "jsmith" |
lastModifier | Most recent editor | lastModifier = currentUser() |
created | Creation date | created >= "2026-01-01" |
lastModified | Last update date | lastModified >= now("-30d") |
ancestor | Parent page ID | ancestor = 12345 |
status | Content status | status = "current" |