-
Notifications
You must be signed in to change notification settings - Fork 17
Closed
Description
we are currently experimenting with this plugin and found the following case, resulting in a wrong returing startDate of a worklog entry using /rest/jira-worklog-query/1.2.0/find/worklogs
compare timestamp of worklog 23634, timestamp should be 2015-03-19T12:57:00+0100
{
"id": 23634,
"startDate": "2015-03-19T00:57:00+0100",
"issueKey": "BIT-3",
"userId": "<user>",
"duration": 10800,
"comment": "",
"updated": "2015-03-19T00:59:34+0100"
},
{
"id": 23635,
"startDate": "2015-03-19T13:08:08+0100",
"issueKey": "BIT-3",
"userId": "<user>",
"duration": 300,
"comment": "more time spent",
"updated": "2015-03-19T13:08:08+0100"
},compare to jira's rest api result https:///rest/api/2/issue/BIT-3/worklog/23634
{
"self": "https://<server>/rest/api/2/issue/80923/worklog/23634",
....
"comment": "",
"created": "2015-03-19T12:58:07.094+0100",
"updated": "2015-03-19T12:58:07.094+0100",
"started": "2015-03-19T12:57:00.000+0100",
"timeSpent": "3h",
"timeSpentSeconds": 10800,
"id": "23634"
}I noticed, it happens only between 12:00 and 12:59, startDates before 11 or after 13 (see worklog 23635) are correct. any idea?
Metadata
Metadata
Assignees
Labels
No labels