Investigating disruption to Atlassian Service used in Portfolio Forecaster for Jira Cloud

Incident Report for 55 Degrees

Resolved

Based on our monitoring, the issue appears to be resolved and forecast generation is now functioning normally. If you’re still experiencing any problems, please reach out to support@55degrees.se.
Posted Jun 05, 2025 - 01:54 CEST

Monitoring

We have released the updated version of the app that calls the new API and have validated that all features are working. We'll be re-evaluating our process of monitoring API lifecycles from Atlassian in order to avoid any emergent issues in the future. We thank everyone for their patience.
Posted Jun 04, 2025 - 16:04 CEST

Update

We are continuing to work on a fix for this issue. We have completed all of the code changes and now are working to verify that everything is working properly before deploying the change to production.
Posted Jun 04, 2025 - 14:20 CEST

Identified

Our engineering team has identified the root cause of the issue (an API in use was deprecated) and is actively working on the code changes needed to resolve the incident. We are treating this as our top priority and we will provide an update in 1 hour or as soon as progress has been made.
Posted Jun 04, 2025 - 12:56 CEST

Investigating

We’re currently experiencing an problem connecting to Atlassian Forge platform when users try to generate new or updated forecasts. This will result in the following error being presented to the user: "Error: Remote could not verify the Forge Invocation Token"

Our development team is working to identify the root cause and implement a solution.

Next update in 1 hour.
Posted Jun 04, 2025 - 11:46 CEST
This incident affected: Portfolio Forecaster for Jira.