Atlassian: Top 10 cloud changes as of February 2025

What changes did Atlassian make to its cloud products in February? We explain the ten most important changes in our new article.

1. Review of product requirements

For Jira, Jira Service Management and Confluence with Enterprise Plan

Users can submit requests for new products. You can find these product requests created by your users in Atlassian Administration. If you are reviewing a product request, you can contact the users directly from the administration to learn more about their requests. As you process the request, you should update the status of the request depending on where you are in the process so that other administrators can also see the status.

In Jira, Jira Service Management and Confluence, you can update the status at any time.

2. Block download of files - with extended data export rule

Prerequisite: Org Admin role in conjunction with Atlassian Guard Standard

The data export rule allows you to block the export of data in areas and projects, products or classification levels that are protected by a data security policy.

This is useful if you want to prevent people from exporting sensitive data to PDF, XML, CSV and other available formats. The rule blocks the export of pages, blog posts and issues or their attachments.

Blockable in Confluence

• Export page to PDF and Word (*** > Export)
• Export blog to PDF (*** > Export)
• Export space to CSV, HTML, XML, and PDF (Space settings > Content tools > Export)

Blockable in Jira products

• Export single issues to Word and XML (*** > Export)
• Export multiple issues (from filters or queries) to XML, RSS, Word, HTML, CSV, XLSX (Issues > Export issues)

When trying to export data via URL or API, the request will return a "can't export" error.

3. New authorizations

To edit workflows and issue layouts in company-managed projects

Jira administrators can now grant permission to edit workflows and add fields to issue layouts in company-managed projects (CMPs). This allows the Jira administrator to give trusted users the ability to make adjustments to statuses and transitions and add existing global fields directly to their projects.

1. As a Jira administrator, select the corresponding authorization scheme of the CMP you want to modify.
2. Change the new permissions for Edit Workflows or Manage Issue Layout
   
   
3. Now the user who has received the Edit Workflows or Manage Issue Layout authorization can access the project settings of the relevant CMP to make changes on the Workflow and Issues > Layout tabs.

4. Check your automation rules in Jira and Confluence

A new feature is being introduced for Jira and Confluence automation that will allow you to check your rules for errors before activating them. This validation feature will help improve efficiency and accuracy in rule creation as you will no longer need to check for errors yourself before activating your rule.

Please note that some errors may not be detected during the validation process. Therefore, keep an eye on the audit log to ensure that no further errors occur after the rule has been executed.

How does it work?

At best, it will look like this:

If not, the errors or warnings displayed must be corrected. Finally, the rule can be activated.

5. Administrators can now delete previously used project keys

Administrators now have the option of deleting previous project keys so that they can be used for new projects.

Whenever you change the project key of a project, the previous project keys are automatically saved. This ensures that all links, filters and queries that use the previous key will continue to work.

Administrators can now delete previous project keys from a project so that they can be used for a new project.

6. Creating a Jira issue can now trigger an automation in Confluence

A new trigger has been added to the Confluence automation to execute an automation rule when a new issue is created in a specific Jira project.

Division and product administrators can now create a rule by navigating to a page and selecting the Automation icon. An automation rule can then be defined in Confluence that is triggered as soon as an issue is created in a defined Jira project.

7. Additional administrator function to hide unused fields

The requirement to be able to show or hide unused fields has been implemented. This is done globally via the system settings.

8. Define how long solved issues appear on the board

In Jira Business projects, you now have more control over which work you want to see on the board. Once you move a work item to a Done column, it will remain visible in that column for the selected number of days and then disappear. You can then find these work items in other views such as the list.

9. Restrict request types for customers and organizations in JSM

You can now control who can create certain requests in organization and team-led service projects. Grant access not only to users and groups, but now also to customer accounts and organizations.

Finally, it is possible that only certain customers should be authorized to make certain requests.

These can be requests that are reserved for different departments in your company. Or even those that manage several customers in external companies. Now you have the option to restrict certain request types in Jira Service Management to these customers who do not have Atlassian accounts. In terms of customer organizations, you can also save time by not having to add the same customers to multiple service projects.

10. Create Confluence whiteboards directly from the Jira backlog

Confluence whiteboards allow you to plan flexibly and implement your ideas quickly. Create a whiteboard directly from your Jira backlog. You can copy backlog issues to the whiteboard and organize your planning as you wish.

If an administrator has three or more tasks in their backlog, they will see the button to add Confluence and use a whiteboard. Once a team has Confluence, everyone who has access to Confluence (including administrators and end users) will see the button in their backlog that allows them to create a whiteboard.

You can remove this button at any time by disabling all product recommendations in your Jira settings.

Note: If you add Confluence and then deactivate the product recommendations, this button will no longer be displayed.