Update - Atlassian is working on a fix for this issue, please let us know in case you are affected, Atlassian has the ability to roll back the change temporarily on a case by case basis.
Feb 10, 2026 - 09:20 CET
Update - We are in active contact with Atlassian to get the bug fixed as soon as possible, please refrain from updating your Forms, if possible, until this issue is resolved.
Feb 09, 2026 - 09:07 CET
Identified - We are currently seeing a bug affecting the Atlassian Forms API, regarding to the new conditional section logic. Please refrain from updating Forms until the bug is fixed, otherwise the conditions will not be evaluated correctly in our Microsoft Teams portal app.
Feb 06, 2026 - 09:42 CET
Resolved -
This seems to have resolved itself, although we do not have any any acknowledgement from from Atlassian on the issue. We'll continue to investigate.
Feb 10, 09:19 CET
Monitoring -
We are in touch with Atlassian to resolve this degradation. Customers can see long running board load times with some board running into timeouts.
Feb 6, 09:38 CET
Resolved -
This incident has been resolved on the Microsoft side, chats can now created normally again.
Feb 10, 09:17 CET
Update -
We are continuing to monitor for any further issues.
Feb 9, 09:05 CET
Monitoring -
We are seeing some improvements to this issue but are closely monitoring this. Still awaiting feedback from Microsoft on the issue.
Feb 9, 09:05 CET
Update -
We are continuing to work with Microsoft on the issue and hope to have an update soon. If you see errors when creating chats, please try to create the chat again. It's also possible that the chat is created in Teams, despite an error being shown in Jira.
Feb 6, 09:43 CET
Identified -
We are seeing a re-occurrence of the issue that happened a few weeks ago. We are currently seeing an increased amount of errors in the chat functionality, coming from the Microsoft Graph API. We'll provide an update once we have more information.
Feb 5, 14:02 CET
Resolved -
Yesterday we experienced a full service outage from approximately 8:30 PM CET until 22:45 PM CET, due to a spike in database usage in our main database. We'll do a full investigation and post a post-mortem soon.
Feb 9, 08:30 CET