Issue Time-in-Status Export API
Learn how to export issue lifecycle and time-in-status analytics from Harness SEI.
The Issue Time-in-Status Export API exports issue lifecycle analytics showing how long issues spend in each workflow status. Exports can be aggregated by sprint or team and are returned in CSV format.
Authentication
All requests require the following headers:
authorization
ApiKey <YOUR_SEI_API_KEY>
Content-Type
application/json
You must also include the following query parameters on all requests:
projectIdentifier
Harness project identifier
orgIdentifier
Harness organization identifier
Export workflow
Creates a new asynchronous issue time-in-status export job.
# Replace BASE_URL with your Harness cluster URL <a href="#replace-baseurl-with-your-harness-cluster-url" id="replace-baseurl-with-your-harness-cluster-url"></a>
POST {BASE_URL}/v2/insights/ticket-data/exports{
"scope": {
"teamId": "team_abc123", // String identifier; use either teamId OR orgTreeName (not both)
"orgTreeName": "string",
"orgIdentifier": "string", // Required when using `orgTreeName`
"projectIdentifier": "string"
},
"dateRange": {
"start": "2024-01-01", // Required
"end": "2024-03-31" // Required
},
"issueStatuses": [
"In Progress",
"In Review",
"QA",
"Done"
],
"options": {
"aggregationLevel": "sprint",
"granularity": "weekly",
"terminalDateColumn": "issue_resolved_at"
}
}The following request fields are available:
scope.teamId
Export data for a specific team.
scope.orgTreeName
Export data for an organization tree.
dateRange.start
Export start date (yyyy-MM-dd).
dateRange.end
Export end date (yyyy-MM-dd).
issueStatuses
List of workflow statuses to measure (In Progress, In Review, QA, or Done).
options.aggregationLevel
Aggregation level (sprint or team).
options.granularity
Reporting interval (daily, weekly, monthly, quarterly).
options.terminalDateColumn
Terminal date used for calculations (issue_resolved_at or version_release_date).
Poll the export until the status changes to COMPLETED.
The following export statuses are available:
QUEUED
Export queued.
PROCESSING
Export in progress.
COMPLETED
Export ready.
FAILED
Export failed.
Downloads the generated CSV export file.
Downloads are gzip-compressed by default and export responses include team hierarchy information where applicable.
Last updated
Was this helpful?