Last updated Feb 7, 2025

Changelog

This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Cloud Platform.

Forge changelog

For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.

Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.

7 February 2025

Deprecation Notice Deprecating usage information expands in workflow, status, and workflow scheme APIs

From Jul 7, 2025, we'll remove the ability to use the expands query parameter for fetching associated projects, workflows, issue types, and schemes in several Jira Cloud APIs. This change is necessary due to the absence of pagination, which can lead to scaling and reliability challenges on larger sites. On these sites, workflows, statuses, and schemes can be extensively interconnected, with numerous projects and issue types.

Once the removal comes into effect, we'll ignore the expands queries for this data and stop returning usage information in these APIs.

Affected APIs and parameters

Workflows:

  • Bulk get workflows: The ability to use the workflows.usages and statuses.usages expands will be deprecated.

  • Bulk create workflows: Usage information will no longer be included in responses.

  • Bulk update workflows: Usage information will no longer be included in responses.

Statuses:

  • Bulk get statuses: The usages and workflowUsages expands will be deprecated.

  • Search statuses paginated: The usages and workflowUsages expands will be deprecated.

  • Bulk create status: The usage and workflowUsages fields will no longer be returned.

Workflow schemes:

  • Bulk get workflow schemes: The workflows.usages parameter will be deprecated.

You may need to update your app as a result of this change - see the more details section.

More details

What you need to do

Migrate to the new usage APIs announced as part of CHANGE-2292.

5 February 2025

Added Minor updates for apps adopting Forge from Connect is now available in Preview for Jira

Until now, the first version of an app to adopt Forge features or migrate fully to Forge required admin approval in order to be upgraded on an existing installation site.

Connect apps moving to Forge can opt-in to have their existing Connect installations updated to their latest Forge version, as long as they do not have an elevation in permissions. The rollout will be staggered over 96 hours by default, but can be further staggered via the staged migration process.

Instructions on how to opt your app in to this feature and check its eligibility can be found at Minor version updates (Connect to Forge) (Preview).

4 February 2025

Announcement Rovo agent modules are now generally available (GA)

The Rovo agent and action modules are now generally available.

Get started with the Build a Rovo Agent hello world app tutorial.

3 February 2025

Announcement New Jira Cloud module: `jira:command`

Jira Cloud now offers support for the jira:command module. This module allows apps to add items to the command palette. Users can also navigate to app-defined pages (such as jira:globalPage modules) or open custom modals. For more information, see the module documentation.

30 January 2025

Announcement Connect and Forge apps will be supported in the new workflow editor for company-managed projects

Rollout : progressive rollout by tenant in progress.

We are rolling out support for Connect rules (condition, validator, post function) and Forge rules (condition, validator, post function) in the new workflow editor for company-managed projects through a progressive rollout by tenant, starting in early February 2025.

Connect and Forge rules for the new workflow editor have already been enabled for all tenants in the Developer Canary Program.

Once app support for the new workflow editor is enabled, we expect apps using the documented workflow rule APIs to work without the need for changes:

  • All Marketplace workflow rules configured in the old workflow editor will automatically appear and become configurable in the new workflow editor.

  • Users will be able to create and configure Marketplace workflow rules in the new editor from scratch for company-managed workflows.

  • Workflows and workflow rules will continue to be editable in the old workflow editor.

More details

Marketplace rules in the new editor

The new workflow editor is a new experience that is already available to Jira Admins as an alternative to the old editor. Jira Admins can switch between the new and old editors, as well as change the default editor experience for company-managed projects.

Unlike the old editor, the new one previously did not support Marketplace workflow rules. With this change, Marketplace rules can now be added, viewed, and configured using the new workflow editor.

Workflow drafts

The new workflow editor doesn’t use drafts. Edits are made to the active workflow, changes are built up in the editing session and published with the update action.

The configuration in the context provided to marketplace rules will reflect pending changes. They won’t however be reflected in drafts. If your apps are reliant on drafts, some changes may be needed.

Additional Editor Context

We’ve extended existing APIs to allow vendor rules to determine if the new workflow editor is being used.

For Connect

The callback passed to the getWorkflowConfiguration will receive the config as the first argument and a context object as a second argument in the new editor. The second argument will remain undefined in the legacy workflow editor.

1 2 3 jira.getWorkflowConfiguration( (config, context) => { const isNewEditor = typeof context !== 'undefined'; } );

For Forge

An additional extension.isNewEditor key is set as true in the context object returned from the getContext API in the custom UI bridge. This key will continue to be unset in the legacy workflow editor.

1 2 const context = await view.getContext(); const isNewEditor = context.extension.isNewEditor || false;

Scope and timeline

This change will be shipped for company-managed projects only. Marketplace rules for team-managed projects will be supported later, with more details to be shared in a separate announcement once available.

The long-term goal is to migrate all users to the new workflow editor once feature parity between the old and new workflow editors has been achieved. The old workflow editor will eventually be disabled. The timeline for this is not finalised yet, but it will happen no earlier than December 2025.

