Jira Todo Sync

1.1.62026-09-06

• One Audit Log entry per sync instead of one per todo. A poll that mirrored fifty Jira 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.1.52026-09-05

• The stored API token is now only ever sent to the Jira site it was saved against. Until this release, an administrator of this extension could ask the panel to test, or list projects from, a different site URL while leaving the token box empty — and the token saved for your real site was sent to that address. Testing another site 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 site URL must be an https:// Jira Cloud address. A cleartext http:// address, or anything that is not a web address at all, is refused rather than quietly accepted — the API token travels in a Basic-auth header on every call, and the same value builds the issue links written into your todos. A site URL you have already saved keeps working untouched; the rule applies to an address 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.
• A new site URL must be an Atlassian Cloud address (….atlassian.net). This connector supports Jira Cloud only, so where the set of valid hosts is known it is checked rather than guessed. If you have it pointed at a Jira Data Center instance, nothing changes — the check applies only to an address entered from now on, and your saved one keeps working and keeps syncing.
• Refused connections now explain themselves in your language instead of showing an internal error code.

1.1.42026-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.1.32026-09-03

• The settings panel says what the Jira account must be able to do, in Jira's own words, in a block that stays on screen whether or not a token is already stored — the next token is usually created long after the first one. It covers the plain API token, the project permissions the account needs, and how assignees are matched.
• A stored token is marked with a «Token stored» tag inside the field itself. Pasting a new value replaces it; leaving the field empty keeps it.

• A refused Jira call now shows Jira's own explanation. These answers used to be relayed as 502, which a proxy in front of Turbo EA replaces with its own error page — so the reason never reached the browser. It is now relayed intact and written to the sync log.

1.1.22026-09-02

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

1.1.12026-08-26

• The extension carries its own logo, so it is recognisable on the Store and Installed tabs.

1.1.02026-08-20

• Settings moved to Admin → Settings → Integrations, next to the built-in ServiceNow integration, rather than sitting on the Extensions page. It is where an administrator looks for a connection to another system.

1.0.42026-08-11

• Timing diagnostics on the settings routes, so a slow panel can be explained rather than guessed at.

1.0.32026-08-11

• Saving the settings is one write instead of ten. Each field used to be stored separately, which made a save on a distant database take seconds.

1.0.22026-08-11

• Assignee matching survives Jira's email privacy setting, which hides the address the match used to depend on. Configuration is also cached, so the panel opens without a round trip per field.

1.0.12026-08-11

• First-run reports from the field: the token instructions, the project picker, assignee mapping and the panel's latency.

1.0.02026-08-10

• First release. Two-way sync between Turbo EA todos and Jira Cloud issues: a todo becomes an issue, its status follows in both directions, and assignees are matched server-side by email. Turbo EA's own sign-off todos are mirrored read-only — a sign-off can be referenced in Jira but never performed there.