This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
A new RFC is ready to review at https://community.developer.atlassian.com/t/rfc-80-app-migration-multi-transfers/87348
Confluence cloud apps on Atlassian Marketplace now offer up to 150k user tier pricing in line with Confluence cloud. The following new tiers are now available:
50,001-60,000
60,001-70,000
70,001-80,000
80,001-90,000
90,001-100,000
100,001-110,000
110,001-120,000
120,001-130,000
130,001-140,000
140,001-150,000
Action required: Pricing for the new tiers will default to the price for 45,001-50,000 users until Marketplace Partners adjust new per-user pricing for newly added tiers.
Please note that the customer experience changes will not take place until around the second week of January.
Support of the blog_moved Connect webhook has been added to Confluence. It’s triggered when a blog post is moved from one space to another.
In addition to the blog field that represents a moved blog post, the webhook payload contains the originalSpace and the currentSpace fields that represent origin and destination spaces respectively.
Owing to the upcoming holiday season and partner requests, we are providing a final extension for existing apps with unresolved naming violations, relaxing the hard block for Marketplace apps until January 31, 2025.
Partners with open tickets related to app name violations must address these issues by the new deadline. Failure to do so will render their app names non-compliant with Atlassian's brand guidelines. We have been sending reminders and will continue to provide updates and support to help you transition smoothly before the deadline.
Key Updates and Timelines:
Hard Block for Current Apps with Violations:
A hard block for existing app names with violations will take effect on January 31, 2025. All apps must be updated to comply with the guidelines before this date.
Soft Block for Existing Apps:
As of October 29, 2024, a soft block has been in place for existing apps with naming violations. Partners receive warnings during app version or name updates, but updates are not currently blocked.
Hard Block for New Apps:
Effective October 29, 2024, all new apps must comply with updated branding guidelines. Non-compliant app names will not be accepted for approval submissions.
We appreciate your cooperation as we work together to maintain a consistent and fair Marketplace.
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.
We’re pleased to announce that Crowd 6.2.0 is now available. Explore Crowd 6.2.0
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.
As announced in the previous deprecation notice changelog, we are enforcing a size limit on bulk API endpoints when the export_view and/or styled_view content representations are requested through an expansion.
The endpoints will return at most 25 results if these content representations are present.
The environment key is now included in the URLs for the following modules:
Note: You will need to update any bookmarks or saved links to these pages to view your Forge app in the left navigation.
For example, for repoMainMenuPage the URL path is changing per below:
from: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeAppModuleKey}
to: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeEnvironmentKey}/{forgeAppModuleKey}
The page loaded directly with the old URL will no longer have menu items on the left navigation:
To navigate to the new URL:
Select the breadcrumb link (test_repo1 in the screenshot above) to load the repo page.
Select the menu item for the Forge page on the left navigation.
All your apps will now be listed on the left navigation.
This feature will allow Connect apps moving to Forge, and existing Forge apps to offer data residency, realm pinning for remotes.
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"
}
...
}We've introduced the bitbucket:repoPullRequestOverviewPanel Forge module. This module adds an expandable panel on the PR Overview tab to display custom information defined in a Forge App.
This enhancement allows developers to customize the information displayed in pull request overviews, improving the visibility of critical data. For more information, see Bitbucket pull request overview panel.
We are refreshing the @atlaskit/select component for better accessibility!
Over the next year, we will be deprecating props that are unused, used incorrectly, or enabled bad accessibility patterns. Review the upcoming deprecation schedule in the following More details section.
We’ll be immediately marking the following props as deprecated and then removing them over the next few quarters.
aria-errormessage (Does not have broad accessibility support, do not use)
aria-invalid (Use isInvalid instead)
aria-label (Will be replaced with label)
aria-labelledby (Will be replaced with labelId)
aria-describedby (Will be replaced with descriptionId)
aria-live
aria-required (Will be replaced by isRequired)
ariaLiveMessages (Do not use)
captureMenuScroll
delimiter
disabled (Use isDisabled instead)
escapeClearsValue
Will be handled automatically to support expected keyboard accessibility.
isRTL
menuShouldBlockScroll
screenReaderStatus
theme
validationState (UseisInvalid instead)
backspaceRemovesValue
Will be handled automatically to support expected keyboard accessibility.
clearOptionsDisabled
Will be removed to support expected accessibility interactions.
closeMenuOnScroll
Will be removed to support expected accessibility interactions.
controlShouldRenderValue
Will be removed to support expected accessibility interactions.
openMenuOnClick
Will be removed to support expected accessibility interactions.
openMenuOnFocus
Will be removed to support expected accessibility interactions.
tabSelectsValue
Will be handled automatically to support expected keyboard accessibility.
className
classNamePrefix
css
components
formatGroupLabel
formatOptionLabel
getOptionLabel
getOptionValue
hideSelectedOptions
instanceId
shouldFitContainer
style
styles
Rate this page: