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.
We've updated our https://developer.atlassian.com/platform/forge/deprecation-policy/ to set clearer expectations regarding the lifecycle of Forge CLI versions. Versions older than 6 months are automatically unsupported and may have unexpected behaviours. We recommend regularly updating to the latest CLI version to benefit from new features and improvements.
We are extending the deprecation period for all endpoints noted in CHANGE-864 and CHANGE-1116 to Dec 2, 2024.
Partners had requested to know which customers are receiving dual licensing support. As part of that, a new field "reason" has been introduced in our APIs to provide insights specifically when discounts are applied due to DUAL_LICENSING. This field is displayed when the discount reason is DUAL_LICENSING.
The newly introduced field information will be accessible through the following Marketplace APIs./vendors/{vendorId}/reporting/sales/transactions/vendors/{vendorId}/reporting/sales/transactions/export/vendors/{vendorId}/reporting/sales/transactions/async/export/{exportId}
Please refer to more details on how the API response and CSV files will reflect this change.
API response with new fields
1
2
3
4
5
6
7
8
9
10
11
"discounts": [
{
"type": "XXX",
"amount": "XXX",
"reason": "DUAL_LICENSING" <-- Reason field shown only if reason is DUAL_LICENSING
},
{
"type": "XXX",
"amount": "XXX" <-- Reason field not shown as reason is not DUAL_LICENSING
}
]CSV response with new columns
We have expanded the transaction csv export file by incorporating four new columns: loyaltyDiscountReason, marketplacePromotionDiscountReason, expertDiscountReason, and manualDiscountReason. If the discount amount is greater than 0 and the reason for the discount is a dual license, these columns will contain DUAL_LICENSING.
loyaltyDiscountAmount | loyaltyDiscountReason | marketplacePromotionDiscountAmount | marketplacePromotionDiscountCode | marketplacePromotionDiscountReason | expertDiscountAmount | expertDiscountReason | manualDiscountAmount | manualDiscountReason |
|---|---|---|---|---|---|---|---|---|
XXX | DUAL LICENSING | XXX |
| DUAL LICENSING | XXX | DUAL LICENSING | XXX | DUAL LICENSING |
We’re introducing new endpoints to the Confluence Cloud REST API v2 for applying and modifying classification levels in spaces, pages and blog posts. How does data classification work?
Classification Levels
Space Default Classification Level
Page Classification Level
Blog Post Classification Level
Make sure that your Power-Up collaborators information is up to date. You can modify collaborators on the Power-Ups admin panel under the ‘Collaborators’ tab.
Going forward, when Atlassian receives communication regarding your public Power-Up, we will create a Jira issue and add every collaborator that is associated with your Power-Up. This will include Workspace admins as well as Workspace members that you added manually. Remember, you and your collaborators already have Atlassian Accounts by virtue of being Trello users.
We want to open up a more reliable method of communication between our security team and Power-Up developers. Currently, we only ask for an email for our contact information, and a Support Contact email/link when the Power-Up is made public. This has created many inefficiencies when it comes to reaching out to developers, specifically regarding security tickets.
Since these emails aren’t necessarily tied to an Atlassian Account, there may not even be a person behind a Power-Up . We can’t reliably tag developers in our Jira tickets, so we don’t have a way to track progress outside of an email chain, and many of our attempts to contact a support email go unanswered.
In effect, we’re asking public Power-Ups to have associated Atlassian Account/s, which will make our third-party security processes faster and more secure.
Thanks for all your efforts making Trello awesome, and thanks in advance for your cooperation!
Our new finance ERP platform, Oracle Fusion, will undergo scheduled periodic updates, causing approximately a 9-hour maintenance downtime that will impact our internal data pipelines. Once the update is completed, our internal data pipelines will resume and it will take about 3 additional hours to reinstate unprocessed transactions in Marketplace reports and APIs.
We anticipate that Marketplace reports and APIs will be affected on the following upcoming date and time.
May 17th 2024 7 p.m PST to May 18th 7 a.m PST
For more details, please refer to this blog: https://atlassianpartners.atlassian.net/wiki/spaces/news/blog/2023/12/21/379453986/Important+Notice+Scheduled+Oracle+Fusion+Maintenance+Impacting+Marketplace+Reports+and+APIs
You can now use the latest version of UI Kit to add configuration to Custom UI macros. Custom UI apps were previously limited to using the UI Kit 1 implementation of macro config.
For more information on adding configuration to the Confluence macros, see the Add configuration to a macro tutorial.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
Run npm install @forge/react@latest on the command line to install the latest version of @forge/react.
Previously, you can download app logs dating up to 60 days from the current date. For compliance and performance reasons, we’re changing this, from 60 days to 30 days.
The Native Node Runtime is now generally available. To use this runtime, specify set your app.runtime.name to nodejs18.x in the manifest file.
As of version 9.0.0 of the @forge/cli, the app.runtime.name field of the manifest file is now required. We recommend that you use the native Node runtime, as this provides several security and performance enhancements, along with greater compatibility with the Node.js ecosystem. See More details for information on choosing a runtime.
forge tunnel for the legacy runtime will require app.runtime.name regardless of the @forge/cli version used. forge tunnel for the legacy runtime always uses the output of forge lint from the latest @forge/cli version.
Some existing apps may need to address breaking changes with the native Node runtime. Forge supports using the legacy runtime while addressing those changes. For more information, see Migrating from the legacy runtime.
We recommend that all apps use the native Node runtime, as the legacy version will eventually be deprecated.
All templates now include app.runtime.name: nodejs18.x. When creating a new app, the CLI will specify this runtime by default.
https://developer.atlassian.com/platform/forge/runtime-reference/external-fetch-api/ is now supported with the latest version of @forge/api.
To use the generally available Native Node Runtime, set app.runtime.name to nodejs18.x in your manifest.yml:
1
2
3
4
app:
id: ari:cloud:ecosystem::app/<unique-identifier>
runtime:
name: nodejs18.xTo continue using the legacy sandbox runtime, set app.runtime.name to sandbox in your manifest.yml instead:
1
2
3
4
app:
id: ari:cloud:ecosystem::app/<unique-identifier>
runtime:
name: sandboxThe first EAP for Jira Software 9.16 and Jira Service Management 5.16 is ready for testing. You can download the EAP from this page. If you’re using maven.atlassian.com, here are the versions: 9.16.0-m0001 for Jira Software and 5.16.0-m0001 for Jira Service Management.
If you want to share your feedback, just leave a reply in the Atlassian Developer Community thread.
We’ve added a set of new query parameters to the v2 Get space by id API endpoint that allows for optional fetching of metadata properties related to the given space. These include:
include-labels
include-operations
include-properties
include-permissions
By default, these metadata properties will not be included in the response unless specified.
You can now secure your Assets imports with the Jira allowlist. This way, you can make sure that your import configurations (such as Object Schema import, LDAP import) get data only from allowed external sources.
To start using this feature:
Make sure that the allowlist in Jira is configured.
Navigate to Jira administration, select Manage apps then Assets configuration.
In the Security section, select Yes for Use the Jira Allowlist to block import configuration URLs.
1: New setting to filter import configuration URLs
To reduce the computational load on your instance, your Workload report now contains additional filters, and is configured by default to show only agents with assigned issues. This will speed up the load time of Workload reports in large Jira Service Management instances and reduce timeouts. Whenever you need to view the workload of all agents, just modify the search filter.
1: New filter to view agents with workload
As we continue to strengthen the security of our products, we’ve made some changes to the Groovy scripts interface in Assets to reduce the risk of arbitrary code execution. From Jira Service Management 5.16, the Groovy script console, which lets you build and execute scripts on the fly, will no longer be available across Assets.
You can continue to use and run Groovy scripts, but you’ll need to store them in a common script directory (located within the shared home directory of Jira) and add the script path for use within workflow transitions and object schema automations. We’ve added a new read-only panel to help you easily verify script content before you use or run scripts. How to use Groovy scripts
This feature is on by default and the change impacts the following:
The console available in Administration (select Manage apps then Assets script console).
The console available in Workflows (conditions, validators, post functions).
The Automation tab in Assets schema configuration.
The Assets allowlist page will no longer be available. However, your existing automations that rely on the scripts you added to the allowlist before this upgrade won’t be affected. The new Groovy scripts page contains a read-only list of these allowlist files.
Any file paths you saved in Workflows will be added to the allowlist during the upgrade.
Any code you added to the console before the upgrade will be available in the read-only panel.
Introducing additions to the Assets archiving experience we released in 5.15. You can now restore archived objects easily from the Archived objects page and take advantage of the new Archive object action in Assets automations. More about archiving objects
What’s new?
Search for objects in the Archived objects page and:
use the new Archived by me filter to search for objects that you’ve archived
restore an archived object directly from this page (select an object and then from the Actions column, select More actions (…) and then Restore)
bulk restore objects (you can either select Restore all to restore all the filtered objects or select the desired objects and then select Restore selected)
Use the new Archive object action in Assets automations. Note the following:
For the action to run successfully, the rule needs to run as a user with manager permissions for the object type.
Each condition can contain only one Archive object action.
As attributes can’t be updated on archived objects, you can’t add an Attribute value action after an Archive object action.
As archived objects can’t be updated, any actions that trigger changes to archived objects will fail. For example, Groovy script or HTTP request actions that attempt to modify objects affected by the Archive object action.
1: New action to archive objects
Rate this page: