Changelog

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.

Added Jira Service Management portal request create property panel module, which enables apps to save arbitrary data during request creation as Jira issue properties.

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

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.

The Jira Service Management get customers API which was limited to agents or admin accounts to return a list of customers on a service desk can now be accessed by customer accounts.

The results for the API would follow the project’s customer sharing settings.

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 deprecated AP.host.getSelectedText in Jira and Confluence on Jan 11, 2022, due to security and privacy concerns.

Removal of this API has begun and is rolling out across all cloud instances.

To cause minimum disruption, all calls to this API will now return an empty string ("").

For full details, see the CDAC post.

For public portals, the get request type by Id API now supports anonymous accounts to return customer request types.

The documentation now contains a getting started tutorial for Jira Service Management. The tutorial takes you through adding a page to a Jira Service Management Queues section to display the number of queues in the project.

See Build a Jira Service Management hello world app to work through the tutorial.

Forge CLI now lints correct scope when Jira Software and Jira Service Management REST APIs are used.

The scope checks are based on the OpenAPI specifications:

• Jira Service Management: https://developer.atlassian.com/cloud/jira/service-desk/swagger.v3.json

• Jira Software: https://developer.atlassian.com/cloud/jira/software/swagger.v3.json

We've updated the Forge CLI to align the experience of upgrading and uninstalling JSM apps for classic or granular scopes. Now, for JSM Forge apps, the Forge CLI does not show JSM as an option when you upgrade and uninstall the app. When the apps are installed, upgraded, or uninstalled in Jira the changes are reflected in JSM.

For more information on classic or granular scopes, see the Jira or JSM Scopes for OAuth 2.0 (3LO) and Forge apps pages.

We’ve introduced a new optional query parameter strictConflictStatusCode for the Create Customer REST API in Jira Service Management Cloud. The parameter allows you to receive a 409 Conflict status code for a duplicate customer creation request, instead of a 400 Bad_Request.