The jiraIssueGlances and jira:issueGlance module in Forge and Connect are being deprecated and replaced with the issueContext module on the Oct 6, 2023.

To make it easier and safer to distribute your Forge app via the developer console, you can now generate new installation links. When you generate a new link, users with the previous link will no longer be able to install your app (however, they can still update to new versions). This gives you more control when distributing your app to specific audiences.

In the developer console, you can now edit the target value of your Forge app alert. Previously, the alert was set at a target value of 99%. Now you can choose from a number of values between 99% and 60%.
For more information, see Manage app alerts.

To quickly identify the current state of your Forge apps, the developer console now displays values, as well as charts, for each metric. For more information, see View app metrics.

To help you debug your Forge apps, the developer console now lets you group your metrics by app version. Each chart now has a Group by dropdown menu, with the option to select Version. For more information, see Monitor your apps.

In the developer console, you can now edit the title and description of your app alert, as well as view alert history. You can also see the metrics highlighted when value is below the threshold. For more information, see Manage app alerts.

To help you debug your Forge apps, the developer console now displays site-specific information about your app's invocation errors. Just select the invocation errors chart title, or select the More actions (⋯) menu on the chart and View details.

For more information, see Monitor your apps.

To help you monitor the performance of your Forge app, we’ve introduced alerts for when your app’s invocation success rate changes. If your app’s invocation success rate falls below 99%, we’ll send you an email. If you don’t want to receive these emails, you can mute and unmute the alert at any time.

To help you debug your Forge apps more easily, app logs are now available by default when a user installs your app on their site.

• Previously log access was disabled by default. If you needed log access for your app on a user’s site, you had to ask the user to manually give you log access through Admin Hub.

• Now log access is enabled by default. When a user installs your Forge app on their site, you will now have automatic access to logs for your app on their site.

Note, apps that are already installed will remain in their current state of log sharing, with log access disabled by default, but we are investigating how to change this.

Disabling access

Users can still manually disable or re-enable log access through Admin Hub. This will remove your access to the logs for your app on their site, including any historic logs that were generated when you previously had access.

To help you when handling logs for your Forge app, we have added new Logging guidelines for app developers. These guidelines outline some best practices to consider when handling logs and determining what data you should, and should not, be logging.

We recently launched a new developer support page, which serves as a centralized hub for reporting issues, managing your app and getting support. This page will streamline your experience of getting in contact with us for different areas of support:

• Bugs: Report development or Marketplace bugs

• Incidents: Report critical issues or breaking changes

• App listing: Edit your app or access Marketplace APIs

• Accounts and payment: Manage your Marketplace payments and licenses

• App migration: Get help with creating a cloud version of your app

• Security programs: Apply or adjust your program details

• Partner resources: Request access to exclusive partner content

• Ukraine support: Request emergency concessions or ask questions

If you have any questions, please get in touch with us via the developer community announcement.

To make it easier to track the performance of your shared apps, we’ve added quick-view cards on the developer console landing page, under a new ‘My shared apps’ section. These cards show your shared apps':

• Invocation success rate for the last 7 days

• Error count for the last 7 days

• Last deployment event

We’ve updated the Forge CLI to reflect the changes resulting from pausing the rollout of new scopes. Forge now supports classic and granular scopes. However, if your app doesn’t have all the scopes it needs, the Forge CLI suggests the recommended classic scopes instead of granular scopes.

Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.

We’ve introduced the compass:dataProvider Forge module. This module enables apps to send events and metrics to Compass whenever specific links are added or modified on a component. For example, you could configure the module to send deploymentFrequency metrics to any component with a bitbucket.org repository link.

Learn more about creating a data provider app for events and metrics

We’ve added support for a new compass:teamPage module in Compass. This module adds a menu item in the left navigation of the team page with an entry for this app. When the menu item is selected, content is rendered on a new page. Use the UI kit or custom UI to create content for the page.

Run npm install @forge/ui@latest on the command line in your app directory to install the latest version of the UI kit.