Jira Cloud adds support for the project settings page module. This module adds an item to the project settings sidebar. When the item is clicked, content is rendered on a new Jira page. Use the UI kit or custom UI to create content for the Jira page.

This module can be used in Jira Core, Jira Software, and Jira Service Management.

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

Jira Cloud adds support for a global page module. This module adds an item in the Apps section of the main navigation. When the menu item is selected, content is rendered on a new Jira page. Use the UI kit or custom UI to create content for the page.

This module can be used in Jira Core, Jira Software, and Jira Service Management.

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

We’ve added documentation about:

• detection of any rotating refresh tokens being reused

• the absolute lifetime, inactivity lifetime, and leeway of rotating refresh tokens

• implications of migrating to rotating refresh tokens and rolling back to persistent refresh tokens

• possible causes of and debugging the 403 Forbidden (invalid_grant) error

We're deprecating the epic link, parent link, epic, and other related fields and events in the Jira REST API and webhooks. They will be removed from the REST API and webhooks on 31 May 2022.

The scope of this change is the Jira REST API and webhooks only. The deprecation does not apply to these fields in Jira UI.

For a breakdown of the affected operations and webhooks, see the announcement in the Developer Community.

The field and query param contextId in the Issue custom field configuration (apps) operation is deprecated and replaced with:

• id, the ID of the configuration entry, which behaves in the same way as the deprecated contextId. Note, this is not the ID of the field context the configuration is associated with, contrary to the previous name.

• fieldContextId, a reference to the field context ID the configuration is associated with.

The reason for this change is that while contextId was intended to be a reference to a field context ID, in some cases it wasn't. fieldContextId serves this purpose now.

The straightforward way of updating your app is to replace contextId with id, making everything work the same as before. However, do check whether fieldContextId is the field that you should use instead.

The contextId field and query param will be removed on 1 March 2022.

We previously announced the deprecation date of persistent refresh tokens as 30 November 2021.

We’ve updated this deprecation date to be 31 January 2022 instead.

Issue data clean up is now done asynchronously while the option remains being deleted synchronously. Overall, it should have no impact to the consumers of the API.

The ability to pass custom context variables in requests to evaluate Jira expressions in the REST API has been added.

See the Evaluate Jira expression operation documentation for more details.

The following Jira modules can now access their issue’s typeId:

• Jira custom field

• Jira issue action

• Jira issue activity

• Jira issue glance

• Jira issue panel

We’re updating the way in which avatars, attachments, and attachment thumbnails are referenced in response objects. These items will be represented by URIs for the appropriate REST API operation, rather than using non-REST URIs. These changes are to ensure that the appropriate OAuth scope checks are made when these objects are requested.

We expect all the affected operations to reach all production instances by January 14, 2022.

See the announcement for more details.

We’ve updated the leeway or reuse detection interval of rotating refresh tokens, from three seconds to 10 minutes.

You can now migrate your Connect app listing and installations to Forge. Navigate to the management view of your Marketplace listing, then select a Forge app with a matching app.connect.key as the new version.

Admins of sites that use your app’s Connect version will be prompted to update to the Forge version (in the “Manage Apps” screen). When they accept, the installation will be replaced by the Forge version.

You can request a staged rollout of the upgrade by raising a Marketplace support ticket listing which sites see the upgrade.

See Migrate an app from Connect to Forge for more information on how to migrate your app (including known issues and limitations with doing so). Then, see Listing a Forge successor to a Connect app for information on how to update your listing with a migrated app.

The comment_created webhook now has a new field eventType which conveys the source of the event. The field can have three values

• partOfIssueChange: The comment was added as part of editing an issue field.

• partOfWorkflowEvent: The comment was added as part of a workflow transition.

• primaryAction: The comment was added as the main action.

Use this field to ignore any webhook events based on how the comment was created. For example, you can ignore any events with partOfIssueChange event type if the comments added as part of the Issue edit screen are unnecessary. Similarly, you can use partOfWorkflowEvent event type to ignore comments added as part of the Workflow transition screen.

Introduction of the Update custom fields operation to update the value of one or more custom fields on one or more issues. Custom fields can only be updated by the Forge app that created them.

See REST API documentation for more details.

As the new Jira Cloud experience rolls out, several locations for providing content in the Jira Cloud user interface have evolved and been replaced with new APIs. The items removed are the project tab panels, profile tab panels, and project admin summary panels.

See Removal of web fragment locations in new Jira Cloud experience for more detail.