Right now we are evaluating the joggle toggle plugin for Jira Download edition.
When testing time tracking through the toggle desktop app for linux i notice my time entries that get synced back to Jira are off (one hour)
For example the time entry in Toggle is
7:55-9:07 in Jira it says 6:55
My settings in Jira, in Toggle and local time are all GMT+1 (Amsterdam/The Netherlands)
Also to me it would seem more logical if the task end time was recorded in Jira instead of the start time
I don't think so there is no setting in Jira for that? You comment did however did me a different idea. Although the settings in the database are correct maybe the settings for the JVM are not correct, I guess toggle talks to Jira through the API, maybe this uses the JVM setting?
Could you be experiencing something like this :
More info can be found here :
Toggle is correct, issues comments, create date, update date and all are correct in JIRA too. Burndown charts are all offset by what looks like the difference to GMT. Server time zone is set to LA, server time was set to LA. Jira was not setup with any JVM timezone setting.
I then set the Jira JVM setting for timezone in setenv.sh to GMT and it seems to have fixed it. This leaves the server at LA time, server time zone at LA time zone and the JVM at GMT. Yes, I could set the entire server up in GMT, but that's not doable right now for other reasons.
So there may be some code in the integration that's not converting times like JIRA does under the hood.
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG