Joggler says no permission?

[Operations Group]

Screen Shot 2015-04-27 at 2.04.18 PM.png

Where do I grant permissions?

Screen Shot 2015-04-27 at 2.04.18 PM.png ‏16 KB

[Benno Baumgartner]

Hi

Turn off all the project tracking issue types on the toggl configuration page. Otherwise it thinks there is a toggl project for each story.

Regards

Benno

[Benno Baumgartner]

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

[Benno Baumgartner]

Looks like your api key user is not allowed to access toggl. Try this:

• Login to the toggl web ui in your browser using username/password of the api key user
• Then open 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 in another browser tab

What do you see?

Regards

Benno

[Benno Baumgartner]

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:

• Login to the toggl web ui in your browser using username/password of the api key user

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

[Benno Baumgartner]

Ok, I think there are various issues here:

1. You see the "You do not have permission to time track" because you have not defined a user mapping for yourself
2. You are getting the permission error on synchronize because one of your users has provided a faulty API Token I assume.

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

[Operations Group]

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"... 

[Operations Group]

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)

[Operations Group]

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},...

[Operations Group]

perhaps worth noting: I'm using google auth to connect... not sure if that may matter, but more data...

[Operations Group]

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

[Operations Group]

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 'Jira

PluginScheduler:Toggl short synchronizer' failed

com.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-05T1

3:11:14-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)

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".