This is the documentation for Dataplane Reports 3.3. - 4.0.x.
If you are using an earlier version of the app, you can access the documentation from the version index page.
Analyze saved Dataplane reports
The administration reports endpoint provides Jira administrators with a REST API for querying and analyzing saved Dataplane Reports across their Jira instance.
This endpoint allows administrators to:
Identify reports that may require attention during migration.
Analyze report usage patterns.
Discover unused, outdated, or complex reports.
Audit sharing and configuration settings at scale.
This is useful when preparing for cloud migration or when reviewing report usage across large Jira instances.
When to use this endpoint
Use the Admin Reports REST API when you need to:
Review report complexity across your instance.
Identify reports that require manual review before migration.
Determine how many reports are actively used on dashboards.
Analyze sharing patterns.
Assess large datasets efficiently without relying on SQL queries.
This endpoint leverages Dataplane’s internal logic to return accurate results, even for complex report configurations.
Access and authentication
You must be a Jira system administrator authenticated through websudo to access the endpoint.
To start an administrator's websudo session go to the Dataplane Reports > Administration page, which will prompt for authentication.
Attempting to access the endpoint without proper authentication or authorization returns a 403 Forbidden error.
Endpoint details
URL
http(s)://<JIRA_ROOT_DOMAIN>/rest/dataplane/latest/admin/reports
Method
GET
Authentication
Required (Jira user session)
Authorization
Jira System Administrator
Response format
JSON
Query parameters
All query parameters are optional.
If no parameters are provided, the endpoint returns all saved Dataplane reports.
Common parameters
Parameter | Type | Description | Example |
|---|---|---|---|
| String | Filter by report owner user key |
|
| String | Filter by report template type |
|
| Integer | Include only reports executed within the last N months |
|
| Integer | Include only reports modified within the last N months |
|
| Boolean | Filter by the presence of customizer scripts |
|
| Boolean | Filter by reports with multiple segments |
|
| String | Filter by chart visualization type |
|
| Boolean | Filter by reports shared with Jira groups |
|
| Boolean | Filter by reports shared with Jira projects |
|
| String | Filter by specific segment type(s). Accepts a comma-separated list of segment keys. A report matches if it contains any of the specified segments. |
|
| Boolean | Filter by reports used in Jira dashboards |
|
| Integer | Maximum number of reports to return (defaults to 1000 if not specified). Ignored when |
|
| Boolean | Return only the count of matching reports without report details. When |
|
Response format
Standard response (≤ 100 reports)
When the query returns more than 100 reports and countOnly is not set, the endpoint automatically triggers a JSON file download with the filename format: dataplane_reports_YYYYMMDD_HHMMSS.json
The downloaded file contains the same JSON structure as the standard response, formatted with proper indentation for readability.
The maxResults parameter limits the total number of reports returned (defaults to 1000). If you set maxResults to a value less than 100, the file download will not trigger even if all matching reports are returned. The countOnly parameter disables result limiting and file downloads.
If the query returns 100 or fewer reports, the endpoint returns JSON with the following structure:
{
"count": 1,
"reports": [
{
"id": 12345,
"guid": "abc123-def456-ghi789",
"name": "Issue Status Report",
"reportTemplate": "issueStatus",
"owner": "admin",
"createdDate": "2024-01-15T10:30:00Z",
"modifiedDate": "2024-12-20T14:45:00Z",
"lastRunDate": "2025-01-02T09:15:00Z",
"reportUrl": "https://your-jira.com/plugins/servlet/dataplane/report?guid=...",
"chartType": "columnChart",
"segments": ["grouping.currentProject", "grouping.issueType"],
"dashboards": [
{
"dashboardId": 10001,
"dashboardName": "Executive Dashboard"
}
]
}
]
}
Count-only response
When countOnly=true, the endpoint returns only the total number of matching reports:
{
"count": 42
}
When countOnly=true:
The
maxResultsparameter is ignored.All matching reports are counted.
No report details are returned.
File download response (> 100 reports)
When the query returns more than 100 reports (and countOnly is not set), the endpoint automatically triggers a JSON file download with the filename format: dataplane_reports_YYYYMMDD_HHMMSS.json. The downloaded file contains the same JSON structure as the standard response, formatted with proper indentation for readability.
Note: The maxResults parameter limits the total number of reports returned (defaults to 1000). Setting maxResults to a value less than 100 will prevent the file download from triggering, even if all matching reports are returned. The countOnly parameter disables result limiting and file downloads.
General maintenance use cases
Migration assessment use cases
The Admin Reports endpoint is especially useful when preparing for migration to Dashboard Hub.
Additional resources
Report Templates
Template Key | Description |
|---|---|
| Issues Table |
| Issues Created by Date |
| Issues Resolved by Date |
| Issues by Date |
| Issue Reporters by Date |
| Time to Next Status |
| Time from Status to Status |
| Resolution Time |
| Closure Time |
| Stat Sum by Date |
| Current Issue Values |
| Issue Values Snapshots by Date |
| Issue Status Flow |
| Project Links |
| Current Stat Sum |
| Issues Work Log Table |
| Work Logged by Date |
| Project Work Logged by Date |
| User Work Logged by Date |
| Issue Values Snapshots Sum by Date |
| Full Custom Current |
| Full Custom Historical |
| Full Custom Transition |
| Pivot Table |
| Issues Entering Status by Date |
| Time in Status |
| Issue Assignees |
| Issue Priorities |
| Issue Statuses |
| Issue Affects Versions |
| Issue Fix Versions |
| Issue Components |
| Issue Reporters |
| Issue Resolutions |
| Issue Security Levels |
Chart Types
Chart Type | Description |
|---|---|
| Table view |
| HTML Table view |
| Bar chart |
| Vertical bar chart |
| Grouped bar chart |
| Vertical grouped bar chart |
| Normalized bar chart |
| Vertical normalized bar chart |
| Pie chart |
| Multiple pie chart |
| Column chart |
| Grouped column chart |
| Normalized column chart |
| Line chart |
| Area chart |
| Range chart |
| Line difference chart |
Segment Types
Common segment values for filtering (any field selectable in Dataplane "segment by" can be used):
Segment Key | Description |
|---|---|
| Project |
| Issue Type |
| Priority |
| Status |
| Assignee |
| Reporter |
| Component |
| Label |
| Project Category |
| Issue Key |
The segment parameter accepts comma-separated values to filter by multiple segment types. For example, segment=grouping.currentProject,grouping.issueType will match reports segmented by Project or Issue Type (or both). A report matches if it contains any of the specified segments.
