• http://192.168.0.71:7500/jira75/
• https://myjiraserver/jira

The output file format of the report. Possible options are:

• XLS = Returns an Excel file in XLS format that contains both the data and calculated averages.
• XLSX = Returns an Excel file in XLSX format that contains both the data and calculated averages.
• CSV = Returns a CSV (comma separated value) file that contains the report data.
• CSVAVERAGE = Returns a CSV (comma separated value) file that contains only average durations.
• CSVSUM = Returns a CSV (comma separated value) file that contains only sums of durations.

• xls
• xlsx
• csv
• csvaverage
• csvsum

Defines how the issues to be included in the report will be selected. Possible options are:

• user = Report will filter out the issues assigned to the selected user
• project = Report will filter out issues in the selected Jira project
• jqlfilter = Report will filter out issues based on an existing JQL filter
  • The value advanced is deprecated but is still valid and will be processed as jqlfilter.
• customjql = Report will filter out issues based on a given JQL query 
• sprint = Report will filter out issues based on an existing sprint 

• user
• project
• jqlfilter
• customjql
• sprint

If filterType is user, system expects a user name in the form user=<some_user_name>

• user=admin

If filterType is project, system expects a project key in the form projectKey=<project_key>

• projectKey=ABC

If filterType is jqlfilter, system expects a JQL filter ID in the form jqlFilterID=<jqlFilterID>

• jqlFilterID=10145

If filterType is customjql, system expects a JQL Query in the form customjql=<customJQL>

• customjql=project=ABC

If filterType is sprint, system expects a Sprint ID in the form sprintID=<sprintID>

• sprintID=2

Defines the column structure of the report. Possible options are:

• statusDuration = Report will show durations spent on each status as column values
• assigneeDuration= Report will show durations spent on each assignee as column values
• statusDurationByAssignee = Report will show durations spent on each status on each assignee as column values
• assigneeDurationByStatus = Report will show durations spent on each assignee on each status as column values
• groupDuration= Report will show consolidated durations spent on members of each group as column values
• statusCount = Report will show counts for each status
• transitionCount = Report will show counts for each transitions between statuses
• firstTransitionToStatusDate = Report will show the date the issue transitioned TO each status for the FIRST time as column values
• firstTransitionFromStatusDate = Report will show the date the issue transitioned FROM each status for the FIRST time as column values 
• lastTransitionToStatusDate = Report will show the date the issue transitioned TO each status for the LAST time as column values
• lastTransitionFromDate = Report will show the date the issue transitioned FROM each status for the LAST time as column values

• statusDuration
• assigneeDuration
• statusDurationByAssignee
• assigneeDurationByStatus
• groupDuration
• statusCount
• transitionCount
• firstTransitionFromStatusDate
• firstTransitionToStatusDate
• lastTransitionFromDate
• lastTransitionToStatusDate

The IDs of fields (separated by commas) on JIRA Issue that will be added to report output as columns.

Both system and custom fields are supported.

The IDs of fields (separated by commas) on JIRA Issue that will be used to group issues for average or sum data.

Both system and custom fields are supported. Some fields are intentionally excluded.

Date fields are included in a speacial format that allows data parts to be used. For further information look at TiS v4.8 - Field Names for REST Reports

A JSON array listing statuses for which the durations will be included in the report.

If not provided or left empty, the report will include all statuses in selected issues' histories.

For assignee based reports, durations of unselected statuses will be excluded from durations of assignee columns.

Supports two formats: Basic and Advanced

Basic:

Basic format is a comma separated list of status ID's to be included in the report.

Advanced:

Advanced format is a JSON text that contains status definitions.

Advanced format must be employed if you want to use the Consolidated Columns feature.

Type type attribute of each column defines whether the column is a Standard (std) or Consolidated (cons) column. For standard columns, id is the id of the status. For consolidated columns, the statuses array contains the IDs of statuses to be included in the column. For more information on status selection and column consolidation, please see TiS v4.8 - Status

The names of user groups (separated by commas) that will be included in Group Time report.

If not provided or empty, the report will included all durations in a column named "Not a member of selected groups"

• jira-administrators
• jira-users, jira-administrators

Sets whether included statuses in issues' histories will be included in the report or not:

Possible options are:

• true
• false

In not provided, "true" is assumed.

• true
• false

The dateConditionField type that startDate and endDate parameters will be based on. Possible options are:

• created = The startDate and endDate parameters will be used to filter issues based on issue create date.
• updated = The startDate and endDate parameters will be used to filter issues based on issue last update date.
• resolved = The startDate and endDate parameters will be used to filter issues based on issue resolution date.

• created
• updated
• resolved

calendar

The calendar that report durations will be calculated based on. Possible options are:

• normalHour = The durations will be based on a 7/24 calendar. (default)
• 0 = The default business calendar
• n = ID of a custom calendar

Tip: You can get the IDs of calendars using the Calendars endpoint, explained at the end of this page

• normalHours
• 0
• 1
• 2

• 24HourDays = Each day will be 24 hours.
• businessDays = Can be used for calendars other than 7/24. The durations will be based on the business calendar defined in admin settings. Length of each day will also be based on business hours defined in admin settings.

• 24HourDays
• businessDays

The format of duration data in the report. Possible options are:

• humanReadable = The values will be shown like "44 d 5 h 2 m 35 s"
• ddhhmmss = The values will be shown like "44:05:02:35"
• hhmmss = The values will be shown like "1061:02:35"
• days = The values will be shown in days, as a single decimal value like "44.71"
• hours = The values will be shown in hours, as a single decimal value like "1061.04"
• minutes = The values will be shown in minutes, as a single decimal value like "63662.59"
• seconds = The values will be shown in seconds, like "3819755"

• humanReadable
• ddhhmmss
• hhmmss
• days
• hours
• minutes
• seconds

The string format to use for displaying values of fields of type Date

If empty or missing, the date format defined in Time in Status Format Settings page is used. If Format Settings date format is also empty, the default date format set for Jira is used.

You can refer to the Java Documentation for more information about Date Format Strings.

• yyyy-MM-dd
• dd/MM/yy
• dd/MMM/yyyy

The string format to use for displaying values of fields of type DateTime

If empty or missing, the datetime format defined in Time in Status Format Settings page is used. If Format Settings datetime format is also empty, the default datetime format set for Jira is used.

You can refer to the Java Documentation for more information about Date Format Strings.

• yyyy-MM-dd hh:mm a
• dd/MM/yy HH:mm
• dd/MMM/yyyy HH:mm:ss