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.
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.
We are shipping a new page that allows project admins to manage the fields associated in each of their team-managed projects.
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.
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.
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.
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.
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.
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.
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.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-79-jira-cloud-rest-api-endpoints-for-plans/87236.
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 |
|---|---|
Adds a menu item to the more actions (•••) menu for the Jira backlog view. | |
Adds a menu item to the more actions (•••) menu for the Jira board view. | |
Adds a menu item to the actions (•••) menu on a sprint card in the backlog view. | |
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.
Following the EAP release, UI Kit’s Frame component is now in preview. This means you can use the Frame component in the production environments.
The Frame component allows you to load custom resources within UI Kit, making it easy to import non-UI Kit components in a UI Kit module.
This update also supports Frame across all modules for Jira, Confluence and Compass.
For more information about how to use the Frame component, see here.
To use the latest version of the Frame component in your UI Kit app, install the @forge/react latest version by running npm install --save @forge/react@latest
We will no longer support creating Epic or Sub-task issue links via the create issue link REST API. This change is being made to streamline the API and improve performance.
This change will take effect after 3 months.
We will no longer support creating Epic link or Sub-task issue links via the create issue link REST API.
Developers should use the parent field in the Issue API to create hierarchy relationships between issues.
API Reference: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-links/#api-rest-api-3-issuelink-post
Parent field Reference: https://community.atlassian.com/t5/Jira-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758
Affecting the create issue link API
Stop specifying an Epic or Sub-task link type to the API. Epic or Sub-task link type is specified by setting type.name="Epic-Story Link",type.name="jira_subtask_link"or type.id="{linkTypeId}"where linkTypeIdis the id of the Epic or Sub-task link type.
Once this deprecation is complete, requests that specify these fields will return a HTTP 400 bad request instead of the current HTTP 201 created response.
Note: All other link types will continue to work as-is.
Example payload that will become invalid
1
2
3
4
5
6
7
8
9
10
11
{
"inwardIssue": {
"key": "HSP-1"
},
"outwardIssue": {
"key": "MKY-1"
},
"type": {
"name": "Epic Link"
}
};Instead provide the parent field to the Issue API (https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-group-issues) for issues of all types to create a hierarchy relationship between issues. This is described in the existing notice here: https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048
An exmple new payload would be
1
2
3
4
5
6
7
8
PUT /rest/api/3/issue/10054
"fields": {
...
"parent": {
"id": "10055"
}
...
}You can now migrate existing Connect workflow modules to their Forge counterparts that are currently in Preview, with GA expected on those modules in Q1 2025.
This change allows your app to upgrade its existing Connect workflow modules to Forge modules. When upgrading, ensure that you set the Forge module key to the value of the key of the Connect module so that the Forge module can access existing workflow configuration information.
See Migrate Jira modules from Connect to Forge for more information.
The AdfRenderer component provides a way to render a valid ADF document, using the same renderer that Atlassian uses internally to render ADF content in Confluence pages, Jira work items, and so on. See ADF renderer for the full docs.
The ADF renderer component also allows you to replace node types that are unsupported in the context of a Forge app with replacement content, or remove them entirely.
See Atlassian Document Format for information on valid nodes.
Run npm i @forge/react@latest to install the preview version of the components and try them out now.
We’re happy to introduce two new Jira Forge product events:
Component deleted - avi:jira:deleted:component
Issue type deleted - avi:jira:deleted:issuetype
Follow the links to read more about them.
UI modifications, the Forge module that allows apps to modify fields, now supports the cascading select field on the Global issue create view.
For more information, see the list of supported fields for Global issue create.
We have now removed the UI Kit @forge/react version 9 from the Forge platform. This UI Kit version was deprecated on Aug 28, 2024.
We recommend using the latest version of UI Kit (@forge/react10).
For more information, see our deprecation policy.
Rate this page: