GitLab Todo Sync

1.0.92026-09-06

• One Audit Log entry per sync instead of one per todo. A poll that mirrored fifty GitLab issues used to leave fifty entries in Admin → Audit log, each with its own Rollback; the whole cycle is now one entry, and one Rollback undoes every todo the cycle created and is still open — todos people have completed stay. A cycle that found nothing to change leaves no entry at all. This release needs Turbo EA 2.131.0 or newer.

1.0.82026-09-05

• The stored access token is now only ever sent to the GitLab instance it was saved against. Until this release, an administrator of this extension could ask the panel to test, or list projects from, a different instance URL while leaving the token box empty — and the token saved for your real instance was sent to that address. Testing another instance now asks you to paste the token for it, which is the token you would need anyway. Nothing changes for normal use: re-testing your saved connection with the token box empty works exactly as before.
• The instance URL must now be https://. A self-managed instance without TLS is still supported — a new «Allow a cleartext http:// instance URL» switch appears under the URL field as soon as you type an http:// address, and spells out that the token then travels in clear text on every call. An instance URL you have already saved keeps working untouched, whether or not it uses TLS; the switch only governs a URL you enter from now on.
• The Turbo EA address used for todo links is now checked too. It is written into each synced todo as a clickable link, so a value that is not an http:// or https:// address is refused instead of being stored and rendered.
• Refused connections now explain themselves in your language instead of showing an internal error code.

1.0.72026-09-05

• This extension now ships a changelog. Every release from here on documents what changed for you in this file, and it travels inside the signed bundle so it is on disk wherever the extension is installed.

1.0.62026-09-03

• The settings panel says what the GitLab token must be able to do, in GitLab's own words, with the exact click-path for a fine-grained token (including the User-tab Project → Read that fills the project dropdown) and the legacy api scope as the alternative. The block stays on screen whether or not a token is stored.
• A stored token is marked with a «Token stored» tag inside the field itself.

• The project field takes what you typed, without pressing Enter. A typed project used to be discarded silently on save.
• A refused GitLab call now shows GitLab's own explanation instead of a bare error, and the line is written to the sync log. A missing optional permission is a hint, not a warning.

1.0.52026-09-03

• The extension carries its own logo and store listing, ready to install from the Store.

1.0.42026-09-02

• Picking a value from a settings dropdown no longer blanks the field and breaks the save.

1.0.22026-09-02

• Dates render in the workspace date format set in Admin → Settings, rather than the browser's.

1.0.12026-08-20

• Settings moved to Admin → Settings → Integrations, next to the built-in ServiceNow integration, rather than sitting on the Extensions page.
• Realigned with GitLab's generally-available fine-grained token catalogue.

1.0.02026-08-19

• First release. Two-way sync between Turbo EA todos and GitLab issues, built for GitLab's fine-grained tokens rather than the legacy api scope. Turbo EA's own sign-off todos are mirrored read-only — a sign-off can be referenced in GitLab but never performed there.