This documentation is for an old version of Dataplane Reports.
View the latest documentation, or the list of documentation for all versions.
Supported Jira Fields
- David Goldstein
Overview
Support for different Jira field types varies with the Dataplane report being used.
For example, historical reports support a different set of fields than current reports, since not all Jira fields are indexed historically. In addition, only numeric-type fields can be used where Dataplane Reports requires a numeric field, and only date-type fields can be used when plotting issues on a timeline.
The tables on this page indicate the extent of support for different Jira field types within Dataplane Reports. Here is a key to the table columns:
Available Use | Description |
---|---|
Value Of/Segment By (Current Reports) | fields marked with can be used for the Segment By or Value Of options in current value reports (non-historical reports) |
Value Of/Segment By (Historical Reports) | fields marked with can be used for the Segment By or Value Of options in historical (date-based) reports |
Value Of (Numeric Field Reports) | fields marked with can be used for the Value Of option in the Sum Numeric Field report, the Sum Numeric Field by Date report, and the Issue Values Snapshots Sum by Date report |
Date Basis (Historical Reports) | fields marked with can be used for the Date Basis option in historical (date-based) reports, including the Issues by Date report, the Issues Created by Date report, the Issues Resolved by Date report, and the Sum Numeric Field by Date report |
Columns (Issues Table Report) | fields marked with can be selected for columns in the Issues Table Report |
Columns/Segment By (Work Log Reports) | fields marked with can be selected for columns or used for the Segment By option in the Issue Work Log Table report, the Work Logged by Date report, the Project Work Logged by Date report, and the User Work Logged by Date report |
Standard Jira Fields
The following standard Jira fields and issue properties marked with are supported by Dataplane Reports:
Available Use Field/Property | Value Of/ | Value Of/ Segment By (Historical Reports) | Value Of | Date Basis | Columns (Issues Table Report) | Columns/ Segment By (Work Log Reports) |
---|---|---|---|---|---|---|
Affects Version/s | ||||||
Assignee | ||||||
Component/s | ||||||
Created Date | ||||||
Creator | ||||||
Description | ||||||
Due Date | ||||||
Fix Version/s | ||||||
Issue Key | ||||||
Issue Type | ||||||
Labels | ||||||
Original Time Estimate | ||||||
Priority | ||||||
Project | ||||||
Project Category | ||||||
Reporter | ||||||
Resolution | ||||||
Resolution Date | ||||||
Security Level | ||||||
Status | ||||||
Status Category | ||||||
Summary | ||||||
Time Remaining | ||||||
Time Spent | ||||||
Updated Date | ||||||
Votes | ||||||
Worklog Author | ||||||
Worklog Date |
Standard Jira Custom Field Types
The following standard Jira custom field types marked with are supported by Dataplane Reports:
Available Use Custom Field Type | Value Of/ | Value Of/ Segment By (Historical Reports) | Value Of | Date Basis | Columns (Issues Table Report) | Columns/ Segment By (Work Log Reports) |
---|---|---|---|---|---|---|
Checkboxes | ||||||
Date Picker | ||||||
Date Time Picker | ||||||
Group Picker (multiple groups) | ||||||
Group Picker (single group) | ||||||
Labels | ||||||
Number Field | ||||||
Project Picker (single project) | ||||||
Radio Button | ||||||
Select List (cascading) | ||||||
Select List (multiple choices) | ||||||
Select List (single choice) | ||||||
Text Field (multi-line) | ||||||
Text Field (single-line) | ||||||
URL Field | ||||||
User Picker (multiple users) | ||||||
User Picker (single user) | ||||||
Version Picker (multiple versions) |
Jira Software Fields
The following Jira Software fields marked with are supported by Dataplane Reports:
Available Use Field | Value Of/ | Value Of/ Segment By (Historical Reports) | Value Of | Date Basis | Columns (Issues Table Report) | Columns/ Segment By (Work Log Reports) |
---|---|---|---|---|---|---|
Epic Link | ||||||
Epic Name | ||||||
Epic Status | ||||||
Epic/Theme | ||||||
Rank | ||||||
Sprint | ||||||
Story Points |
Advanced Roadmaps for Jira Fields
Dataplane Reports does not directly support Advanced Roadmaps fields, however they can be integrated with Dataplane Reports through use of a Jira Misc Custom Fields (JMCF) or ScriptRunner custom field.
Third-Party App Custom Fields
Dataplane Reports directly supports custom fields provided by a number of popular third-party apps including:
Dataplane Reports also supports all third-party app custom fields that Atlassian defines as "stattable"—those which support the standard Jira CustomFieldStattable interface. Most of the standard Jira Core dashboard gadgets support only stattable fields, so if a third-party custom field is available in one of the standard Jira dashboard gadgets, it will generally be available in Dataplane as well. When in doubt, ask your app vendor if the desired custom field is "stattable", or contact our support team for help.
As a backup option, there is a third-party app called Stattable Searchers which can make certain non-stattable, third-party custom fields appear as stattable to Jira Core dashboard gadgets and to Dataplane. While this app is no longer available from Atlassian Marketplace, it can be compiled from source.
The following third-party app custom field types marked with are supported by Dataplane Reports:
Available Use Custom Field Type | Value Of/ | Value Of/ Segment By (Historical Reports) | Value Of | Date Basis | Columns (Issues Table Report) | Columns/ Segment By (Work Log Reports) |
---|---|---|---|---|---|---|
General | ||||||
"stattable" fields | ||||||
Elements Connect | ||||||
Calculated Date/Time | ||||||
Calculated Duration | ||||||
Calculated Number | ||||||
Calculated Text/Html | ||||||
Last Field Value Change Date/Time | ||||||
Time in Status | ||||||
Transition Count | ||||||
Transition Date/Time | ||||||
Script Field | ||||||
Account | ||||||
Team | ||||||
Team Role | ||||||
User Picker |
For complete details on how to work with ScriptRunner and Elements Connect fields, see:
Page Contents