fyyyyy / toggl-to-jira-chrome-extension Goto Github PK

Header URLs are hardcoded in background.js
Should also be loaded from the chrome storage.

I did notice another small bug.

I get this error whenever I try to record a time less than 1 minute

Originally posted by @ThatGuySam in #10 (comment)

First off, thanks for building this for free so I don't have to pay $10/month to some random software company on the internet.

I'm getting the following error

MacOS Mojave 10.14.2
Chrome 71.0.3578.98
Toggle Chrome Plugin 1.19.1

I'm not really sure what else context you may need.

All worklogs are one hour of (one hour too early). Could this be a timezone mismatch?

I believe that API has changed and is not accepting the authentication.

The extensions is causing the XHR requests to be blocked by CORS policy on toggl site, due to this u can't login on https://toggl.com/track/login/

There is a warning message at the bottom of the popup: "Logging repeatedly will add new time logs for the same JIRA task, instead of overwriting the old log. So log only once per Toggl entry."

Is this still valid? From the code and my usage it looks like you'd always be prevented from being able to log anything twice since it checks the Jira work entries and matches them against the toggl entries?

I think we should remove this message, but wanted to make sure I wasn't missing something first!

As i mentioned on Chrome Web Store, the plugin is not working.

I checked the console logs and it seems that the Toggl api is returning 403.

I do not know if this is related to the plugin it self, or to Toggl api.

Just got an email from Toggl saying I'm using https://www.toggl.com/api and I should now be using https://api.track.toggl.com/api as https://www.toggl.com/api will be dropped after 'June 30th 2021'.
Checked the code and reproduced the requests the extension does in Postman with the new domain and they seem to work fine.
Can you please update the URLs?

When you go to https://www.toggl.com/login and use Google sign-in, you get redirected to https://toggl.com/app, notice the lack of www.. In https://github.com/fyyyyy/Toggl-to-Jira-Chrome-Extension/blob/master/parser.js#L193 there is a hardcoded https://www.toggl.com/api/v8/time_entries URL. Because you don't have the required cookie for www.toggl.com domain, you get 403 from the API and the extension doesn't work as expected.

Workaround I found is to set the account password by resetting your Toggl password and use it to log in. Would be great if the extension handled this case, though. The easiest to implement (not so great UX) would be to make the Toggl host configurable.

From my understanding, currently the extension takes the first word of the Toggl time entry description and checks on JIRA if an item with that key exists. then adds the toggl time entry as a worklog.

Could an option be added so that when activated the plugin would use the rest of the Toggl description as the worklog comment for the JIRA issue?

Example:
I have a toggl entry that look like this
LOM-951 Add dropdown menu to element on site

Currently the extension takes the "LOM-951" and searches for the item on JIRA. If it finds the items it adds the tracked time with the comment that is set in the extension options.
My proposal is to enable the extension to use the rest of the description.
So in this case: "Add dropdown menu to element on site", and to use that as the comment for that issue when logging the worklog in JIRA.
This would enable me to add meaningful comments to the worklog on Jira by editing the Toggl time entries.

Unfortunately I am not familiar with javascript and extension developing to propose a technical solution for this. But maybe somebody could add this.

Thanks.

The app has not been working for me for some weeks now. I'm getting a 403 when calling https://www.toggl.com/api/v8/time_entries?start_date=2020-01-01T00:00:00.000Z&end_date=2020-01-31T00:00:00.000Z. I had this error in the past, but logging out and logging back in at the Toggl website solved it. Now, that quick fix doesn't work anymore.
I've noticed that the Toggl website is now using the v9 API and this app still uses the v8. Can this be the issue?

Yesterday I got an email from Toggl saying that they will shut down their v8 API on May 23rd and that I need to migrate to v9. I checked the source code of this project and it uses v8 as I was suspecting.
This means that this extension will stop working in less than a month if the migration is not done in time.
Here are the URLs they sent in the email with the documentation for the migration process:

• https://engineering.toggl.com/changes/2022/10/01/api-v8-deprecation/index.html
• https://engineering.toggl.com/docs/additional/v8_migration_guide/index.html

From what I've seen in the source code, the changes seem to be simple. I'll try to create a PR with them.

404 on the https://chrome.google.com/webstore/detail/toggl-to-jira/anbbcnldaagfjlhbfddpjlndmjcgkdpf

installed, added our jira server url, without trailing slash, nothing happens when i try to load entries.
tried with and without inputting a end date.
no console errors, no network requests.
what should i be looking for?

chrome: Version 62.0.3202.94 (Official Build) (64-bit)
Toggl to Jira 2.0.5

i'm so this doesn't work right now :(