Update - We are gathering additional information from affected users - to date we have not found a root cause for the problem.
May 05, 2023 - 22:46 UTC
Investigating - We have identified a problem with Jira REST API where endpoint /rest/api/2/issue/{issueIdOrKey} returns media IDs instead of filenames for the attachments. We are investigating the root cause.
May 05, 2023 - 20:30 UTC
Completed -
The scheduled maintenance has been completed.
May 22, 16:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 09:30 UTC
Scheduled -
We are in the process of enabling higher user tiers (Upto 50k) for Confluence apps on Atlassian Marketplace. We request you not to make any pricing changes to the apps during this window as the pricing updates made during this time window might be lost.
Maintenance window : 09:30 AM UTC - 4:00 PM UTC
May 22, 05:29 UTC
Resolved -
Between Feb 3rd and May 11th the value of localId parameter passed via productContext to Forge Jira Issue Panel extension points is incorrect. This may impact, in some cases, the ability to persist data against this parameter in case of Apps using multiple issue panels on a single issue.
The issue has been resolved for all affected apps. If you experience any further problems please contact Developer and Marketplace support (https://developer.atlassian.com/support).
May 22, 13:11 UTC
Update -
We are continuing to monitor for any further issues.
May 22, 13:03 UTC
Monitoring -
Since Feb 3rd the value of localId parameter passed via productContext to Forge Jira Issue Panel extension points is incorrect. This may impact, in some cases, the ability to persist data against this parameter in case of Apps using multiple issue panels on a single issue.
The fix has been implemented and enabled for every new app, thus preventing the issue from spreading further. As mentioned in the previous update, the existing app installations will continue to receive an incorrect value. Affected partners will be contacted directly after the Easter break.
Apr 7, 10:10 UTC
Identified -
Since Feb 3rd the value of localId parameter via productContext to Forge Jira Issue Panel extension points is incorrect.
The value of localId parameter is incorrectly equal to extensionId parameter for Forge Jira Issue Panels. This may impact the ability to persist data against this parameter in case of multiple issue panels on single issue (when 'allowMultiple' configuration parameter is set to 'true').
Team is working on fix that would bring back the correct value of localId parameter for _new_ app installations. The existing app installations will continue to receive incorrect value and the team will work on mitigation steps in coming days. This may require updates to app code that will be described exhaustively in following communication.
This fix shouldn't cause any impact on Forge apps that are using Forge Jira Issue Panels without "allowMultiple" set to true.
We will provide another update by 2023-04-07 8:00 UTC, in 17 hours from now.
Apr 6, 15:18 UTC
Investigating -
Since Feb 3rd the value of localId parameter via productContext to Forge Jira Issue Panel extension points is incorrect.
The value of localId parameter is incorrectly equal to extensionId parameter for Forge Jira Issue Panels. This may impact the ability to persist data against this parameter in case of multiple issue panels on single issue (when 'allowMultiple' configuration parameter is set to 'true').
Apr 6, 15:18 UTC
Resolved -
This incident has now been resolved, we have verified the flow of invoices, we will be closing this incident.
May 19, 05:55 UTC
Identified -
Invoices created after May-19 19:50 UTC are delayed for the all the partners, we have identified the root cause for this issue, we are currently working on the fix, we will have the next update on this issue in 4 hours.
May 19, 04:00 UTC
Resolved -
Between 19:52 UTC to 00:44 UTC, Forge app developers using the Forge CLI were unable to create a Forge tunnel. The issue has been resolved and the service is now operating normally.
May 18, 01:38 UTC
Monitoring -
We have updated a supporting docker image for the Forge CLI tunnel functionality to resolve the problem with the ngrok version. This will be picked up automatically by the Forge CLI when a tunnel is created by a developer. No action is required by developers.
We are now monitoring closely.
May 18, 00:49 UTC
Identified -
We continue to work on resolving the problem with the Forge CLI support for Forge Tunnel.
We have identified the root cause and working on releasing a new version.
The issue was triggered by removal of support by ngrok for the version used in the Forge tunnel. This commenced at 2023-05-18 19:52 UTC
May 18, 00:29 UTC
Investigating -
The Forge CLI is currently unable to create a Forge tunnel, affecting Forge developers. Customer app users are unaffected. Forge developers can deploy their app without using the tunnel.
We are working on a fix for this issue and will release an updated ForgeCLI component
May 17, 23:33 UTC
Resolved -
This incident has been resolved.
May 17, 04:14 UTC
Monitoring -
The issue been fixed and the install events analytics for the coming week will be correct. We continue to monitor the issue.
May 16, 09:56 UTC
Identified -
Hi Partners, We have identified an issue affecting the active install counts for a few accounts, the root cause investigation is underway, in the meanwhile the marketplace team is implementing a temporary fix, we will keep you updated on the status of the issue.
May 16, 07:21 UTC