Jira: Reconnect Instantly, Connect More Reliably

This release makes the Jira integration easier to fix when it breaks, and more reliable to set up in the first place, especially for teams connecting with an Atlassian service account.

Improvements

Reconnect without disconnecting first

If your API token expires or your credentials change, you can now fix a broken Jira integration directly from the setup form. Come back to the Jira Integration page, re-enter a fresh token, and save. Your existing integration updates in place, so you no longer need to disconnect and reconnect from scratch.

Cloud / Server & Data Center toggle

The connect form now has an explicit Instance Type toggle instead of assuming Jira Cloud. Selecting Server / Data Center adjusts the form accordingly, asking for a username instead of an email, and the API token hint updates to point you at the right place to generate one: the Atlassian admin console for service accounts, id.atlassian.com for regular Cloud accounts, or your Server instance's Personal Access Token page.

Clearer errors when setup or sync fails

If Jira projects can't be loaded after connecting, you'll now see a clear message telling you to reconnect with a fresh token, instead of a stale project list or a failure with no explanation.

Reliability Improvements

Service account connections now work reliably

Atlassian service accounts were sometimes rejected during setup with a generic "Invalid Jira credentials" error, even when the credentials were valid. This is now fixed, and service accounts connect successfully.

Setup no longer hangs on a slow Jira response

If your Jira instance is slow to respond during setup, you'll now get a clear error quickly instead of a page that stays stuck loading.