Zephyr Squad Cloud –for Test Cycle startDate and endDate mismatch in API response via HttpClient
Description:
Inconsistency in the Cycle entity response from Zephyr Cloud (Zephyr Squad)
When I create a cycle with startDate = 2025-10-31 and then fetch it through Postman, the response shows the correct dates:
API:
https://prod-api.zephyr4jiracloud.com/connect/public/rest/api/1.0/cycles/search?projectId=10381&versionId=28634
Response from Postman:
{
"createdByAccountId": "5b03e4117409772b3a334df7",
"endDate": "2025-11-01",
"tenantKey": "ODVkM2E4ODEtMmZiNi0zMzRhLWI4NzEtODZhNzgyNmVmMmRk",
"description": "",
"cycleIndex": "6c11fb8a-19b6-4d05-8d23-84806383b41c",
"creationDate": "2025-10-31",
"projectCycleVersionIndex": "10381_28634",
"environment": "",
"versionId": 28634,
"build": "",
"createdBy": "5b03e4117409772b3a334df7",
"name": "cycle2",
"id": "6c11fb8a-19b6-4d05-8d23-84806383b41c",
"projectId": 10381,
"startDate": "2025-10-31"
}
However, when I fetch the same cycle through my Java code using Apache HttpClient, the same API returns the following:
Response from Java HttpClient:
{
"build": "",
"createdBy": "5b03e4117409772b3a334df7",
"createdByAccountId": "5b03e4117409772b3a334df7",
"creationDate": "2025-10-31",
"cycleIndex": "6c11fb8a-19b6-4d05-8d23-84806383b41c",
"description": "",
"endDate": "2025-10-31",
"environment": "",
"id": "6c11fb8a-19b6-4d05-8d23-84806383b41c",
"name": "cycle2",
"projectCycleVersionIndex": "10381_28634",
"projectId": 10381,
"startDate": "2025-10-30",
"tenantKey": "ODVkM2E4ODEtMmZiNi0zMzRhLWI4NzEtODZhNzgyNmVmMmRk",
"versionId": 28634
}
As seen, the creationDate remains the same (2025-10-31) in both, but startDate and endDate are shifted by one day only in the Java client response. The same happens consistently across cycles.
I have verified all headers and request parameters — both requests are identical.
Since this is Zephyr Cloud, timezone differences shouldn’t normally affect the data, but the shift seems to occur only for startDate and endDate, not for creationDate.
It looks like these fields might be internally handled differently (possibly as UTC timestamps), leading to the shift after deserialization.
Requesting confirmation on whether Zephyr Cloud stores or serializes startDate and endDate differently from creationDate, and if any recent update could have caused this difference in behavior.