Supported Integrations
Dashboard Templates, Charts, Graphs & Reports for Jira is a native Jira Cloud app built on Atlassian Forge. It integrates deeply with Jira's own data model and dashboard system - no external services, no third-party connectors, and no data leaving your Atlassian environment.
Native Jira Integration
The app reads and displays data directly from your Jira Cloud instance. All data access uses Jira's standard APIs within the Forge sandbox - the same data you would see in Jira's own issue navigator and board views.
Jira Data the App Uses
| Jira Data Type | How the App Uses It |
|---|---|
| Issues | Primary source for all charts, tables, and filters - count, sum, group, and filter issues by any field |
| Projects | Select one or more projects as the data source for a gadget |
| Saved Filters | Use any saved Jira filter as a gadget data source - picks up the filter's JQL automatically |
| Sprints | Filter and group issues by sprint (Active, Future, Closed); supports openSprints() and closedSprints() in JQL |
| Custom Fields | Any custom field on your Jira instance can be used as a Chart By, Group By, column, or filter field |
| Standard Fields | Status, Priority, Assignee, Reporter, Issue Type, Component, Labels, Fix Version, Epic Link, Story Points, Due Date, Created, Updated, Resolved |
| User Data | Assignee and Reporter fields display user names and avatars (Issue List); JQL supports currentUser() for personal views |
| Jira Statuses & Workflows | Status values reflect your project's actual workflow statuses - no mapping needed |
| Epics | Group or filter by Epic Link or Epic Name using standard Jira fields or JQL |
What the App Cannot Access
- Jira Service Management (JSM) specific fields - some JSM-only fields may not be available depending on your Jira configuration
- External issue trackers - the app only reads from Jira Cloud; no GitHub, Asana, or Linear integration
- Confluence pages - the app does not read from Confluence
- Jira Server / Data Center - Atlassian Forge is Cloud-only
Jira Dashboard Gadget Integration
The app is delivered as Jira dashboard gadgets - the standard Atlassian mechanism for adding content to Jira dashboards.
What This Means
- Gadgets appear in the standard Jira Add gadget gallery
- Gadgets follow Jira dashboard share permissions - view or edit access is controlled by whoever owns the dashboard
- Gadgets can be placed on any Jira dashboard, including personal, team, and company dashboards
- Gadgets respect Jira's column layout system (1, 2, or 3 column layouts)
- Multiple gadgets of the same type can be added to the same dashboard
Gadget Sizing
Gadgets adjust their display to the column width assigned in the dashboard layout. For best results:
| Gadget | Recommended Column Width |
|---|---|
| Custom Charts (Pie, Bar, Line) | 1 or 2 columns |
| Issue List | 2 or 3 columns (wider is better for many columns) |
| Dynamic Filter Controller | Full width (3 columns) or at least 2 columns |
Jira Filter Integration
Saved Jira Filters can be used directly as the data source for any gadget:
- Open a gadget in edit mode
- In the left panel, set Source Type to Saved Filter
- Search for the filter by name
- Select the filter - the gadget uses its JQL automatically
Benefits of Using Saved Filters
- Changes to the saved filter in Jira are reflected automatically in the gadget
- Filters managed by your team ensure everyone uses consistent data definitions
- Useful for organization-wide dashboards where a central filter defines "all active projects"
Supported Filter Types
| Filter Type | Supported |
|---|---|
| Personal saved filters (My Filters) | Yes |
| Shared filters (visible to you) | Yes |
| Favorite filters | Yes |
| Starred filters | Yes |
| Filters you don't have access to | No - only filters you can view in Jira |
No External Service Integrations
The current version does not natively integrate with:
| Tool | Status |
|---|---|
| Slack | Not supported |
| Microsoft Teams | Not supported |
| Confluence | Not supported |
| Google Sheets / Excel | Not supported (use CSV export instead) |
| BI tools (Tableau, Power BI) | Not supported (use CSV export instead) |
| Jira Server / Data Center | Not supported |
Workaround for BI tools: Use the CSV export feature to download issue data, then import it into your preferred BI or spreadsheet tool.
Platform & Security
| Aspect | Detail |
|---|---|
| Platform | Atlassian Forge (Cloud-native, sandboxed) |
| Data storage | Forge KVS - gadget configurations only; no issue data stored |
| Data transit | All data accessed within Atlassian's infrastructure; no external API calls |
| Permissions | Respects Jira's native project and issue permissions - users only see data they can access in Jira |
| Authentication | Uses Atlassian's standard OAuth/session for all API calls |