It's not the same without you
Join the community to find out what other Atlassian users are discussing, debating and creating.
Hello Operations Group;-)
You have to sign in with an admin user and then go to the Joggler configuration page and configure Joggle. See http://pandora.comerge.net/joggler/
Regards
Benno
Looks like your api key user is not allowed to access toggl. Try this:
What do you see?
Regards
Benno
Hello
Toggl says your API user does not have permission to access https://www.toggl.com/api/v8/time_entries?end_date=2015-04-28T17:21:12-04:00&start_date=2015-03-28T17:21:12-04:00. As said:
Do not use google auth. I don't know why your user does not have access. But there is nothing we can do on our side if Toggl says no.
Regards
Benno
Ok, I think there are various issues here:
To find out who: Joggler will print a debug statement before fetching the time entries for the user. Something like "Loading entries for JIRA user name". To see this statement you have to turn on debug logging for Joggler plugin. In JIRA admin go to Logging&Profiling page and configure a debug log level for package "net.comerge.joggler"
I hope this helps
Regards
Benno
Getting closer.. user mapping and api key issues resolved.
New (maybe last) issue:
There was a problem
- Could not start tracking. Are you a member of the Toggl project PE-4428?
The PE project has been mapped in joggler to a public toggl project... not sure why it's referring to the JIRA story id as a "project"...
Joggler is setup with toggl admin api key as well as user mappings to JIRA and individual user toggl keys.
Also seeing this in the logs:
2015-04-27 17:21:13,969 atlassian-scheduler-quartz1.local_Worker-3 ERROR ServiceRunner [atlassian.scheduler.core.JobLauncher] Scheduled job with ID 'JiraPluginScheduler:Toggl short synchronizer' failed
com.sun.jersey.api.client.UniformInterfaceException: GET https://www.toggl.com/api/v8/time_entries?end_date=2015-04-28T17:21:12-04:00&start_date=2015-03-28T17:21:12-04:00 returned a response status of 403 Forbidden
at com.sun.jersey.api.client.WebResource.handle(WebResource.java:676)
at com.sun.jersey.api.client.WebResource.get(WebResource.java:191)
at ch.simas.jtoggl.JToggl.getTimeEntries(JToggl.java:125)
at net.comerge.joggler.synchronizer.TogglSynchronizer.loadEntries(TogglSynchronizer.java:298)
at net.comerge.joggler.synchronizer.TogglSynchronizer.loadEntries(TogglSynchronizer.java:290)
at net.comerge.joggler.synchronizer.TogglSynchronizer.synchronize(TogglSynchronizer.java:150)
at net.comerge.joggler.synchronizer.TogglSynchronizerJob.execute(TogglSynchronizerJob.java:25)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:130)
at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:91)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80)
at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)
at org.quartz.core.JobRunShell.run(JobRunShell.java:223)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
I get an http 200 response and a pile of json...
[{"id":214663669,"guid":"4be61b98-63fa-4aaa-b696-7c6e0bc1ff15","wid":865247,"pid":9162581,"billable":false,"start":"2015-03-30T13:34:38+00:00","stop":"2015-03-30T14:00:53+00:00","duration":1575,"description":"email","duronly":false,"at":"2015-03-30T14:00:55+00:00","uid":1607257},{"id":214678774,"guid":"1345aeed-e9ef-4799-8db1-a6424570210b","wid":865247,"pid":9162579,"billable":false,"start":"2015-03-30T14:00:57+00:00","stop":"2015-03-30T14:09:06+00:00","duration":489,"description":"standup","duronly":false,"at":"2015-03-30T14:09:08+00:00","uid":1607257},...
I don't understand. I've logged in to toggl, provided your plugin with my toggl api key, done and update and the update has gained visibility to my toggl workspace.
So it's clearly working, somewhat.
Yet, when I open a story, I see an error message that says I don't have permission to log time against the issue...
This feels like it's coming from JIRA not toggl
More data:
refreshed my api key in case there was some glitch from when I was using google auth into toggl. logged in with username and password, got a new key, plugged it into joggler. Nothing's changed. Can still see my toggl workspace from within jira/joggler config, but the job that extract data from toggl into JIRA is not working. See log below.
As a test, I also looked at the toggl api docs and ran a curl test on my JIRA server.
curl -v -u <my_api_token>:api_token -X GET https://www.toggl.com/api/v8/me
And this worked just fine. So it's not a communications issue, nor is it an api/auth issue.
still seeing the stacktrace in the logs
2015-05-04 13:11:14,122 atlassian-scheduler-quartz1.local_Worker-1 ERROR ServiceRunner [atlassian.scheduler.core.JobLauncher] Scheduled job with ID 'JiraPluginScheduler:Toggl short synchronizer' failedcom.sun.jersey.api.client.UniformInterfaceException: GET https://www.toggl.com/api/v8/time_entries?end_date=2015-05-05T13:11:14-04:00&start_date=2015-04-05T13:11:14-04:00 returned a response status of 403 Forbiddenat com.sun.jersey.api.client.WebResource.handle(WebResource.java:676)at com.sun.jersey.api.client.WebResource.get(WebResource.java:191)at ch.simas.jtoggl.JToggl.getTimeEntries(JToggl.java:125)at net.comerge.joggler.synchronizer.TogglSynchronizer.loadEntries(TogglSynchronizer.java:298)at net.comerge.joggler.synchronizer.TogglSynchronizer.loadEntries(TogglSynchronizer.java:290)at net.comerge.joggler.synchronizer.TogglSynchronizer.synchronize(TogglSynchronizer.java:150)at net.comerge.joggler.synchronizer.TogglSynchronizerJob.execute(TogglSynchronizerJob.java:25)at com.atlassian.sal.jira.scheduling.JiraPluginScheduler$JobDescriptor.runJob(JiraPluginScheduler.java:130)at com.atlassian.sal.jira.scheduling.JiraPluginScheduler.runJob(JiraPluginScheduler.java:91)at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:136)at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:101)at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:80)at com.atlassian.scheduler.quartz1.Quartz1Job.execute(Quartz1Job.java:32)at org.quartz.core.JobRunShell.run(JobRunShell.java:223)at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Also note the start_date above.. I assume it's just truncated in your logging, but the start_date is malformed.
When I try to pull this url from toggl I get a 400 error (not a 403) so I don't think that's "it".
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.
Read moreAtlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!
Find a groupConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.
Start an AUGYou're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.