- Created by Emre Toptancı, last modified by Gizem Gökçe on 10.12.2024
GET /rest/issue
Returns a single issue report as text (CSV or JSON)
Request
The request takes all parameters you select on the screen for a report as query parameters.
Basic:
<service_url>/rest/issue?issueKey=<issueKey>&columnsBy=<columnsBy>&calendar=<calendar>&outputType=<outputType>
With all parameters:
<service_url>/rest/issue?issueKey=<issueKey>&columnsBy=<columnsBy>&fields=<fields>&statuses=<statuses>&groups=<groups>&includeDeletedStatuses=<includeDeletedStatuses>&trimHistoryStartDate=<trimHistoryStartDate>&trimHistoryEndDate=<trimHistoryEndDate>&calendar=<calendar>&dayLength=<dayLength>&viewFormat=<viewFormat>&outputType=<outputType>
Parameters
Parameter | Description | Required | Value Samples |
|---|---|---|---|
| issueKey | Key of the issue that report will be generated for. | Yes | ABC-1 |
| outputType | The output format of the report. Possible options are:
If not provided, "json" will be used. |
| |
| columnsBy | Defines the column structure of the report. Possible options are:
| Yes |
|
| timePeriod | The time period to use for statusDurationByTimePeriod and timePeriodDurationByStatus report types. Has no effect on other report types. Possible values are:
If not defined, Month will be used as the default value. |
| |
| multiVisitBehavior | Defines the behavior of reporting individual status visits. Only effective for Status Duration reports. If not provided, default behavior "total" will be used. |
| |
| fields | The IDs of fields (separated by commas) on JIRA Issues that will be added to report output as columns. Both system and custom fields are supported. For more information see TiS Cloud - Field Names for REST Reports | assignee,customfield_10020,customfield_10007,description,duedate, fixVersions | |
| historyFields | The IDs of fields (separated by commas) on JIRA Issues that will be used for Any Field reports. For details about Any Field report types please see: TiS Cloud - Report Types Both system and custom fields are supported. For more information see TiS Cloud - Field Names for REST Reports | only when columnsBy = anyfieldDuration or anyFieldCount | assignee,customfield_10020,customfield_10007,description,duedate, fixVersions |
| statuses | 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 Cloud - Status. Other parameters may be included in the URL as a query parameter but statuses parameter is expected to be sent in request body encoded as "application/x-www-form-urlencoded" Note: You can get the list of statuses and their IDs, directly from your Jira. Please check Statuses part of the documentation. | Basic 1,3,4,5,10001,10234 Advanced [
{
"id":"6",
"type":"std"
},
{
"id":"2",
"type":"std"
},
{
"name":"cons. status 1",
"type":"cons",
"statuses":[
"10008",
"3",
"10007"
]
}
]
| |
| assignees | Comma-separated list of IDs of users that will be included in the report. If not provided or empty, the report will include all the assignees found in issues' histories. Please refer to Jira Cloud REST API Documentation to get the IDs of your users |
| |
| groups | The names of user groups (separated by commas) that will be included in Group reports. If not provided or empty, the report will include all durations in a column named "Not a member of selected groups" |
| |
| dbsMetrics | The list of metrics that will be showed as columns in Duration Between Statuses reports. The parameter must be provided as JSON text. The maximum number of metrics allowed is 10. Each metric will report the duration between two statuses (or status sets) and consists of the following parameters: name: (required) Name of the metric. Can only include alphanumeric characters and space. from: The starting status(es) that the duration will be calculated from. Its format should be a JSON object contains id and order (first/last) of the status(es). Not defining this parameter means that the starting point will be "issue creation". to: (required) The target status(es) that the duration will be calculated until. Its format should be a JSON object contains id and order (first/last) of the status(es). excluded: List of status ids that will be excluded from the calculations. Time spent on these statuses will not be added to total time. Note: You can get the list of statuses and their IDs, directly from your Jira. Please check Statuses part of the documentation. | only when columnsBy = durationBetweenStatuses | [
{
"name":"Resolution time",
"to":{
"id":["5", "7"],
"order":"first"
}
},
{
"name":"Development time",
"from":{
"id":["1", "2", "3"],
"order":"first"
},
"to":{
"id":["6"],
"order":"last"
},
"excluded":[
"10008",
"10003"
]
}
]
|
| includeDeletedStatuses | Sets whether included statuses in issues' histories will be included in the report or not: Possible options are:
If not provided, "true" is assumed. |
| |
| trimHistoryStartDate | The start date of history trim for issues. When provided, only activities in each issue's history after the given date will be processed for the report. Must be provided in "yyyy-MM-dd" or "yyyy-MM-dd hh:mm" format. If time parameter is not provided, default time "00:00" will be used | 2017-07-01 00:00 | |
| trimHistoryEndDate | The end date of history trim for issues. When provided, only activities in each issue's history before the given date will be processed for the report. Must be provided in "yyyy-MM-dd" or "yyyy-MM-dd hh:mm" format. If time parameter is not provided, default time "00:00" will be used | 2017-08-31 23:59 | |
calendar | The calendar that report durations will be calculated based on. Possible options are:
Tip: You can get the IDs of calendars using the Calendars endpoint. | Required for Duration reports |
|
| dayLength |
| Required for Duration reports |
|
| viewFormat | The format of duration data in the report. Possible options are:
If not provided, "minutes" will be used. |
| |
| dateFormat | The string format to use for displaying values of fields of type Date If empty or missing, the date format defined in TiS Cloud - 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. |
| |
| dateTimeFormat | The string format to use for displaying values of fields of type DateTime If empty or missing, the datetime format defined in TiS Cloud - 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. |
| |
| emptyValueToken | The token to use for empty values in the report (for example when an issue has never visited a status) Selecting a custom token might make it easier for the requesting system to process the data. Possible options are:
|
|
Examples
https://tis.obss.io/rest/issue?issueKey=XYZ-34&columnsBy=statusDuration&calendar=normalHours https://tis.obss.io/rest/issue?issueKey=ABC-3&columnsBy=statusDuration&fields=assignee&statuses=3,10000,10001&includeDeletedStatuses=true&calendar=normalHours&dayLength=24HourDays&viewFormat=minutes&outputType=csv https://tis.obss.io/rest/issue?issueKey=TEST-85&columnsBy=statusDuration&multiVisitBehavior=last&calendar=0&dayLength=24HourDays&viewFormat=minutes&outputType=json https://tis.obss.io/rest/issue?issueKey=TTP-123&columnsBy=statusDuration&calendar=1&dayLength=businessDays&viewFormat=minutes&outputType=csv https://tis.obss.io/rest/issue?issueKey=TIS-1&columnsBy=statusDuration&calendar=1&dayLength=businessDays&viewFormat=humanReadable https://tis.obss.io/rest/issue?issueKey=QWERTY-45&columnsBy=statusDuration&trimHistoryStartDate=2017-09-01 00:00&trimHistoryEndDate=2017-10-31 00:00&calendar=1&dayLength=businessDays&viewFormat=minutes&outputType=csv
Responses
Success
HTTP 200
Returns a single issue report as text (CSV or JSON)
{
"dateTimeFormat": "dd/MMM/yy h:mm a",
"dateFormat": "dd/MMM/yy",
"timeZone": "Europe/Istanbul",
"locale": "en-US",
"viewFormat": "humanReadable",
"isComposite": false,
"columnsBy": "Status Duration",
"multiVisitBehavior": "total",
"calendar": {
"allWorkingDaysHaveEqualLengths": true,
"calendarSuccessfullyLoaded": true,
"clientKey": null,
"dailyWorkingHours": 24.0,
"holidays": [],
"id": null,
"is7x24Calendar": true,
"isDefault": null,
"name": "normalHours",
"timeZone": "UTC",
"workingTimes": [
{
"end": 86400000,
"start": 0,
"weekday": "SUNDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "MONDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "TUESDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "WEDNESDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "THURSDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "FRIDAY"
},
{
"end": 86400000,
"start": 0,
"weekday": "SATURDAY"
}
]
},
"dayLength": "24HourDays",
"query": " issuekey = 'ABC-1'",
"reportDate": "03/Dec/20 1:39 PM",
"version": "1.29.0.1",
"isAggregationType": false,
"isOverall": false,
"isAverage": false,
"isSum": false,
"isMedian":false,
"isStddev":false,
"table": {
"header": {
"headerColumns": [
{
"id": "issuekey",
"value": "Key"
},
{
"id": "summary",
"value": "Summary"
}
],
"groupByColumns": [],
"fieldColumns": [],
"valueColumns": [
{
"id": "10000",
"value": "To Do(10000)",
"isConsolidated": false
},
{
"id": "10002",
"value": "Done(10002)",
"isConsolidated": false
},
{
"id": "3",
"value": "In Progress(3)",
"isConsolidated": false
}
]
},
"body": {
"rows": [
{
"headerColumns": [
{
"id": "issuekey",
"value": "ABC-1"
},
{
"id": "summary",
"value": "Example 1"
}
],
"groupByColumns": [],
"fieldColumns": [],
"valueColumns": [
{
"id": "10000",
"value": "0d 2h 36m 29s",
"raw": "9389589",
"count": "2"
},
{
"id": "10002",
"value": "0d 0h 34m 0s",
"raw": "2040000",
"count": "1"
},
{
"id": "3",
"value": "1431d 18h 38m 15s",
"raw": "123705495310",
"count": "3"
}
],
"currentState": [
{
"id": "3",
"value": "237d 2h 41m 48s",
"raw": "20486508218"
}
]
}
]
}
}
}
"Key","Summary","To Do","Done","In Progress" "ABC-1","Example 1","0d 2h 36m 29s","0d 0h 34m 0s","1431d 18h 38m 15s"
Invalid Parameter
HTTP 400
When one or more of the required parameters are missing or one or more of the supplied parameter values are invalid.
messages array contains the error messages for invalid parameters.
{
"status": 400,
"message": "Invalid report parameters",
"messages": [
"ERROR: Invalid issuekey value: 'abc'",
"ERROR: Invalid outputType value: 'xls'. Possible values are 'csv' and 'json'"
],
"pluginVersion": "1.18.0.1",
"time": "2020-05-22 06:31:15"
}
- No labels