On Monday August 31, 2026 Atlassian unexpectedly shipped breaking changes to Jira OAuth integrations. This made it impossible for any new users to add the Jira integration. Atlassian did not provide any way for us to edit our current integration configuration to be compliant with the breaking changes effectively stranding our current integration. We can't be certain what they broke since the changes are opaque to us but there were two issues we identified.
(1) Atlassian apps now use granular scopes, many of our test apps were automatically migrated but not the main one customers interact with. Unfortunately, the ability to transition to granular scopes existed no where in their developer portal which stranded us.
(2) Atlassian created a new flag for all integrations which decides whether permissions are granted for all the sites under your account at once or one site at a time. Our original integration used the old "all sites under the account" setting which was the only option at the time. Atlassian's developer portal made it impossible to swap to the new version when they made that optional - it can only be set exactly once when you create your integration's profile.
We've made many attempts to reach out to their support and senior leadership but heard nothing back about getting our integration transitioned. Instead of continuing to wait, we decided to pull the trigger and publish a brand new version of our Jira OAuth app.
This means all existing users of our Jira integration will need to perform a one time re-authorization.
There's a screen that will walk you through it:
Once you perform the re-auth all tasks you had linked to Jira reconnect. Until you do this reconnection, they'll show as "not found".
We're extremely sorry about this extra step but Atlassian left us no choice. The silver lining for existing users, our Jira integration now uses the most modern scopes and a much safer one-site-at-a-time authorization system making it easier to control what access Sunsama gets.