Timezone issue in worklog comparaisons

[dstj]

@Socolin Salut! :)

I think this commit is causing a bug:
80d6b741c361e245f715591b935993ab760e7826

One is retrieved as Utc while the other is retrieved as Local, so the comparaison is always considering them to be different.

The correct one is 2025-06-30 15:00:00Z (11 EST)

Even if I say "y" to update the entries, the next sync, they are still detected as different because of the timezone diff.

[Socolin]

I'm confused here, when I run this, I'm getting 1 date as UTC and 1 as Local, but the offset match.

The one in UTC probably come from the conversion from toggl DateTimeOffset when calling startDate.UtcDateTime
The one with the local timezone is probably returned by jira.

Feel like the date is not saved when updating the entry, does they appear correct in the UI ?

I checked UpdateWorkLogAsync with the doc and it seems, we are using the wrong model to update the entry. Looking at the documentation it seems the field should be started and not StartDate so I think we should use Atlassian.Jira.Remote.RemoteWorklog instead of Atlassian.Jira.Worklog.

Can you test if the following is working after replacing it in UpdateWorkLogAsync

var request = new Atlassian.Jira.Remote.RemoteWorklog()
{
	comment = entry.JiraWorkLog.Comment,
	startDate = entry.JiraWorkLog.StartDate,
	timeSpent = entry.JiraWorkLog.TimeSpent,
	timeSpentInSeconds = entry.JiraWorkLog.TimeSpentInSeconds
};
await _jira.RestClient.ExecuteRequestAsync(Method.PUT, $"rest/api/3/issue/{entry.IssueKey}/worklog/{entry.JiraWorkLog.Id}", request);
return OperationResult.Success(entry);