simoneldevig / jira-toggl Goto Github PK

Hi,

I’m trying to use this add on and I get error 403 on Firefox Mac and PC. API token and username, jira server are correct.
I get the listing of my projects, ready to import but whenever I press the sync to jira-button, I receive Error 403. So the add on can make the toggl connection but writing into the jira ticket doesn’t work...

Hi

The calendar should remember the selected dates between each openings

Toggl has changed its product names since a while.
https://toggl.com/blog/api-documentation-change

Now, the Toggl track api is located at api.track.toggl.com and www.toggl.com/api is not responding anymore.
This extension needs some adaptation to the new urls: https://github.com/toggl/toggl_api_docs

Hi,
I'm currently trying to get the Browser-Extensions to work properly, and so far it works good.
The only issue I found is, that already synched worklog entries are not marked as logged:
Syncing:

Synced in Jira:

Not marked as logged:

Is someone else have that issue?

Hi,

I'm having a problem with already logged issues that are not marked as logged the next time I use the extension. Does anyone know the reason for that? This leads to duplicate worklogs if I do not check manually which issues are already logged.

API v8 which is being used by this extension is deprecated since Oct 1 2022: developers.track.toggl.com/changes/2022/10/01/api-v8-deprecation

During March 2023 there will be brownouts:

During brownout periods, endpoints will be temporarily disabled and then re-enabled after a few hours. The goal is to help API clients to notice the scheduled unavailability and plan their migration accordingly.

On April 1 2023 the v8 will be disabled and the extension will stop working.

Here is the migration guide: developers.track.toggl.com/docs/additional/v8_migration_guide

Hello

If I select a date range of a week, with many time entries and several Toggl projects, Toggl rejects some api request with a "429 Too many request".

See a screenhost with some rejected requests:

You can also see that more than one api request are made for the same project.

I see too optimizations here:

• introduce a cache for projects: if one project has been fetched, no need to call the api again
• if a request leads to a 429, wait for 500 milliseconds and retry it

Hi,
Times are loaded successfully from toggle and I'm logged in my Jira server, but when I click the "Log work" button I got a network error. and nothing is logged.

Sometimes due to lots of context switching I might log less than a minute, which causes a 400 response from jira when creating the worklog.

Possible solutions, in order of preference:

1. ceil instead of round the time, therefore those entries will be at least one minute.
2. Log the time in seconds instead of rounding it to minutes.
3. Filter out from the popup tasks shorter than one minute.

I will take a look at the code later and decide a solution that works for me. If it's too opinionated, I'll add an option to customize the behavior.

Hi

The first day of the week should be defined in options:

• Week starts on monday
• Week starts on sunday

Hello

In France we have two timezone: summer UTC+2 and winter UTC+1.
I have synced to JIRA time entries in UTC+2, and now we are in winter time, those entries are not marked as synced.

The time comparison should be done in UTC only in order to be timezone agnostic.