Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

When it is desired to add worklogs for the users in different time zones using REST API, there is a relationship between the time zone of the user who is specified in authentication header and the time zone of workStart part of request body.
The period control is done according to the time zone of the user who is specified in the authentication header. The date specified in the workStart and the time zone are changed according to the time zone of the user specified in the authentication header. Period check is done with this changed date. If this date within the closed period, worklog can not be added.

For example, workStart that is specified for the date and time is 01/Nov/21 08:00. The time zone of the user in the authentication header is GMT+11:00 and time zone of the user who is added worklog for is GMT+10:00. In this case, '2021-11-01T08:00:00+0900' is converted to GMT+11 and that is “01/Nov/21 10:00”. First of all, Is the date 01/Nov/21 10:00 belonging to a open period or not? If it is not (means it is belonging to a closed period), worklog can not be added. If it is included in open period, then the worklog is added. The same work log looks like the table below according to the time zones of different users.

Time zone of the User in the Authentication Header

GMT+11:00

Time zone of the user who is added worklog for

GMT+10:00

workStart

GMT+9:00

01/Nov/21 10:00

01/Nov/21 09:00

2021-11-01T08:00:00+0900

  • No labels