Added New Jira status, workflow, and workflow scheme usage REST APIs

We've added a number of new APIs that can be used to find out what is using statuses, workflows, and workflow schemes. They allow you to page through the following:

These APIs will replace the usage expands in the workflow, status and workflow scheme APIs, so look for an upcoming deprecation notice shortly. When these deprecations happen, they’ll adhere to our deprecation policy.

28 January 2025

Deprecation Notice Third-party package mirrors will no longer be available

We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com

More details

We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.

For details on how this change affects you and for guidance on migration, please refer to the documentation available on Atlassian Developer .

Announcement UIM onError handling for unregistered fields

The UI modifications (UIM) error handling method now supports a new error type - unregistered field.

The complete list of error types is available here.

21 January 2025

Announcement Project/Fields Association Improvements for team-managed projects

We are shipping a new page that allows project admins to manage the fields associated in each of their team-managed projects.

Affected APIs

The following APIs providing the fields parameter will be affected, with all and navigable field sets being narrowed down to only those fields that are explicitly added to the project.

Similar changes will be applied to webhooks, with the issue data that is sent by the webhook limited to the fields explicitly added to the project.

When these changes are rolled out, your app will need to:

  • Be able to handle receiving a partial list of fields that can differ between projects and between project/issue-types depending on the custom fields the admin has configured for each project and issue type

  • Be prepared for an admin potentially removing access to a required custom field from a project or project+issue type in which the app is used, at any time

This change will be rolled out progressively late February 2025 onwards. Please leave any further comments on https://community.developer.atlassian.com/t/rfc-70-project-fields-association-improvements-for-team-managed-projects/85254.

Added New Jira workflows REST API: search workflows

The new Search Workflows API allows you to search for workflows in both Company-managed and Team-managed projects. The new API accepts the same request parameters as Get workflows paginated, with the addition of a new scope parameter, allowing you to now specify the scope of the requested workflows.

More details

To use the new functionality, invoke the following with your desired search criteria:
GET /rest/api/2/workflows/search

To request that only results for Company-managed projects are returned, specify a scope of GLOBAL. To request only results for Team-managed projects, specify a scope of PROJECT.

Find more information, see the Search workflows API.

13 January 2025

Announcement New Jira Forge product event for configuration change

We’re happy to introduce a new Jira Forge product event:

  • configuration changed - avi:jira:changed:configuration

Follow the link to read more about it.

7 January 2025

Announcement Taking the Ecosystem Forward: An Update on the Future of Connect

Today we published a blog titled Taking the Ecosystem Forward: An Update on the Future of Connect, which shares an early look at plans to phase out support for Connect. This early announcement is intended for owners of business critical Connect apps, including partners and customers with custom apps, to provide ample time to explore requirements and arrive at a fair timeline for end of support, together.

We’re seeking your feedback to help us shape the next steps for Connect - you can provide your feedback via the survey linked in the blog post.

More details

The blog post details the key stages of our plan, as we progress on this journey. By the final stage, Connect will enter an end of support state (defined in the blog post), where apps can continue to utilise Connect modules, but do so at their own risk. At this stage, we do not have definitive dates for each of these phases - determining a fair and appropriate end of support date will be a joint effort with our partners and other app builders. The purpose of today’s announcement is to start that conversation.

18 December 2024

Announcement Improvements to JQL functions and the precomputations API

We’re happy to announce several improvements to the JQL Functions module as well as the related precomputations API:

  • New endpoint to fetch precomputations by ID; see the docs to learn more.

  • New param (skipNotFoundPrecomputations) for the Update precomputations endpoint, allowing the request to succeed even if some of the requested precomputations no longer exist.

    • The same endpoint now returns a list of IDs of precomputations that couldn’t be found - notFoundPrecomputationIDs.

  • Apps can now return the storeErrorAsPrecomputation param to store the error message as a precomputation , see https://developer.atlassian.com/cloud/jira/platform/jql-functions/#output.

Request for Comments (RFC) RFC-79: Jira Cloud REST API Endpoints for Plans

17 December 2024

Announcement New Jira Forge modules in Preview

We have added four new Forge modules in Jira, which provide additional extension points for customizing and extending Jira functionality.

The following modules are available in Preview:

Module

Description

Jira backlog action

Adds a menu item to the more actions (•••) menu for the Jira backlog view.

Jira board action

Adds a menu item to the more actions (•••) menu for the Jira board view.

Jira sprint action

Adds a menu item to the actions (•••) menu on a sprint card in the backlog view.

Jira personal settings page

Adds an item to the user's profile menu in the main navigation. When the item is clicked, content is rendered on a new Jira page.

To be able to use the new modules, you must first update the Forge CLI:
npm install -g @forge/cli@latest

These new Forge modules also allow Connect developers to replace equivalent Connect modules. For details on these equivalents, see Connect module equivalents.

Rate this page: