HELP HELP HELP: there is something seriously wrong with AP (connect javascript API)

There are reports in the Atlassian vendor community that there are issues with AP.context.getToken() and AP.context.getContext() which is breaking vendor cloud apps, but there is no escalation path for vendors to contact Atlassian.

Just tagging anyone who might be able to help here
@mike-scriptlover @peter.vandevoorde @dmeyer @jgaard

11 Likes

Applying licenses to instances is also broken. We are affected by this, raised a P1 DEVHELP ticket and didn’t get a response within an hour.

https://ecosystem.atlassian.net/browse/ACJS-1104
https://ecosystem.atlassian.net/browse/ACJS-1103

1 Like

It’s been escalated internally. As soon as there are comms/updates they’ll be posted here.

3 Likes

Update:

From 12:30 pm 21 May Tuesday UTC, we experienced an issue with multiple connect apps on Jira Cloud. We continue to work on resolving the issue. We have identified the root cause and expect recovery shortly.

Posted to https://developer.status.atlassian.com/ as well.

2 Likes

And https://jira-software.status.atlassian.com

Fix has been rolled out to all Jira Cloud customers. Update:

Between 11:44am 21 May UTC to 2:21pm 21 May UTC, we experienced issues with multiple connect apps. The issue has been resolved and the service is now operating normally.

Thanks for the update @nmansilla. Can we think of a way to escalate these kinds of things more swiftly?

3 Likes