• Atlassian Administration
• Jira platform
• Jira
• Jira Service Management
• Jira Product Discovery
• Confluence
• Bitbucket
• Compass
• Opsgenie
• Atlassian Analytics
• Focus

Sync Atlassian teams with Workday data

Organization admins can now sync teams data between Workday and Atlassian through the Teamwork Graph connector. Once synced, teams will be created in Atlassian based on your organization data in Workday. These teams will be marked as verified in Atlassian, and can only be modified in Workday. Read more about syncing teams with Workday

To start syncing teams with Workday:

1. Ensure that the Workday connector has been enabled by an organization admin.
2. Go to the Teams app, and select the Settings icon in the top right corner to open Admin settings.
3. Select HRIS connections.
4. In the section titled Sync HRIS teams in the Teams app, select Sync for the connector you want to use.

Note: If your organization uses Talent, it’s recommended to use the same Workday connector to ensure that both apps are using the same, consistent data.

Copy specific Jira Service Management and Jira Work Management projects to your sandbox

Copy only the projects you need to save time setting up your Jira Service Management and Jira Work Management sandbox. Understand how to select data to copy

To copy specific Jira Service Management and Jira Work Management projects from your production to its sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Sandbox.
3. Select Copy production data for the Jira Service Management or Jira Work Management product.
4. Select Specific projects.
5. Select the service or work management projects you need.
6. Follow the prompts to copy data to your sandbox.

More about what we copy to sandboxes

We’re replacing Beacon with Guard Detect

This update only applies to organizations that participated in the Beacon or Atlassian Information Security beta.

Beacon (beta) will soon be part of Atlassian Guard Premium. Read the blog

We’re replacing ‘Beacon’ with ‘Guard Detect’ in the CSV files you export. The name of your groups (such as beacon-admins) will not change.

In Atlassian Administration, you’re able to export CSV files for:

1. Managed accounts
2. Audit logs
3. External users
4. User API tokens
5. Authentication policies

We recommend checking and updating any scripts that may be impacted by the change.

Accessibility and style improvements to tables and page layouts

We restyled tables and updated the layout of pages. This improves accessibility and readability in Atlassian Administration.

You can see the changes on most pages in admin.atlassian.com.

Apply a default classification level for your entire organization

Data classification is the process of categorizing the sensitivity of information.

Apply a default classification level that can be enforced across your entire organization, enabling you to implement data classification quickly at scale. This classification level will be applied to all unclassified content within the organization.

This process requires Atlassian Guard Premium.

To apply a default classification level across your entire organization:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data classification
3. Select More actions (•••) > Manage settings
4. Choose the classification level
5. Select Update

Copy specific Jira projects or Confluences spaces to your sandbox

Save time copying data to your sandbox by choosing only the projects and spaces you need.

Understand how to select data to copy

To copy specific Jira projects or Confluence spaces from your production to its sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Sandbox.
3. Under Actions in the product table, select Copy production data.
4. Select the Specific projects or Specific spaces.
5. Follow the prompts to copy data into your sandbox.

Learn about what we copy to sandbox

Apply a default classification level for all Confluence products in your organization

Data classification is the process of categorizing the sensitivity of information.

Apply a default classification level that can be enforced across all your Confluence products in your organization. This classification level will be applied to all unclassified content within Confluence.

This process requires Atlassian Guard Premium.

To apply a default classification level for all Confluence products in your organization:

• Go to admin.atlassian.com. Select your organization if you have more than one.
• Select Security > Data classification
• Select More actions (•••) > Manage settings
• Choose the classification level
• Select Update

Prevent your team from using new Bitbucket workspaces without your approval

You can now proactively manage product requests for Bitbucket from admin.atlassian.com. This feature provides you with more oversight to control Shadow IT and billing.

After you select admin review required, you can approve or deny new Bitbucket requests from your managed accounts. This gives you greater control over where your team does their work.

This is available for Bitbucket as part of a beta program. It’s also available for Jira, Jira Service Management, Confluence, and Trello with an Enterprise subscription.

More about product requests

To manage product requests for Bitbucket:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Product requests.
3. Select Request settings. If this is your first time updating these settings, you may need to select Update request settings.
4. Next to Bitbucket, select Require admin review under the Request setting dropdown.

The next time one of your managed accounts tries to sign up for a product, they’ll receive a prompt to enter a reason for their request. After they create the request, all organization admins receive an email, letting them know someone created a request.

Prevent people from downloading attached files

Data security policies allow you to use rules to control how users, apps, and people outside the organization interact with content in Confluence and Jira.

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. Our findings showed that the types organizations needing to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policies currently block exports:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Limit mobile app sessions for users

You can now control when a mobile app session expires from an authentication policy. You’re able to update the mobile app session setting with the number of days for a session. This setting applies only to managed accounts in an authentication policy.

To ensure uninterrupted access to the mobile app, we prompt users to re-authenticate before their session expires.

Mobile app session applies to these mobile apps:
Jira Cloud
Confluence Cloud
Opsgenie (Atlassian Accounts only)

To update the mobile app session expiration:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Authentication policy.
3. Select the policy you’d like to Edit.
4. Enter number of days for when the Mobile app session expires.

Understand authentication policies

Control access to Compass with IP allowlisting

You can now apply IP allowlists to your Compass sites so that users can only access Compass from specific IP addresses. This gives you an extra layer of security.

IP allowlists for Compass requires a Premium subscription.

To apply an IP allowlist to Compass:

Go to admin.atlassian.com. Select your organization if you have more than one.
1. Select Security > IP allowlists.
2. Select Create allowlist.
3. Enter allowlist details.
4. For Applies to, select Compass.
5. Select Create.

Read more about IP allowlists

Improved usability and performance of the user list

We’ve made improvements to the organization’s user list so it’s easier to use. This change applies to customers who have the centralized user management experience.

Status, Role, and App access are now separate filters. Each filter comes with a search field to help you quickly find your criteria.

This update also lets you choose how many users to show per page, so you can browse your user list more efficiently. You can also sort users by their public name.

We updated the look and feel of the user list. Colored status indicators help you easily identify the status of any user.

More user management improvements

To see your organization’s user list:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory.

Introducing your new user requests page

We’re consolidating your access requests into one convenient new page called User requests. We’re also moving it from site administration to your organization.

Why? To give you better visibility over access requests from all sites in your organization. Plus, we’re introducing a new feature called User interests, where you can keep track of and review trending user interest in new apps.

The new experience will be available to Organization admins, and Site admins with centralized user management. Read more on user management

To get started:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > User requests
3. Select Access requests or User interests

SCIM API keys expire in one year

We're changing the expiration date for SCIM API keys from an infinite lifespan to a one year expiration date: This change applies only when you:

-set up user provisioning for the first time
-regenerate an existing SCIM API key

This change does not affect existing SCIM API keys for now.

We’re making this change to reduce security risk for any leaked or stolen keys and to encourage you to rotate your keys. If a key is leaked or stolen, its limited lifespan prevents attackers from using it indefinitely to access sensitive information.

When is this changing?
-On December 15, 2024, SCIM API keys expire in one year. This includes a SCIM API key that we create when you set up user provisioning or when you regenerate a SCIM API key.

How to view the SCIM API key’s expiration date when you set up user provisioning:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your Identity provider Directory.
4. Select Set up user provisioning and follow the prompts.
5. View API key expires date in User provisioning.

How to view the SCIM API key’s expiration date when you regenerate an API key:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your Identity provider Directory.
4. Select Regenerate API key from […} and follow the prompts.
5. View API key expires date in User provisioning.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Tailor your Jira Service Management sandbox setup

We're excited to introduce a new feature that allows you to save time by copying only the specific Jira Service Management (JSM) projects you need to your sandbox. This enhancement streamlines the setup process, ensuring you have exactly what you need without unnecessary clutter. Additionally, audit logs now track the copying of specific projects, providing a clear record of changes for better management and oversight. Understand how to select data to copy

To copy specific Jira Service Management (JSM) projects from your production to its sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Sandbox.
3. Under Actions in the product table, select Copy production data.
4. Select the Specific Jira Service Management projects.
5. Follow the prompts to copy data into your sandbox.

Learn about what we copy to sandbox

Choose what an API key does in your organization

You can now choose what an API key can do with scopes, which are specifically the actions an API key has permission to perform. You’re able to allow APIs to view, write, and delete content in your organization.

To create an API key with scopes:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Settings > API keys.
3. Select Create API key.
4. Enter a Name that makes it easy to remember the API key.
5. Select the expiration date for the API key. Keys can last no longer than a year.
6. Select API scopes to choose what the API key can do in your organization.
7. Review your API key information.
8. Select Create to save the API key.
9. Copy your API key and save it somewhere safe. You can't recover the API key later.

See how Rovo usage is trending in your org

Atlassian Rovo uses AI-driven insights to help you turn information into action. To follow usage trends, view the number of requests your users have sent to Rovo Chat or Agents. Use the date range filter to see usage trends over time.

Explore Rovo features

To view usage trends for Atlassian Rovo:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the AI usage tab.
4. Navigate to the Requests sent to Rovo chart.

Multiple sandboxes for a single production site

You can now create multiple sandboxes for a single production site. Thanks to that, your teams can get a sandbox environment of their own so they can test different kinds of changes in parallel, for example:

• App testing sandbox

• New features sandbox

• Migration sandbox

Multiple sandboxes are in open Beta, available for Enterprise plans. For every plan, like Jira Enterprise or Confluence Enterprise, you can create 10 sandboxes across your entire organization. You can use them for a single production site or spread across more sites, depending on where you need to test the changes.

Tell me more about multiple sandboxes

To get started:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Products > Sandbox.

Org insights, now with better organization

We’ve updated the Insights page so there’s less scrolling to find the right user and activity charts. There are now tabs on the page to group related charts.

To view your organization’s refreshed Insights page:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select a tab to see your charts.

Get more insights about external users

You can now track when external users access a site for a specific app, for example:
Last active on Confluence in my site.

You can find these insights when you export a CSV file in Atlassian Administration for external users in your organization.

To export the CSV file for external users:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > External users.
3. From the External user policy or test policy, select … > Export external users

What is external user security

Removal of trusted user role

We’re removing the trusted user role on March 27, 2025. This change applies to customers who have the original user management experience.

From March 27, 2025, you’ll no longer be able to assign this role to a user. Existing trusted users will still be able to access products and product administration. They won’t be able to invite users or add a product to a site.

Trusted users currently belong to a group that’s hidden from Groups. This group assigns trusted users their user and product admin roles. When we remove the trusted user role, we’ll unhide this group so you can continue to manage its users as a group. It will appear in Groups as trusted-users-<site ID>.

We’re making this change to bring customers who have the original user management experience closer to the centralized user management experience. You can read more about this in our Community post.

We recommend you inform your trusted users of this change. To find the trusted users for a site, go to admin.atlassian.com > Products. Navigate to the site, then select “Trusted” in the “Any role” filter.

If you need to give a user the ability to invite new users or add products to a site, make them a site or organization admin. How to assign admin roles

Find out which external users have customer role access to Jira Service Management

You can now track external users that have customer role access to Jira Service Management.

To see this information, you can export a CSV file in Atlassian Administration.

To export the CSV file of external users:

1. Go to admin.atlassian.com. Select your organization if you have more than one.

2. Select Security > External users.

3. From the External user policy or test policy, select … > Export external users

How to export external users

Reactivate your inactive custom domains

You can now reactivate your previously suspended custom domain. Instead of remaining suspended, your custom domain will be marked as inactive, allowing you the option to activate it whenever you want.

If you're unable to activate your custom domain you may see an Error status, Provisioned status, or an error notification next to your CNAME records. To fix this, you can troubleshoot your custom domain.

To activate your custom domain:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Product URLs.
3. Select the Custom domains tab.
4. For the domain you want to activate select More Actions (…) > Activate domain.

Manage access to analytics for all apps

We're introducing a new setting for analytics, which enables admins to choose whether or not the apps they're using can send data to third-party analytics tools. Check the documentation for the permissions you may need to access the new setting.

By default, this setting is enabled, which allows data sharing for all new app installations. However, admins can choose to enable or disable this setting at any time from the Connected apps page, even before a new app is installed on to a site. Admins can also configure this setting for individual apps at any time.

Manage your integrations and automations with service accounts

You can now create service accounts to manage automations, integrations, and apps for your Atlassian organization.

You’re able to manage the service account lifecycle the same way you manage a user account. You can create and edit the account. You can also give the account app permissions, edit the details of the service account profile, and create an API or OAuth token with scopes for the service account.

To create a service account:

1. Go to Atlassian administration. Select your organization if you have more than one.
2. Select Directory> Service accounts.
3. Select Create a service account.
4. For service account name, enter an alphanumeric Name with 6 to 30 characters.
5. For the optional Description, we recommend you enter the name of a person or app that uses the account.
6. Select roles for the apps that the service account needs to access. You can also add the service account to a group.
7. Select Create.

After you create a service account, you can create an API token or an OAuth token for the service account.

Admins can now see Rovo indexed objects for each third-party connector

Organization admins can now see the number of indexed objects against each Rovo third-party connector. To find out more about indexed objects and Rovo quotas, see Rovo usage quotas.

To see the object count:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Settings > Rovo.
3. Expand the site where you’ve connected a third-party app.

Control access to external user email and notifications

We’re improving how you manage access to email content and notifications for external users. You can now set email and notification visibility in your external user policy.

This means you control whether external users receive content in emails from apps like Jira and Confluence. You can also control if external users receive mobile app push notifications.

To control email and notification visibility, you can choose to:

Allow - Allow external users to receive content in their emails and mobile push notifications.
Block - Block external users from receiving content in their emails and mobile push notifications.

To update email and notification visibility:

1. Log in to admin.atlassian.com > Security > External users.
2. Select a policy.
3. Select Allow or Block for Email and notification visibility.
4. Update the policy.

Monitor user API tokens without a subscription

You no longer need an Atlassian Guard Standard subscription to monitor the usage of user API tokens.

At no extra cost, you can view when a token expires, when it was last used and who created it. You can also revoke a token if you need to. You can track these details about user API tokens only for your managed accounts.

Explore user API tokens

To view user API tokens:

1. Log in to admin.atlassian.com > Security
2. Select User API tokens.

We're renaming 'products' to 'apps'

At Team ‘25, we announced a shift in how we think about and refer to our suite of individual products, now called ‘Atlassian apps’, or ‘apps’ for short.

We’ve started rolling out this terminology change (from ‘products’ to ‘apps’) across Atlassian Administration experiences. Over the coming months, we’ll continue to roll this out to admin emails, support documentation, audit logs, URLs, and more. You may see both terms used as we work through this change.

The way you manage Atlassian apps like Jira and Confluence in Atlassian Administration remains unchanged.

Read more about this change on Atlassian Community

Automatic invitations when you grant a group access to a new app

When you grant a group access to a new app, we email its users to invite them to start using the app. If a user in that group already has access to that app, we won't email them.

To grant a group access to a new app:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory > Groups.
3. Select the group.
4. Select Add app and follow the prompts.

Experience improved reliability and loading time when using Discovered products

In response to recent customer feedback, we’ve made some important updates to the Discovered products screen and process.

We’ve redesigned the screens to improve loading time, and restructured the code to improve the reliability of rendering. These changes should prevent loading failures where customers have high numbers of discovered products. How to review discovered products

To get started:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Discovered product

Atlassian Intelligence & Rovo: Filter active users by site and date range

To better assist you in monitoring adoption trends, we've enhanced the ‘active user’ charts for Atlassian Intelligence and Rovo. You can now filter these charts by:

• • Date range:* View usage trends over specific time periods.

• • Site:* Identify where artificial intelligence features are being used most (if your org has multiple sites with Atlassian Intelligence or Rovo activated).

Understand how Atlassian Intelligence is activated for products, and how Rovo is activated for sites.

To view usage charts for Atlassian Intelligence and Rovo:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Insights.
3. Select the AI usage tab.
4. Navigate to the relevant chart.

You will only see charts for the artificial intelligence tools that are activated and being used in your organization. More on gaining insights into product usage

SharePoint connector now has blocklist and allowlist

The Rovo SharePoint connector now includes support for both blocklist and allowlists. This gives finer control into what content is indexed by Rovo and Atlassian from your SharePoint instance. As an admin, you can configure these while you connect for the first time, or by managing an existing connector.

Improved audit log webhook registration

We've enhanced the webhook registration process to simplify how you edit webhook details.

To edit the details of a registered webhook:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Audit log.
3. Select Settings.
4. Select the Webhook tab.
5. Select Edit details to update the details.

Runs on Atlassian program for cloud apps

We've rolled out a new program for cloud apps called Runs on Atlassian.

Apps that qualify for the program automatically get the Runs on Atlassian badge on their listing page. You can also browse and filter for Runs on Atlassian apps on the Atlassian Marketplace.

Runs on Atlassian addresses the following requirements from customers:

• Apps exclusively use Atlassian-hosted compute and storage.
• Apps support data residency that matches data residency provided by the host product.
• Customers are in control of data egress, such as analytics and logs, and can fully block data egress at any time.

Learn more about the program and what it means for you and your organization.

Provision employee identity information from your identity provider

You can now provision the employee identity (ID) for managed accounts in your organization. When you provision managed accounts through SCIM to your organization, you can view the employee ID for a managed account in their account profile.

To provision employee ID, you need to update the attribute in your identity provider with the following employeeNumber attribute:

urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:employeeNumber

How to map identity provider attributes for Okta, OneLogin, or Microsoft Azure AD

After you update the attribute and sync your managed accounts, you can view the employee ID in their account profile.

To view employee ID:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory > Managed accounts.
3. Select Show details for a user.
4. Select More details.

SCIM API keys set to expire

Your existing System for Cross-Domain Identity Management (SCIM) API keys currently have an infinite lifespan. Starting on April 28, 2025, we will set your keys to expire between May 1, 2026 and May 1, 2027.

What is an existing SCIM API key?
An API key generated before January 1, 2025.

Who does this change apply to?
Identity providers that provision users with SCIM to an Atlassian organization.

This change does not apply to these identity providers: Google Workspace or Microsoft Azure AD for nested groups.

Why are we making this change?
To encourage you to rotate your keys to reduce the risk of leaked or stolen keys.

What action do you need to take?
You don’t need to do anything at this time.

When we make this change you can view the expiration date for your existing SCIM API key.

To view the expiration date of your SCIM API key:

1. Log in to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Identity providers.
3. Select your identity provider Directory.
4. Select Provisioning.
5. View API key expires date in Provisioning.

More about user provisioning

Easier to activate AI for your apps

Activate AI for your apps for both Atlassian Intelligence and AI-powered Rovo features under AI-enabled apps. Read about using AI in your organization

To activate AI for your apps:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Settings > AI-enabled apps.
3. Select Select apps. You’ll see a list of apps that have AI features.
4. Select the apps that you want to activate AI for.

Data residency is now part of the security guide

We are adding a data residency recommendation to our Security guide. This feature provides recommendations when you have'nt yet designated specific locations for your apps . You can see the number of apps that remain unpinned and can easily navigate to the data residency page to take the appropriate actions.

The main objective of this security checklist is to assist you in effectively managing compliance with data residency requirements.

To check if you have any data residency recommendations, go to Security > Security guide. In the Security recommendations section, see the task titled Control the location of your data.

New activities added to Audit log in Atlassian Administration

We're excited to announce that moving forward, we will have monthly updates on any new activities added to the Audit log in Atlassian Administration. This enhancement is designed to help you easily track and stay informed about the latest changes.

Create Jira Product Discovery sandboxes

Set up projects, change configurations, and test on a Jira Product Discovery instance within an isolated environment. Sandbox is available for Jira Product Discovery on the Premium plan. More about sandboxes

To add a Jira Product Discovery sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Apps from the navigation bar.
3. Select Sandbox from the sidebar.
4. From the table of sandbox URLs, select Add and select Jira Product Discovery. (If you don’t have a sandbox site, select Create sandbox to create one.)

Discovered apps: clearer admin details

To help you better manage your Discovered apps (Shadow IT), we now display the organization admin’s name and profile picture in the table. We’ve also added a summary of how the user count is calculated. How to review discovered apps

To view details of discovered apps:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Discovered apps.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

New activities added to audit log in Atlassian Administration (June edition)

We have added new activities to the audit log in Atlassian Administration. You now view these new categories: Encryption actions, Anti Abuse, Focus user actions, Goals user actions, Service account actions.

Additionally, we've expanded the audit log capabilities with new activities for: Jira Service Management Assets Actions, Jira Service Management Product Actions, Loom user actions

These enhancements provide greater visibility and control over user and system activities, ensuring improved security and management within your Atlassian environment.

Explore the audit log activities database to view a comprehensive list of all activities that occur within an Atlassian organization.

We’ve refreshed the look of our Atlassian app icons

We’re thrilled to share some exciting news with you. To continue improving Atlassian Administration, we’ve rebranded our Atlassian app icons.

To see your Atlassian app icons

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Apps.

The legacy Microsoft Teams connector has been deprecated in Atlassian Automation

As of today, all automation rules that use the legacy Office 365 connector webhook in the Send Microsoft Teams message action can no longer be saved or updated, until they are migrated to the new Microsoft Teams workflow.

To update your automation rules:

1. Go to your Teams channel and select … > Workflows > Post to a channel when a webhook request is received.
2. Copy the new webhook URL.
3. Paste this URL into the Send Microsoft Teams message action in your automation rule.
4. Save your rule.

Delete, copy and export rules directly from the automation rulebuilder

We're excited to announce a new feature in Atlassian Automation that enhances your workflow efficiency. You can now quickly copy, delete, and export rules while in the rulebuilder. Previously, you could only complete these actions from the rule list.

This update aims to streamline your rule management process by reducing the number of steps needed to perform these actions. Whether you're setting up new rules or maintaining existing ones, this feature will help you manage your rules more effectively.

Improved usability and performance of user profiles

We made user profiles easier to use. This change applies to customers who have the centralized user management experience.

We moved the App access and Groups tables into tabs. You can now choose how many apps or groups to show in each table, so you can see as many as you want at a glance. This update also adds filters to help you find certain apps or groups when there are many results.

We made the user status more prominent so you can easily see if the user has access to your organization or not.

More user management improvements

To go to a user’s profile:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Directory.
3. Select the user.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Streamlining general and blank project templates in Jira Service Management

We’re simplifying our Jira Service Management project templates and no longer splitting out our general and blank templates by IT and business team types. Now you’ll see just one general service management template and one blank template to cater to all needs - no matter the team type.

These project templates will replace the previous general service management for IT teams and general service management for business teams templates, and the blank project for IT teams and blank project for business teams.

Use the general service management template if you wish to get up and running with basic pre-configured settings to start managing incoming service requests, whilst blank projects let you fully customize how you manage incoming service requests.

Find out more about projects templates in Jira Service Management

Removal of SEN from UPM Manage apps

The SEN field has now been removed from the Manage apps section of UPM. To identify an entitlement, you'll have to use the new cloud identifier, which is the Entitlement number.

Reducing ‘issue’ terminology in Jira

We’re reducing the use of 'issue' terminology in an effort to simplify our language and better suit all team types.

Smart Links are now available in more fields

Add and view Smart Links in URL and short text fields. This will apply to your issue, list, board, and backlog views.

From your list or issue view, copy a valid URL link into a URL or short text field.

Read more about using Smart Links

Smart Links available in more fields

Add and view Smart Links in URL and short text fields. This will apply to your issue, list, board, and backlog views.

From your list or issue view, copy a valid URL link into a URL or short text field.

Highlighted search terms in in-product help

When you search in in-product help, we'll highlight your search terms in results so you can quickly see how the results relate to the terms you've entered.

To search in in-product help, select the help (question mark) icon in the navigation and enter your query in the search field.

Note: In-product help is available in many screens in Jira, including in software, service desk, and work management projects. There may be some screens where in-product help isn't available yet.

Create custom fields while building forms

Admins in team-managed projects can now create custom fields within a form as they're building the form, without having to go to project settings.

Filter form-related requests in Jira

You can now quickly filter and locate requests linked to a submitted form, without the need to manually search.

To get started:

1. Open Jira and navigate your business project.
2. Go to the Forms tab.
3. Locate the recent form.
4. Select View submitted.

You’ll be taken to your list view with the new search filter already applied.

Edit your help center's home page layout and add rich content to it

With this release, admins will have more control over their help center's home page, allowing them to tailor it to fit the needs of their audiences. They will be able to:

• hide and reorder sections on the home page to create a more organized experience
• add layouts, images, and rich content to make the help center visually engaging and user-friendly.

This will help admins create a more customized and appealing help center for their different audiences.

Nest media and codeblocks in quotes

We’ve added the capability to nest media (images, videos, etc.) and codeblocks inside of quotes in the editor. This allows for better context when formatting quotes.

• • Media in quotes*: Users can now embed images, videos, and other media types within quotes, enhancing visual context.

• • Codeblocks in quotes*: Codeblocks can now be nested inside quotes, making it easier to reference and highlight code snippets within discussions.

New and updated virtual agent Channel management

This update simplifies channel management and enhances the visibility and usage of the virtual agent across your Jira Service Management projects.

Streamlined configuration: For a more efficient admin experience, manage all channel configurations from a single Jira Service Management channel home.

Centralized channel visibility: View all connected channels with the virtual agent in one place.

Unified testing: Test draft intents and AI Answers directly from the web preview, eliminating the need for specific Slack request channels.

Read more about how to use the virtual agent in your customer channels

A new home for help center customization features

Quickly access customization options for your help center. All customization features related to the help center are have now moved under the Customize button in the top navigation. From there, you can manage announcements, add login page messages, customize the look and feel, manage topics and portals, and edit the layout of your help center.

Creating a Jira issue can now trigger an automation in Confluence

We're adding a new trigger to Confluence automation that will let you run a rule when a new issue is created in a specified Jira project.

Space and product admins can build a rule by navigating to a page and selecting the Automation (lightning bolt) icon.

1. Select Issue created in Jira as your trigger.
2. Select Connect to connect Confluence to your Jira project.
3. If your organization has multiple Jira sites, you will need to select a Jira site from the Create connection menu.
4. Select one or more projects from the dropdown menu.
5. Continue to build your rule.

Collect higher quality information with business forms

Gather better quality information with new functionality for business forms.

Choose from more fields including parent, category and people. Have more control by making fields optional or required to submit when building a form. You can also add more detailed guidance for people submitting a form, by adding field descriptions.

Manage your form fields

To find updates to business forms, you’ll need project admin access:

1. Open a business project and navigate to Forms in the project navigation.
2. Select an existing form or select + Create form
3. Find all new functionality while building your form.

An improvement to the Jira search experience

We’re boosting performance in the issue navigator by changing how the search field works behind the scenes.

When using the search field, results will be based on the Summary, Description and all text custom fields. The Search issues field in the top navigation will also follow this rule.

Before this change, results were also based in Comments and Worklog, which caused results to be slower to load.

If you’d prefer to search using text fields, select More + to view additional field filters, then select Text.

To try it out, go to the issue navigator in your project and select Issues.

As part of the shutdown of the "External Assets Platform", the ability to create, add, or modify "External Assets Platform" custom fields has now been removed

As part of our ongoing efforts to deliver the most streamlined and integrated service management solution, the ‘External Asset Platform’ will be shut down.

Learn more about the shutdown of the 'External Assets Platform'.

This change will take place in two stages: currently, we are removing the ability to create new "External Assets Platform" custom fields, add these fields to projects, or modify the contents of existing "External Assets Platform" custom fields.

Ultimately, all existing "External Assets Platform" custom fields will be removed, along with any data contained in them. If you have not yet begun backing up your data from your "External Assets Platform" custom fields, we recommend you do so immediately using the provided script.

Efficiency improvements in the calendar view

In our ongoing effort to streamline tasks and enhance your experience with the calendar view, we’re rolling out the following improvements:

• Load more issues without pagination — We’ve replaced the page numbers at the bottom of the calendar with a single Load more button. Selecting this will keep currently loaded issues in view while loading the next 50.

• Real-time updates — If you create, update, or delete an issue, other team members viewing the calendar will see those changes in real-time without reloading the page.

• Hide done items via URL — If you switch on the toggle to hide done items, the parameter hideDone=true will be added to the page’s URL. If switched off, the parameter will be removed. You can use these URLs to share exactly what you’re seeing, without unnecessary configuration. This change is only applicable to business projects.

• Manage issue types — While creating issues in the calendar, you’ll notice a new option to Manage types in the issue type dropdown. Selecting this gives you quicker access to the issue type configuration page in project settings. This change is only applicable to software projects (to match existing functionality in business projects).

• Improved sorting — When a day in the calendar contains multiple items, you’ll notice a consistent sorting pattern that better shows the continuity of longer events and prioritises important context like sprints and releases. Sprints will always appear at the top of the day, followed by multi-day events, releases, and single-day events.

Unless otherwise stated, these changes will be available on software projects, business projects, plans, and Jira Service Management.

To try out these improvements, head to the calendar by going to your project, then select Calendar in the sidebar.

The 'External Assets Platform' Custom Field now includes a shutdown notice

The ‘External Asset Platform’ will be shut down on 17 December 2024 as part of our ongoing efforts to deliver the most streamlined and integrated service management solution.

Learn more about the shutdown of the 'External Assets Platform'.

Now, when you view the 'External Assets Platform' custom field, a DEPRECATED notice will appear in front of the custom field with a warning icon. If you click on the warning icon, you will see additional information and a link to the shutdown notice page that is linked above.

When you create a new custom field of the 'External Assets Platform' type, a warning about the shutdown will also be displayed.

Finally, for existing 'External Assets platform' custom fields that appear within Jira issues, a warning icon will appear next to the custom field name. If you hover over the warning icon, you will see additional information about the shutdown.

Collect more relevant work requests with Jira forms

Collect only the relevant details from your stakeholders. By creating conditions, you can now show specific questions based on responses to previous questions.

To begin creating conditions on a form, you’ll need project admin access:

1. Open a Jira project and navigate to Forms in the project navigation.
2. Select an existing form or select + Create form.
3. Add a priority field, or any custom multi-select or single-select fields to the form builder.
4. Select that field from the form builder to edit.
5. Select Add condition.

Change the assignee straight from Smart Link list view

Change the assignee using a Smart Link list without the need to open the issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select assignee from one of the items. Once the dropdown appears, you can change the assignee straight from the cell.

New Okta actions available in Automation!

We’re excited to announce that we’ve built a new integration with Okta! This integration makes it possible to create a connection between your automation rules and Okta, giving you new ways to use Automation to handle your user lifecycle management needs. The connection with Okta can be made from Automation in Jira Service Management with these two new actions:

Create user in Okta – auto-creates a user in Okta.

Retrieve user details from Okta – checks if a user already exists in Okta, so you can avoid duplicating users.

Read more about how to use these actions and connect your automation rule to Okta.

Introducing 'work' as the new collective term for items tracked in Jira Cloud

As more teams make Jira their home for work, we’re committed to improving the language in our tools to better reflect the diverse ways you define and manage your work.

We’re introducing work as the new collective term for all items tracked in Jira. We’re also exploring ways to incorporate the language you use for your own work types.

• Read more about these changes on the Atlassian Community.

This change builds upon our previous efforts to reduce the use of 'issue' terminology in Jira.

Beta: Generate work item descriptions from Confluence links using AI

AI can assist in generating work item descriptions when you simply paste Confluence links into Jira. By using the context from the Confluence link placed in the description field of the work item, AI creates structured content to generate and improve the description.

To generate work item descriptions:

1. Paste a Confluence link in a work item’s description field. If a Confluence link is already present, edit the description field.
2. Select Improve description.
3. Once the description is generated, select either Insert below or Replace to update the work item description.

Creating issues from Slack using Atlassian Intelligence is now generally available

We are excited to announce that the AI issue creation from Slack feature is now generally available.

With Atlassian Intelligence (AI), you can effortlessly create Jira issues directly from your Slack messages and threads. AI uses the context of your conversations to automatically generate summaries and descriptions filled with relevant details, allowing you to create issues more quickly and efficiently.

To create Jira issues in Slack using AI:

1. Install the Jira Cloud app for Slack.
2. Go to a Slack message or thread, and select More actions.
3. Follow the on-screen steps and select Use Atlassian Intelligence to generate the summary and description.
4. Fill in any additional fields and select Submit.

Find out more about creating Jira issues from Slack using AI

Jira: Fixing JQL query errors using AI is now generally available

We’re excited to announce that AI-powered JQL error fixing is now generally available in Jira.

This feature automatically detects and suggests fixes for common issues, like syntax errors and typos, saving your time and effort when troubleshooting queries. It helps you quickly get to the work you need by making JQL easier and more reliable.

Simply enter and run your JQL query. If there are any errors, they’ll be listed below the editor, along with an AI-generated, error-free query that you can review and instantly apply.

Jira: AI work item creation from Microsoft Teams is now generally available

We’re excited to announce the general availability of AI-powered work item creation from Microsoft Teams chat.

You can now use AI to create Jira work items directly from Microsoft Teams chats. AI analyzes your chat context to quickly generate work item details, saving you time. The content is automatically localized to the language set in your MS Teams settings, ensuring clarity and relevance. Additionally, the AI-generated descriptions follow a pre-defined structure based on the work type, maintaining consistency. Using AI is the default creation method, but you can turn it off anytime while creating work items.

To create Jira work items in Teams using AI:

1. Add Jira Cloud to the team, channel, or meeting chat.
2. On a message in your chat, select the More options (···), then select Create issue in Jira.
3. Choose a project and work item type.
4. If not already selected, select Use Atlassian Intelligence to generate the summary and description to allow AI to generate the work item details.
   • The app remembers your previous selection and apply it each time until you decide to change it.
5. Fill in any additional fields as required and select Create to create the work item.

Create work items from a Loom with AI

You can now use AI to generate multiple work items directly inline in the Backlog, based on content from a Loom video.

AI analyzes the linked Loom video and suggests relevant work items for you to review and create, without switching context. It supports cross-site linking and respects the permissions you apply to the video.

AI-powered work creation helps you reduce manual effort and fast-track backlog management.

To get started:

1. Go to the Backlog in your Jira project.
2. In the inline create field, select Generate from Loom.
3. Search or paste a Confluence link, then select Suggest work items.
4. Review the suggestions. Then, accept them individually or all at once to create work items in the backlog.

Template bundles in the project create page

Effortlessly create between 2 to 6 projects at once, with bundles. We're helping streamline your project creation process and minimizing the need for repetitive manual tasks. Whether you're working in Jira or Jira Service Management, bundles guarantee a smooth project creation experience.

Choose from two pre-set bundles: the Marketing or the IT team bundle. And if they don't fit your requirements, you have the flexibility to customize and create your own bundle.

There are a few ways you can create a bundle, one way is to:

1. Select the plus icon + in the project sidebar
2. Choose More templates from the dropdown
3. Select Bundles

Another way to create a bundle is to:

1. Select Projects > Create project in the top navigation bar
2. Select Bundles

Company-managed projects: Create, edit, and delete columns directly on the board

If you want to quickly add or update a column on your board, you don’t need to go far. You can now create, rename, move, set constraints for, and delete columns without leaving the board. You’ll still have the ability to do all of the above in your board’s settings page, but if you’ve only got time for a quick fix, we’ve now got you covered!

If you’re a project or board admin for the board you want to update, you can try the following changes:

• To create a column, select the + icon to the right of all columns.
• To rename a column, select its name to edit directly.
• To move a column, select its top, then drag the column to its new position.
• To set column constraints, right-click its name or hover to select more actions (•••) > Set column limit.
• To delete a column, right-click its name or hover to select more actions (•••) > Delete.

View high-level work across multiple teams with a new template

Use the new cross-team planning template to get a high-level view of work across multiple teams.

Create Confluence whiteboards directly from your Jira backlog

With Confluence whiteboards, you can plan freely and execute quickly. Create a whiteboard directly from your Jira backlog, copy backlog issues to the whiteboard, and plan however you want.

Here are some suggestions for things you can do with Confluence whiteboards:

• Use award-winning templates such as a prioritizing and planning matrix
• Import Jira issues directly into your new planning whiteboard
• Link sticky notes and issues to show dependencies and timelines
• Turn sticky notes into Jira issues
• Engage teammates with real-time, group editing
• Collaborate using stamps, timers, and more

If an admin has three or more issues in their backlog, they'll see the button that allows them to add Confluence and start using a whiteboard. Once a team has Confluence, anyone with access to Confluence — including admins and end users — will see the button on their backlog that allows them to create a whiteboard.

You can remove this button anytime by turning off all product recommendations at in your Jira settings. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Development feature for software projects in Jira is now generally available

We’re excited to announce that the new development feature for all software projects in Jira is now generally available. The development feature unifies data from your connected code, CI/CD, and security apps into a single view, giving you clear visibility into your team’s work and engineering health. With key software development metrics and proactive work suggestions, you can quickly spot and address delivery bottlenecks, helping your team stay productive and deliver software faster.

All software projects have the development feature enabled by default. Jira project admins can enable or disable it. When enabled, everyone with project access can go to the Development page from the project’s navigation.

To enable or disable the development feature as a Jira project admin

1. Go to your software project in Jira.
2. In the sidebar, select More actions (•••) next to your project’s name, then select Project settings.
3. Select Features.
4. In the Development section, use the toggle next to Development to enable or disable the feature.

If disabled, you can re-enable the development feature at any time from Project settings.

To view and use the Development page

1. Go to your software project, then select Development (assuming it’s enabled).
2. Explore the key metrics, work suggestions, and related work for a holistic view of your team’s progress.
3. For richer insights, ask an admin to connect your source code management, CI/CD, and security apps to Jira (if they aren’t already). Then, link your work items to development and security objects—like builds, commits, pull requests, and vulnerabilities—to see this data on the Development page and across Jira.

New navigation: A faster way to find work

Key parts of the top navigation have moved to the sidebar, aligning Jira with other software tools you use daily. The new navigation is centred on customization capabilities and ease-of-use improvements, featuring:

• A customizable sidebar you can personalize to the unique way you work

• Expand or collapse sidebar options to maximize screen space when needed

• A horizontal project navigation admins can customize to each project

Find out more about the new navigation

Improvements to the workflow editor

We've updated the workflow diagram in company-managed projects to be faster and more accessible.

Improved performance and reliability for CSV exports

If you need to export your Jira issues, you’ll notice a faster and smoother experience due to the following improvements:

• Speed and reliability — the export process is faster and can handle a large number of fields and extensive data sets
• Tracking and control — you can monitor the progress of your export, and cancel if needed

To try it out, go to the Issues page in your project. Select Export, then select a CSV export option.

Note that only one CSV export can be processed at a time.

Speed up your next Jira import with configuration files

When importing multiple projects using CSV files, a configuration file can help you save your preferences, such as project settings, Jira fields, and user information, and use it for future imports. In the new import experience, select Download a configuration file at the end of your next Jira project import. Upload it with a CSV file in another import to bring in the same preferences without the hassle of selecting the same fields once again.

To use a configuration file during an import:

1. From the navigation bar, select Projects > Create project > Import data.
2. Select the app from which you’d like to import your data from. If you can’t find your app in the list, select CSV to use any CSV file to import your data.
   • If you select Asana, ClickUp, monday, or Trello, you can directly import data without a CSV file.
3. Select Upload a configuration file (optional) and upload the configuration file you downloaded from a previous import.
4. Select Next and continue with the import.

Read about configuration files

Enhancements to work item hierarchies in the issue navigator

We've introduced the ability to view work item hierarchies, providing a clear and concise overview of related tasks at a glance. Additionally, you can now easily add work items directly from the list.

This update improves clarity, structure, and scalability. It allows you and your teams to efficiently manage tasks in both team-managed and company-managed projects.

Prefer a flat list view?

If you prefer working with a flat list of work items, you can easily customise your view.

Go to View settings and select Hierarchy

Insight settings are being removed from software projects

As part of our ongoing effort to simplify project settings for admins, we're removing the option to configure insight settings in Jira software projects. Insights will continue to show as normal, but board admins and project admins won't be able to enable or disable specific insights, and any insights that were previously disabled will now be enabled. This means that all insights available in a project will be visible to any user who selects Insights from the board or backlog.

To send us feedback about this change:

1. In your Jira software project, select Board or Backlog.
2. Select Insights.
3. Scroll to the bottom of your Insights and select Give feedback.

List view: Formatted cells will still show color on hover

We’ve introduced hover color to formatted cells in the list view, so you won’t lose the color when hovering over a row. How to create a format rule

Get work suggestions for pull requests with new comments

You’ll now get work suggestions in Jira when new comments are added to your open pull request since the last time you got this suggestion for the same pull request. When you select your avatar on the board, any available suggestions will automatically appear on the work suggestions panel.

The availability of this suggestion type depends on the source code management tool you’re using and its connection with Jira. The new suggestions will be available in scrum and kanban projects in Jira.

Read more about work suggestions in Jira

Updates to creating linked issues for business projects

We’ve made some changes to the way you create linked issues in business projects.

Forge and Connect workflow rules in the new workflow editor

As part of our series of improvements to the new workflow editor in company-managed projects, you'll soon be able to add and edit Forge and Connect workflow rules using the new workflow editor. Previously, this function was only possible in the old workflow editor.

New additions to the More (•••) menu on an issue

When viewing the timeline in business projects, you can now change parent issue, edit an issue's start and end dates, and link to to issues using the More (•••) menu on the issue.

Plans Group now displays related child work items

When grouping, child issues will now appear under their parent’s group, regardless of their assigned group. This change to the plan timeline behaviour aligns with the list view and project timeline.

We’ve made it faster and easier to use new project templates

If you have the ability to create new projects in Jira, you can choose to start from a template, such as Kanban or Scrum. Additionally, you can utilize templates from other apps, like Jira Product Discovery.

In the past, navigating through templates in Jira made it challenging to visualize what each project would look like. Users had to go through multiple clicks before they could actually begin using a selected template.

Now, the templates featured in the ‘Made for you’ section of the template gallery clearly display their functionalities and distinctions. The user experience has also been enhanced, allowing you to start using a template with significantly fewer clicks.

Add and edit statuses on work items in team-managed projects

To help you keep your statuses up-to-date, we've introduced the ability to quickly create and edit statuses while viewing work items in team-managed projects.

Please note that you must be a project admin to add and edit statuses on a work item.

To create statuses when viewing a work item:

1. Go to your team-managed project.
2. Open a work item.
3. In the Status dropdown, select Create status.
4. Add a name and category for the new status, and select Create.

To edit status when viewing a work item:

1. Go to your team-managed project.
2. Open a work item.
3. In the Status dropdown, select Edit status.
4. Update the name and/or category of the status, and select Save.

Group by fields in the All work tab

We're introducing grouping in the All work tab. You can now view work items grouped by Status, Assignee, Priority, Sprint, Story Point, Story Point Estimate, and Category.

To group work items in the All work tab:

1. Make sure you are in the list view in All work.
2. Select the Group button.
3. Choose one field that you’d like to group your list by.
4. Your list will then be grouped by your selection and will only be visible to you.

Beta: Link similar work items using Atlassian Intelligence

This Atlassian Intelligence (AI) feature is in beta. Read more about Atlassian Intelligence features

Use AI to surface and link work items that are similar to yours. Linking similar work items that have been worked on in the past can help you understand the complexity of planning and be a great resource for referring to prior art when coding.

To find and link similar work items using AI:

1. Open your work item.
2. Select Improve work item in the issue details section.
3. Select Link similar work items.
4. Select Link next to each work item to link them one by one, or select Link all to link all at once.

The work items are linked with a ‘relates to’ link type.

Respond to comments faster with Atlassian Intelligence (AI)

You can now use Atlassian Intelligence (AI) to suggest responses to comments on your issues. By leveraging the context of your work and any prior comments, AI helps you craft relevant responses more efficiently.

When viewing an issue, select one of the AI prompts to generate a response that you can review, edit, and submit.

Read more about Atlassian Intelligence features in Jira

Create forms fast with new templates in Jira

We've added pre-defined templates that let you quickly set up forms for your software and business projects without having to manually add your fields.

Create issue types from the list or board view

Admins in team-managed projects can now create issue types while creating new issues from the list or board.

From the list or board view:

• Select Create at the bottom of the items.
• Open the drop-down menu (next to 'What needs to be done?').
• Then, select Create issue type.
• Name the issue type, add a description, and Create.

Map data to Jira issue types to organize your project better

In the new import experience, we're adding a capability for administrators to set up[ issue types|https://support.atlassian.com/jira-cloud-administration/docs/what-are-issue-types/] and hierarchies. This can help you categorize and organize your team’s work by either assigning Jira issue types (epic, task, story, bug, and/or subtask) or creating custom issue types before importing.

When importing data, map column headers from your CSV file to issue type, issue ID, and parent fields. In the next screen (Map values to issue types), you can map the values within the selected issue type column to Jira issue types or create custom issue types. More about mapping data to Jira issue types

Create new statuses from the list view

Admins in team-managed projects can now create new statuses directly from the list.

From the list view:

• Select a status (from the Status column).
• Then, select Create status from the dropdown menu.
• Name the status, select a category, and Submit.

Save time with AI generated subtasks in plans

Plan users can save time and use Atlassian Intelligence (AI) to break work items down into smaller work-items, or subtasks, that can be edited and refined.

No need to create separate tickets and fill in the details. AI does it for you.

Trigger AI from any work item (except level -1 subtasks) in the plan timeline by selecting More actions (•••) then Suggest child work items.

Accept one or all suggestions, or remove a suggestion before displaying the draft work in the plan.

You can also provide a prompt within the AI suggestion box to refine the task list and generate more relevant options.

Atlassian Intelligence is available and automatically activated for all products on Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings, Atlassian Intelligence in Atlassian Administration.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Automatically clone an issue when it’s done

You can now set an issue to automatically clone once its status has been updated to anything defined as “Done” in your project’s status categories. No need to create the same issue over and over for the tasks you regularly need!

Clone issues will automatically inherit all the same fields as the issues they were cloned from - except for attachments, start dates, due dates, links, and child issues. They’ll even inherit the “Clone when issue is done” automation rule, so you can keep the fun going.

Read more about automatically cloning issues

To clone an issue automatically:

1. Open a Jira issue and select Actions.
2. Select the toggle next to Clone when issue is done to switch the automation on or off.

Prevent people from downloading attached files

Data security policies allow you to use rules to control how users, apps, and people outside the organization interact with content in Confluence and Jira.

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. We found that organizations that needed to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policy currently block exports:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Create and save multiple board views in business projects

As project admins, in business projects, you can now create multiple board views within your project, tailored to the needs of your team. Saving the view settings (including filter, grouping, column ordering, collapsed columns, etc) of your board, will be visible for everyone in the project.

You can also rename all all tabs in your business and software projects (except apps).

As an end user, you’ll still be able to apply view settings on top, with the additional ability of reverting back to how your admin had last the board.

For project admins

To save or reset the view configuration for your project:

• Apply view settings (filtering, grouping, column ordering, collapsing columns etc) onto your board view
• Select the Save or reset view settings button located at the top-right of the view.

To create multiple board views:

• Select the + add to navigation button situated on the project navigation
• Select Board and then select Add to navigation.

For non-admin users

To reset the view back to the default:

• Select the reset button located at the top-right of the view.

To rename any of your tabs:

• Hover your cursor over the tab you'd like to rename, then select the more actions button (...) on the tab
• Select Rename from the drop down menu
• Enter a new name and press enter.

Note: This feature is only available to those who have the new navigation enabled

Add statuses quicker in the new workflow editor

We’ve consolidated the three add status buttons at the top of the new workflow editor into one. This single button opens a modal where you can either add a status that's already been created to your workflow or create a new one.

Introducing a brand new way to complete bulk actions in the issue navigator

We’re introducing a toolbar in the issue navigator so users can update multiple issues even more seamlessly.

To use the new toolbar:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. Use the issue checkboxes.
   2. Hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. You can either select Edit fields to make edits to fields in your issues or Change status to transition your issues.

Software projects: Improvements to start and due date fields for scheduling work in the calendar

Use the issue view to quickly schedule work in your calendar. An issue's start and due date fields dictate how work is scheduled, so we've made the following improvements:

• For new software projects: Start and due date fields are now enabled by default so you can quickly schedule issues without configuring the fields beforehand.

• For existing software projects (if fields aren’t already enabled): Admins will notice additional information in the issue view to Enable date fields. Depending on your project type, admins will see the option to Configure fields (in company-managed projects) or Enable (in team-managed projects). Selecting Configure fields will take you to the issue layout settings page, where you can add fields to issue types. Selecting Enable will add the fields straight away.

To get started with this change, open an issue in your software project’s calendar or timeline view.

How to schedule work in the calendar

Improvements for Jira notification emails

We’re moving Jira notifications to a central platform to enhance the delivery and consistency of your emails.

Adaptive handling for large payloads: For emails exceeding the 230 KB payload limit, we’ll remove the attachments, try a different template, or send your emails directly to ensure you don’t miss any notifications.

More consistent email design: All emails not related to work items will be sent with a more modern, consistent design. And if you’re required to comply with HIPAA, you’ll now receive emails with the same design as non-HIPAA customers (with the necessary redactions, of course).

The 'External Assets Platform' Custom Field is shutting down

The ‘External Assets Platform’ is shutting down as part of our ongoing efforts to deliver the most streamlined and integrated service management solution. Learn more about the shutdown of the 'External Assets Platform'.

If you’re a customer currently using the ‘External Assets Platform’ to add context to your Jira issues, we recommend you consider adopting Assets in Jira Service Management, available to Premium and Enterprise customers. Assets allows you to use the Assets objects custom field to display your objects on Jira tickets, and gives you the ability to display your Assets data within Confluence, along with many other features.

Introducing a brand way to delete multiple issues in the issue navigator

We’re introducing an easier way for users to delete multiple issues from their projects.

To delete multiple issues from the issue navigator:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. Select Delete to delete the selected issues.

Updated endpoint for new rules containing incoming webhooks

We're updating the incoming webhooks trigger in Atlassian automation. All rules containing incoming webhook triggers will begin to be routed through more secure endpoint. This update is part of our continuous focus to uplift the security and reliability of Atlassian automation.

Starting today, all new rules created with incoming webhook triggers will automatically be routed through the new endpoint. Any existing rules will continue working as before, however, please note that further action will be required in the future, as these rules will also need to be routed through the new endpoint eventually.

What's next?

• We’ll be providing more information about how to migrate existing rules with incoming webhooks triggers over the next few weeks - this will be announced via community post and email, so keep an eye out for updates!
• Once this information is released, you’ll be able to update your existing rules so that they're routed through the new endpoint. We'll give you instructions on how to transition your existing rules to the new incoming webhook endpoint, and share further details about the eventual retirement of the current legacy webhooks.

View recent automation community posts

The end is near for Epic Link and Parent Link fields

For a little over a year, we've been working to combine the Epic Link and Parent link fields in company-managed projects into the new universal Parent field (which you can read about here). To prevent data loss, the values from both fields have been automatically ported into the Parent field.

With this change, the values in the Epic Link and Parent link fields are no longer visible on the Issue view. If your issue view still includes these fields, simply swap it for the Parent field instead.

Read more in our documentation

Send emails from a custom address using the new Automation action ‘Send customized email’

We’ve introduced the ability to customize the emails that are sent as part of your automation rules.

You can now send emails from a custom email address, add images, and use plain text, rich text, or HTML formatting for the email content. This allows for improved personalization and branding of emails that you send to employees, customers, and more.

To customize your emails:

• From your project settings, go to Automation.
• Select an existing rule or create a new one by selecting Create rule.
• Select Add component and then select THEN: Add an action.
• In the search bar enter ‘email’, then select Send customized email.
• In the Settings tab, enter the email details.
  • For the Recipient(s) field, from the dropdown list you can select user fields or groups. You can also enter smart values, or email addresses for recipients internal or external to your organization. Recipients receive separate emails and will not see other recipient addresses.
  • For the From field, you’ll have the option to customize the email prefix of the default email domain that comes with your site. You can also send emails from any custom email address added at admin.atlassian.com by your organisation admins. Read how to set up custom email addresses.
• In the Content tab, select the content type you want to use for your email. You’ll have the choice of:
  • Plain text – no content formatting, but can include smart values.
  • Rich text – content formatting via the editor toolbar including links and images, and can include smart values.
  • HTML – content formatting via HTML, and can include smart values.
• Enter your content into the Content field. When you’re done filling in the fields in both tabs, select Next.
• Save or Update your rule.

Note that some emails may be blocked and not sent to some recipients if your organization has an external user security policy.

It just got easier to keep on top of your unread comments

We’re introducing an unread badge in the Comments column in the list view to help you easily identify work items with unread comments. This allows you to stay on top of important discussion and collaborate with your team.

To make sure you get to try this feature, we’ll be automatically adding the Comments column to all list views.

Join the conversation and give us early feedback

Create unique, customizable pages in your help centers

Jira Service Management Premium and Enterprise users can create and design landing pages in their help centers.

Admins can use landing pages to curate and efficiently organize help resources for specific subjects or audiences in a visually appealing manner. These stand-alone pages have customizable layouts to which admins can add rich content, images, videos, links, and more.

To create a landing page:

1. Go to the help center of your choice.
2. Select your avatar, and from the dropdown, select Landing pages.
3. Select Create page.
4. Give your page a name and description and select Create.

Read more about creating, customizing and managing landing pages.

See request type and customer satisfaction metrics on the project summary page

You can now access two new charts on the project summary page in Jira Service Management!

The Request types chart shows you how many open issues are in each of your project’s request types.

The Customer satisfaction graph helps you visualize your project’s average CSAT over the last 12 months.

As well as these two charts, we’ve also made some other improvements; now, you can get the most up-to-date data at any time using the refresh button, and share the summary page with your team members by email.

To enable the project summary page:
1. From your service project, select Project settings, then Features.
2. On the Features page, look for the Feature lab heading and find the Project summary toggle.
3. Use the toggle to turn on the feature.
4. Select Summary in your service project navigation to see metrics across your project.

More historical data available in velocity charts

Velocity charts in Jira now show data from more sprints, giving you a clearer picture of your team's productivity over a longer period of time. We've also added an average line so you can easily track your team's average output at a glance. Read more about the velocity chart

To view the velocity chart:

1. Start in your Jira software project.
2. Select Reports.
3. Select Velocity report if you're in a team-managed project, or Velocity chart in a company-managed project.

See all your Asset attributes now in Forms

Take the guesswork out of selecting the right Asset when filling out a form and find all attributes now visible on Asset form fields. Previously when filling out a form, customers would only be able to see the object name which made it hard to know what option to select. Now you’ll see the same attributes listed alongside each object - just like you do on request types.

Add and remove fields from field configurations; new tools to optimize fields in your projects

We’re introducing a number of improvements to the way field configurations and field configuration schemes work. In addition, we’re also adding some new tools which make it easier to remove unused work types and fields from schemes. Here are more details about what’s changing.

You can now remove and add fields to field configurations

Removing a field from a field configuration is similar to hiding it. However, when a field is removed, its configuration isn’t preserved. It will need to be entered again if the field is re-associated.

Adding a field to a field configuration is similar to unhiding it. Once unhidden, it becomes available to the projects associated with the field configuration scheme.

You can manage field associations in the Jira admin panel or using the new field association REST API.

We’re releasing tools which allow you to optimize fields

These tools will automatically identify and remove unused work types from a scheme, as well as unused fields from a field configuration scheme and field configuration. For more details about these tools, see this Atlassian community announcement or type: entry-hyperlink id: 5m0df9oFEgswh305bKEQ1v

Unlocking another level of help center customization

The Jira Service Management help center is getting a sleek and modern design update across all its pages, offering new opportunities for customization. Admins will be able customize the help center navigation and manage background and text color for sections in their home page.

To customize the navigation:
1. Go to the help center of your choice.
2. Select Customize, then Customize look and feel from the navigation.
3. Scroll down the side panel to find the navigation color settings.

To manage section settings:
1. Go to the help center of your choice.
2. Select Customize, then Edit page layout from the navigation.
3. Select the section you want to customize and manage its settings on the side panel.

Copy project configurations to create new Jira Product Discovery projects faster

We’re excited to introduce a new way to speed up project setup in Jira Product Discovery. When creating a new project, you can now reuse the configuration of an existing project instead of starting from scratch.

To reuse a project configuration:

• Go to Create project > Product Management.
• Select Reuse a project configuration.

Read more about creating Jira Product Discovery projects.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

Public access is now available for Jira forms

We are adding a Public access option to the forms available in Jira business and software projects. Any user, including those without a Jira license, will be able to submit a response through a public form.

Only people with project admin permissions will be able to create a public form, and these will be available for all licence editions and both team-managed and company-managed projects. In addition, Jira admins will be able to disable public forms on their site. There is one setting for team-managed projects and one for company-managed.

An unlicensed user can submit a response through a public form, but they will need a Jira license to view and collaborate on the work item created from their submission.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

We've launched a new prioritization project template

When you set up a new project in Jira, you can use project templates. There are many to choose from, including specific templates from different apps like Jira Product Discovery and Jira Service Management.

We've just added a new template for projects that are all about gathering ideas and prioritizing them. With this new prioritization template you can list ideas and add data to them. You can then use this data with common frameworks (such as RICE) to prioritize. The project has multiple views, like an effort and impact matrix, list, or roadmap view, so you can see and share your priorities in a way that suits you.

Anyone who has Jira Product Discovery and permission to create projects can use this template.

Create a chart via the issue navigator

Visualize data from your project in seconds by creating a chart via the issue navigator. Select the column you want to see in a chart, and choose the chart type that best fits your data. The chart will be created based on data from all the filtered issues in your issue navigator.

To create a chart via the issue navigator:

1. Start in a Jira Cloud project.
2. Select Issues to view the issue navigator.
3. Select More actions (•••), then View issues as a chart.
4. Choose the column you want to see in a chart.

Introducing the Fields page in team-managed projects

With this change, project owners need to add a field to the Fields page in team-managed projects before they can use it in a work item layout. You can read more about this process in our documentation.

If you've seen this message before, you're not alone: this feature was announced a few months ago in the Jira community. The main difference is that now it's rolling out to all sites.

There’s a small chance that this may cause some Jira Automations to fail. To resolve this, you’ll need to add the fields to the team-managed projects included in your automations.

See the Premium features in-product before starting a trial

We're introducing a new and faster way to understand and upgrade to Jira Service Management Premium trial. Whenever you choose to upgrade to Premium or start a trial, you will see a modal which lists all new features available to you.

Configure fields directly from All work

Introducing inline field configuration in All work, giving you greater flexibility and control over how you use and manage your view.

Now, it’s more intuitive and efficient to add, edit, and create fields directly from the All work tab.

1. Navigate to the All work tab.
2. Hover between columns. Select Add to include new fields.

If you’re a team-managed project admin:

1. Select + Create field to define new fields inline.

Plans in Jira - More Program boards per plan!

In Plans, you can now have up to ten active Program boards at one time in a plan. A Program board is considered 'active' if it has an end date in the future.

Previously, you could only have two.

Jira: Seamlessly add a due date and assignee when creating work items on list view

You can now add a due date and assignee when creating a work item, without needing to leave the list view in your project.

To create a work item with a due date and assignee on list view:

• Select the + Create button at the bottom of the list.
• Give your work item a name based on what work needs to be done.
• Choose which type of work item you’d like to create from the dropdown.
• Select the due date icon and choose a date from the date picker, or select the assignee icon and choose an assignee.
• Select Create, or press enter or return on your keyboard to create your work item.

Project delete improvements

We’re making the project deletion process easier to follow. When a project is moved to trash and marked for deletion, you have a 60 day window in which to restore a project. After that, the project will be permanently deleted.

With this change, if you don’t require the 60 day grace period, you can select 'Delete now' from the project trash list menu. A ‘Deleting now’ message confirms the project deletion process is underway.

Software projects: board names in the backlog to help identify sprints from other boards

If your backlog includes sprints created from other boards, we’ll show the corresponding board names, along with a link to each board. This makes it easier to track and plan your team’s work when managing sprints across multiple boards.

To display board names in the backlog:

1. Head to your Jira software project’s backlog.
2. Select View settings.
3. Select the Board name toggle to turn the setting on or off.

Filtering is now available in the summary view

We’ve added filters to the summary view so you can customize your view with the information that’s most relevant. You can filter by the following:

• Date range (for when work items were updated, created, or due)
• Assignee
• Work type
• Status
• Parent
• Priority

To try out filtering on the summary view:

1. Start in your Jira project.
2. Select Summary.
3. Select Filter.
4. Choose a filter and select the data you want to see in the summary view.

Jira: Export work items into Excel

You can now export work item fields, comments, history and work log to an Excel file.

To export to Excel:

• Select the work item you want to export.
• Select Actions (…) in the top right navigation, then Export Excel.

We're making it easier to compare plans during a trial

When you're in a trial, you can now click on the trial button in the top navigation and see the plan options available to you. This way, it'll be easier for you to understand the plan that is best for your team based on the features that plan includes. You can also easily upgrade and pay from the plans page.

Automation rules triggered by old incoming webhooks are now marked with warning icons for visibility

We’ve added a new feature to Atlassian Automation to help you easily identify rules that were recently triggered through a legacy incoming webhook. Now, when you open the rule list in Jira or Confluence Automation, warning icons will appear next to rules that are triggered through a legacy incoming webhook endpoint. For these rules to continue working after 30 May 2025, you’ll need to make updates in the connected applications which trigger them.

Please note - the warning icon will continue to be shown 14 days after the rule was last triggered through the legacy endpoint, even if you have updated your connected applications to use the new endpoint. The icon will disappear once 14 days has passed without the rule being triggered through the legacy webhook. You can confirm when your rule was last triggered by viewing the ‘latest call’ timestamp next to the legacy URL.

If you have already made updates in your connected application to use the new endpoint, but there are still requests coming through the legacy endpoint, this may indicate there’s more than one application using the webhook trigger in the same rule. You can confirm if this is has happened by looking at the ‘latest call’ timestamp next to both the legacy and new URLs. In this case, find all the applications connected to your rule and replace the URL and secret in all of them.

To get started with this feature:

1. Open the automation rule list in Jira or Confluence.
2. Click on the ‘Trigger' filter and select the ‘Incoming webhook’ filter. All rules triggered by an incoming webhook will be shown. These rules need to be updated before 30 May 2025.
3. Within these filtered rules, any which have recently been triggered through a legacy webhook will have a warning icon next to their name. This shows which rules are actively using the legacy URL. To learn how to update these rules, you can read our support documentation.

Bulk connecting Rovo connectors

We've made it easier to see and connect to all the connectors that are available to Rovo users, so you can get the most out of your Search.

To get started, select the connect banner in the top of quick find to see and connect all your available Rovo connectors.

Avoid accidentally deleting work items

We’re changing the way Premium and Enterprise users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you can now choose to archive it, or confirm that you want to delete it.

Compact format in the All work tab for team-managed and company-managed projects

Introducing a single row height layout and reduced scrolling, making it easier to scan and manage your work at a glance.

• Go to your project
• Select the All work tab to view the work in a single row height format.

Linking related Confluence content using Atlassian Intelligence is now generally available

We're excited to announce that linking related Confluence content to work items using Atlassian Intelligence (AI) is now generally available.

With AI, you can effortlessly find and link related Confluence content to your work item, so you always have all key information at your fingertips. This allows you to fully understand the work context needed to make progress.

To find and link related Confluence content using AI:

1. Open the work item.
2. Select Improve work item, then Link Confluence content.
3. Select Link for individual links or Link all to link all related Confluence content at once.

Read more about linking Confluence content

Add media from web links

You can now add media, including images and videos, directly from web links into your Jira work items. This is an update to the existing image upload process. Once you select the Add image, video, or file from the toolbar or / command, you can now upload files or media from links.

Watch multiple work items from the backlog and All work tab

Stay updated about the work that matters to you by watching multiple work items in either the backlog or the All work tab. When you watch a work item, you’ll be notified when important changes occur.

To watch or stop watching multiple work items from the backlog or All work tab:

1. Select multiple work items from the backlog or All work tab. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting work items
   3. hold the Shift key to select a group of adjacent work items
2. Select Watch options, then select either:
   1. Start watching to receive updates
   2. Stop watching to stop updates

Create and manage email templates for stakeholder notifications

Jira Service Management Premium and Enterprise users can now save time and customize stakeholder notifications on the go with email templates.

Email templates provide an easy and efficient way to customize stakeholder notifications. They eliminate the need to draft new emails from scratch, especially when teams are responding to incidents, allowing for quick customization and notification. Templates ensure consistent messaging by structuring emails to include all necessary information. You can also use predefined placeholders and dynamic fields, which help minimize the likelihood of omitting critical details.

To create an email template:

1. Go to Settings, then Products.
2. Under Jira Service Management, select Incident management.
3. Go to Email templates.
4. Select Create template.
5. Type in name, sender and reply address, upload header image, if any, and type in the email body.
6. Select Save template.

Find out more about creating and managing email templates.

New option added to the delay action in Atlassian Automation

We've added a new option to the delay action in automation rules. Now, when you add the delay action to your rule, you can either specify the exact amount of delay that you want to occur before your rule runs (such as 5 seconds) or select a random period for the delay to occur over (such as between 3 to 10 seconds). Previously, you could only select a specific amount of delay, so the randomised option provides you with more flexibility in choosing when and how your rule is executed.

A cleaner All activity tab in work items

We’ve updated the All tab in the activity section of each work item. This improves readability and reduces clutter.

It's easier to scan and understand updates in a work item’s history, at a glance:

• Entry grouping: Similar updates are now grouped together to reduce clutter.

• Modern UI: Improved alignment, formatting, and date presentation for a cleaner look.

• Progressive disclosure: Long descriptions and details are now collapsible, reducing excessive scrolling.

This more structured and intuitive layout helps you quickly access relevant updates without the overwhelming detail.

Jira Plans - Turn releases off and on in your plan

Releases are a powerful tool for planning work for software teams, but for Marketing or Design teams? Not so much. For planners who don't need to see releases information from their plans, you can now hide it for a simpler planning experience.

When you turn releases off in your plan, you’ll no longer see:

• the Releases tab
• the Releases field from the timeline as well as any filters that use it
• release markers on the timeline, calendar, and program board
• the option to group work items by assigned releases in the View settings menu
• any rolled up dates based on releases

For a full breakdown of this new feature, read more in our documentation.

Jira: Create work items in a group in list view

You can now create work items directly within a group in the list view. This feature automatically adds the group field (such as assignee) to the new work item, streamlining your workflow.

To create a work item in a group:

1. Go to the list view in your project.
2. Select the group where you want to create the work item.
3. Select Create to add a new work item, which will automatically include the group field.

Jira: Improvements to the child work item panel

The child work item panel is faster to load and more responsive.
You now get smoother scrolling, better performance and real-time, instant updates (without needing to refresh).

Performance and reliability improvements for Assets in Jira Service Management

As announced last year, we’re rolling out several changes to the Assets platform in Jira Service Management designed to improve the system's overall performance and reliability. This includes adding new limits and removing support for several AQL operators, functions, and endpoints. See the following Changelogs for more details:

https://developer.atlassian.com/changelog/#CHANGE-1739

https://developer.atlassian.com/changelog/#CHANGE-1915

https://developer.atlassian.com/changelog/#CHANGE-1905

https://developer.atlassian.com/changelog/#CHANGE-1906

https://developer.atlassian.com/changelog/#CHANGE-2198

Jira: Introducing an improvement to attachment previews

Introducing Grid view for attachments.

This change improves the organization and visualization of attachments.

Attachments appear in a grid view rather than the strip view and list view. You'll still be able to switch to another view, and save that as the default if you prefer.

Grid view helps you to more easily navigate through your content.

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

Jira: Making the status of work items more prominent

The status of a work item will now appear between the title and description of each work item.

Subscribe to your change calendar and explore the new filters

We’ve made major improvements to the change calendar to help you stay on top of change events and avoid conflicts across your services, Assets objects, and teams.

Subscribe to change calendar from your external calendar
You can now generate an iCal link and subscribe to your change calendar from apps like Google Calendar, Apple Calendar, and Outlook. This lets you stay updated on change activity without logging into Jira Service Management.

New JQL filtering in change calendar
Use JQL to filter work items shown in the calendar view. Filter by affected services, affected Assets objects, change types, or any custom fields, so you can focus on exactly what matters.

Show or hide change events by type
Choose which types of change events to display on the calendar, including freeze windows, maintenance windows, and standard work items.

Link your change calendar with affected services and Assets objects
You can now select affected services and Assets object fields when creating a new change window. This helps surface change conflicts more clearly and ensures better risk insights for service-dependent work. Read how to connect Assets schemas with changes

Generate a subscription link directly from your change calendar following these steps:

• Navigate to Operations > Change calendar in your service project.
• Select Subscribe to change calendar icon in your toolbar.
• Choose the event types and calendar format, then generate your calendar link.
• Paste the link into your external calendar app (Google, Apple, or Outlook). Read more about subscribing to change calendar

Once subscribed, you’ll automatically see any future updates to change events in your external calendar.

You don’t need to take any action to start using the new filters or event fields. They’re already available in the change calendar and the change event creation form.

Additional fields now editable in the All work list view

You can now edit Confluence items and linked Goals from the All work list view.

Confluence items and comment summaries are also now included when exporting work items to CSV or HTML.

• In the All work tab, view work items in list view.
• Select Configure columns in the column bar to add the Confluence items or Goals fields to the list view.
• They can now be edited directly in the list.

New 'offer options' standard flow in the virtual service agent

We heard your feedback about the escalate standard flow creating too many work items, so we've introduced a new standard flow, called offer options. Depending on the situation and the channel, offer options is sometimes used instead of escalate.

Offer options is configurable, and lets you choose 1–3 options to present to your customers. These appear as buttons:

• Raise a request starts the escalate standard flow, which lets the customer know a request has been raised and creates a work item.
• See search results takes the customer to the relevant portal, and shows search results based on their first message in the conversation.
• Ask another way tells your customer to try rephrasing their question.

Read more about the 'offer options' standard flow, or find out how to configure 'offer options' in the virtual service agent.

Refined drag and drop experience in the work item

We’re refining the drag and drop experience in the work item to make it more consistent and intuitive across different views in Jira.

We’re running an experiment with two variations.

New plans background save process

No more waiting around for plan changes to save.

Now, you can keep working in your plan while changes save in the background. If there's any errors or incomplete fields, we'll prompt you to reopen the unsaved changes modal and resolve the problem.

Jira Plans - Sprint capacity calculations now includes completed sprints

Completed sprints are now included in capacity calculations on the timeline and program board in Plans. This ensures a more accurate reflection of the team's velocity.

How to view capacity in your plan

Reorder starred projects in the sidebar navigation using drag and drop

You can now reorder the starred projects in your sidebar navigation to more easily organize your projects according to your preferences.

Here's one way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Hover over the starred project you want to move.
3. Drag the project to your desired position.
4. Drop it to set the new order.

Here's another way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Select the More actions for the starred project you want to move, then select Move in sidebar.
3. Select where you'd like to move it in the order.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Create and reorder work items faster in the All work tab

We’re rolling out sibling create and drag and drop re-ranking in the All work tab, so it’s easier to structure and prioritise related work items without switching views.

You can now quickly create a new work item at the same level (a sibling), and re-rank work items by using drag and drop (select and move) when sorted by rank.

Now available for both team-managed and company-managed projects in the All work tab.

Key benefits:

• Plan faster by creating structured work items in context.
• Prioritise quickly with drag and drop (select and move) ranking.
• Avoid unnecessary actions and switching views.

1. Go to the All work tab.
2. Check that your view is sorted by Rank.
   1. Select a work item, then drag and drop (move) to reorder based on priority.
   2. Select a work item, then + Sibling to create a related work item.

Jira: Collapsible sections in work items

You can now collapse sections in a work item view to reduce scrolling and highlight key information.

To use collapsible sections:

1. Open a work item in Jira.
2. Find the section you want to collapse, such as Description or Activity.
3. Select the chevron or section title to collapse or expand it.

Due date notifications now available

As the assignee of work items that are overdue or due today, you'll now receive daily notifications within Jira and via email. Each notification links to a pre-filtered page showing your overdue and due work items. Manage your due date notification preferences by:

1. Select your profile image at the top-right navigation.

2. Select Notifications, then you can manage how you receive notifications for overdue work items.

For more details, join the conversation and provide feedback on our Atlassian Community.

Easily spot your company's top priorities with one focus area icon

All focus areas now share the same icon. We thought having different icons for each type would make things easier, but we got feedback that using words to communicate the type was more effective. If you hover over a focus area icon, you can see the name of the Type in the tooltip. If the focus areas are displayed in a table, you'll see a Type column and can filter by the focus area type.

Deactivated users can’t be mentioned or tagged in work items

We’ve removed anyone who’s been deactivated or deleted from your Jira instance. This means that when you use the @ mention function to tag someone in a comment or a description on a work item, you’ll only see active users in the list of people available to tag.

Parent Key is now included in CSV exports of work items

When exporting work items into a CSV file, the Parent work item key is included alongside Parent ID and Parent Summary.

Parent link and Epic Link fields have been removed from the Board view

With this update, the Parent Link and Epic Link fields can no longer be shown on your board. This is part of our work to combine the two fields into one unified field called Parent field. Read our community post about this change

In a previous change, these fields were converted to read-only fields, and the values ported into the new Parent field. This update removes the ability to view this old data.

Jira: Consolidated actions in the work item view

In Jira’s work item view, we’ve moved the Vote and Feedback actions into the More actions (•••) menu. Previously, these actions were available outside of the menu. This change simplifies the work item view and makes it easier to focus on key actions.

To see this change, navigate to your Jira project. Select a work item to open the work item view, then select More actions (•••).

Jira: A wide view for work items

Reduce visual clutter and surface essential details only by switching your work item to the wide view layout.

To switch your layout:

1. Open a work item in Jira.
2. Select Switch layout.
3. Choose Wide view.

Jira: AI-powered related Confluence content suggestions are now proactive

Jira now uses AI to automatically suggest relevant Confluence content to link to your work items. When you link existing Confluence content to a work item, Jira proactively surfaces related content from your site’s Confluence while respecting access permissions. You can review the content results and link them to the work item so your team always has all the key information needed to fully understand the work context and make progress.

To get started:

1. Open a work item.
2. Select + Add.
3. Select Existing Confluence page. We’ll show you a list of related Confluence content in the Confluence content section.
4. In the Link related Confluence content panel, select Show results to expand the results.
5. Select Link to add content items individually, or Link all to add them all at once.

More custom project template editable settings are here for workflows and issue layouts

We’re excited to announce we’re supercharging company-managed custom project templates for Enterprise users.

More flexible controls means less need for admin support.

Jira admins can clone selected source project settings and empower end-users with the new CMP permissions to Manage Issue layouts and Edit workflows within projects created using custom templates.

To allow these settings, go to the source project and select More actions (•••) then Edit template. From the template name and description screen select Next.

Select the project settings you wish to clone and make editable for template users with required permissions and select Save.

The custom project template will appear to everyone you’ve allowed within the list of project templates available when they select Create project.

Team-managed projects: Currency and percentage formatting now available on number fields

We’ve added new formatting options for number fields in team-managed projects. You can now format any number field to show a number, currency symbol, or percentage symbol. This feature enhances the presentation of numerical data and provides an easy way to track information like budgets, estimates, costs, and more.

You must be an admin to edit fields.

To try out a number field with currency or percentage formatting:

1. Start in a team-managed project.
2. Next to your project's name in the sidebar, select More actions (•••), then Project settings.
3. Select Fields.
4. Find the number field you’d like to configure, select Actions (•••), then Edit field.
5. In the Format section, select either Currency or Percentage.
6. If you selected Currency as the format, you can then select a Currency type (for example, USD or AUD).

Jira Plans - Usability improvements on the Releases tab in Plans

With this update, we've brought some new functionality to the Releases tab in Plans:

• You can now rerank releases within their projects (see image)
• you can change the sorting order of cross-project releases using the toggles at the column header

Parent link and Epic Link fields have been removed from CSV export

With this update, the Parent Link and Epic Link fields are no longer included in CSV or HTML exports of Jira work items. This is part of our work to combine the two fields into one unified field called Parent field. Read our community post about this change

In a previous change, these fields were converted to read-only fields, and the values ported into the new Parent field. This update removes the ability to view this old data.

Improve visual and hierarchy of the Quick actions menu in the work item

We’ve improved the Quick actions menu in the work item with a cohesive visual look, and better action hierarchy and grouping, making it easier for you to find and use the tools you need.

We’ve also added Goals and recommendations to the menu.

Open a work item and select the Add button under the summary.

Jira: Select a work item from the Summary column in All work

The Summary column in the All work tab now includes Select work item.

1. Go to the All work tab.
2. Hover over the Summary column or focus on Select work item by pressing the Tab key.
3. Select to open the work item view.

Import workflow from Marketplace feature has been deprecated

With this release, users will no longer be able to import workflows hosted in marketplace apps.

Opsgenie on-call is moving to Jira Service Management

Atlassian ended new sales of Opsgenie on June 4, 2025, and will end support on April 5, 2027.

With this change, we’re moving to a better alerting and on-call experience with Jira Service Management, which offers advanced incident response capabilities including AI-powered automation and streamlined workflows to fully support your team’s operations.

To continue using on-call features and access a range of powerful new capabilities, move to Jira Service Management.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

Jira: Create work items inline in the Backlog with AI (beta)

You can now use AI to generate multiple work items directly inline in the Backlog, based on content from a Confluence link.

AI analyzes the linked Confluence page and suggests relevant work items for you to review and create—all without switching context. It supports cross-site linking and respects your existing access permissions to Confluence content.

AI-powered work creation helps you save time, reduce manual effort, and streamline backlog management by quickly turning documentation into actionable tasks.

To get started:

1. Go to the Backlog in your Jira project.
2. In the inline create field, select Generate from Confluence.
3. Search or paste a Confluence link, then select Suggest work items.
4. Review the suggestions. Then, accept them individually or all at once to create work items.

Improvements to the Fields pages in Jira Admin - Part 1

We're rolling out the first phase of our improved fields management experience in Jira that we announced in the Atlassian Community at the start of June. Our post outlines the full list of changes as well as how this fits into our larger plan. The Atlassian Community is also where we'll share updates, announce future changes in full detail, and engage with the community to make sure we're delivering an experience that meets your needs.

This first release includes changes that make field management simpler and more efficient for Jira admins, such as a redesigned Fields page (formerly Custom fields) that now shows fields created by Jira or plugins (i.e., System fields). You can also create and add new fields to configuration schemes without leaving the page, and filter and sort fields based on Field category type.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

Attachments now supported for the 'Send customized email’ action in Automation

We’ve introduced the ability to add attachments to emails sent as part of your automation rules.

Once a rule has been saved or enabled, you’ll be able to upload files as part of the email content. When the rule executes, any uploaded files will be included as attachments to the emails that are sent.

This capability will be available when using the Send customized email action as part of your Jira automation rules, and will become available for use in other Atlassian apps in the future.

Read more about the Send customized email[ action in Automation.|https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-customized-email]

This highly-requested update includes:

• Attachment support: You can now add attachments (in most file formats up to a total of 5MB) to your automated emails.
• Secure storage: All attachments are stored securely in Atlassian’s media platform, ensuring reliability and compliance.
• Easy preview: Once uploaded, you can open a preview of an attachment by selecting a card in the Attachments field.

To add attachments to your automated emails:

• Add the Send customized email action to an automation rule, then fill in the email details in the Settings tab.
• Select the Content tab, then from the Attachments field browse or drop the files you want to attach to the email.
• Select Update.

Note that the rule must be saved or enabled before you can add attachments to the email action.

Jira Plans - View your calendar one week at a time

When looking at the Calendar view in your plan, you can now isolate to see one week at a time.

Prompt inactive Confluence users to create content from work items

We're introducing a feature that encourages inactive Confluence users to create content directly from Jira work items. This feature targets users who haven't been active in Confluence for the past 28 days and belong to sites that have had Confluence for more than 14 days. When these users view certain Jira work items, they'll see a suggestion to create a relevant project document in Confluence.

To start using this feature:

1. Open a Jira issue of type epic, story, or bug.
2. Look for the Confluence content section.
3. Select the suggested template to create a project document in Confluence.
4. Follow the prompts to complete and publish your document.

The legacy Microsoft Teams connector has been deprecated in Atlassian Automation

As of today, all automation rules that use the legacy Office 365 connector webhook in the Send Microsoft Teams message action can no longer be saved or updated, until they are migrated to the new Microsoft Teams workflow.

To update your automation rules:

1. Go to your Teams channel and select … > Workflows > Post to a channel when a webhook request is received.
2. Copy the new webhook URL.
3. Paste this URL into the Send Microsoft Teams message action in your automation rule.
4. Save your rule.

Avoid accidentally deleting work items

We’re changing the way users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you must complete a two-step process to confirm the action.

To delete a work item:

1. Select the work item you want to delete.
2. Select More actions (•••), then select Delete.
3. To go ahead with deleting the work item, type “delete” in the text box.
4. Select Delete (this option will only be available after you type “delete” in the text box).

New suggestions in search box

We're introducing some new personalised and smart suggestions when you open the search box, but before you begin to type. These will more easily help you find information relevant to you.

We're deleting unused field associations

Starting today (June 16, 2025), we’re beginning the process of removing unused field associations from your field configuration schemes. We expect this process to take several weeks from today. Once finished, this will improve the performance and stability of your Jira instances.

If this causes any issues in your projects, we have documented the steps for adding fields back in this Atlassian community announcement. The page also covers how we determine which associations to delete. If you have any questions about this scheduled deletion, you can ask them in the comments section of the linked announcement.

Selecting dates in Jira is now easier

We’ve made improvements to the way you select dates and times in Jira, making it more efficient to schedule work and keep your team on track.

Key changes:

• Smart defaults: The placeholder date has been updated to the current day’s date and time.
• Keyboard navigation support: You can now press "tab" or "enter" to confirm a selection.

Delete, copy and export rules directly from the automation rulebuilder

We're excited to announce a new feature in Atlassian Automation that enhances your workflow efficiency. You can now quickly copy, delete, and export rules while in the rulebuilder. Previously, you could only complete these actions from the rule list.

This update aims to streamline your rule management process by reducing the number of steps needed to perform these actions. Whether you're setting up new rules or maintaining existing ones, this feature will help you manage your rules more effectively.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Jira: AI-powered linking of similar work items is now generally available

We’re excited to announce the general availability of AI-powered linking of similar work items.

Jira now uses AI to automatically find and surface similar work items from your project, saving you time and effort. This feature makes it easier for your team to reference prior work, understand complexity, and provide the context needed to plan and code with confidence.

Read more about AI features in Jira

To find and link similar issues with AI:

1. Open a work item.
2. Select + Add, then select Linked work item. Alternatively. select Improve task, then Link similar work items.
3. In the Link similar work items panel, select Show results.
4. Select Link as related to link work items with a ‘relates to' relationship type. You can change the relationship type by selecting the Link as menu.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Control playbooks visibility using JQL

You can now use JQL in the playbook details section to control playbook visibility. This helps agents see only the most relevant playbooks, improving process efficiency and reducing noise. Read more about playbook details.

Save playbooks as draft

Creating a meaningful playbook often takes time, and it may not always possible to have every detail ready upfront. To add flexibility to the playbook creation process, we’ve introduced a new Save as draft feature for playbooks.

With draft mode, you can:

• Save your work and return later to complete it.
• Build and refine playbooks at your own pace, without losing progress.
• Skip validations that are only required to turn on the playbook.

Playbooks in Jira Service Management

You can now use playbooks to create clear, step-by-step instructions and automated rules for resolving issues. Similar to Standard Operating Procedures (SOPs), playbooks help standardize and optimize your issue resolution processes. Read more about playbooks.

To view a list of playbooks, go to Project settings > Playbooks.

Select a playbook to open it, or create a new playbook using the Create playbook button.

Use Atlassian Intelligence to draft a reply

You can now use Atlassian Intelligence to draft replies (beta) for your customers. The replies will be based on comments added by agents while resolving similar requests.

To use Atlassian Intelligence to draft a reply:

1. Select any issue from Queues.
2. Select Add internal note or Reply to customer.
3. Select Atlassian Intelligence from the toolbar, and then select Draft Reply. Alternatively, use /draftreply.

You can copy, insert, or edit the reply as needed.

Enhancements to work item hierarchies in the issue navigator

We've introduced the ability to view work item hierarchies, providing a clear and concise overview of related tasks at a glance. Additionally, you can now easily add work items directly from the list.

This update improves clarity, structure, and scalability. It allows you and your teams to efficiently manage tasks in both team-managed and company-managed projects.

Prefer a flat list view?

If you prefer working with a flat list of work items, you can easily customise your view.

Go to View settings and select Hierarchy

Announcing a new way to streamline processes across your projects with Journeys

Build end-to-end journeys that automatically connect work items across both service and software projects in Jira Service Management. Here you’ll be able to get a view of all the work that needs to happen as part of a specific process, and the relationships between the specific teams doing the work.

You’ll also able to control when, where and how these work items get created so you can increase efficiencies by streamlining all the various processes that may cross multiple departments. This could include processes such as employee onboarding or off-boarding that require action from different teams who may not be in the same project.

All you have to do is set a trigger so a journey type knows when to start creating and linking work items across projects. You can also pause the progress of a journey by stopping subsequent work items from being created until a dependency on another work item’s status is met. Plus map Automation rules to specific work items in a journey that may require additional functionality or flexibility.

Read more about journeys

To start using Journeys:

1. From your company-managed service project, select Project settings, then Features.
2. Under Features lab, turn the toggle on next to Journeys to enable this feature.

If you participated in our early access program, this feature will be enabled for you by default.

Automation suggestions in issue and alert views

In the issue and alert views, you’ll now receive automation rule suggestions to help improve your team’s efficiency and simplify the alert management workflow. These suggestions are generated based on keywords found in the issue summary and description, and offer relevant automation options that can be beneficial for your team. By implementing these rules, you can reduce manual tasks, save time, and ensure more consistent management of issues and alerts.

If you are an admin:

• To set up and enable the rule for your team, click Build this rule.
• To modify an existing rule, click Edit in rule builder.
• By default, automation suggestions are visible to everyone. To control who sees these suggestions, go to Project Settings > Features > Automation Suggestions. Turning it off will prevent your team from receiving suggestions.

If you’re an agent:

• You can request your admin to build and enable the suggested rules for you.
• To view details about a suggestion, click View rule.
• To quickly send a request to your admin, click Copy message to copy the message and send it to your admin.

Use the virtual service agent in email (beta)

You can now activate the virtual service agent in email (beta) so that your customers can find the help they need. When your customers send requests to the email address connected to your project, the virtual service agent responds using Atlassian Intelligence answers.

Find out more about using virtual service agent in email

Edit your help center's home page layout and add rich content to it

With this release, admins will have more control over their help center's home page, allowing them to tailor it to fit the needs of their audiences. They will be able to:

• hide and reorder sections on the home page to create a more organized experience
• add layouts, images, and rich content to make the help center visually engaging and user-friendly.

This will help admins create a more customized and appealing help center for their different audiences.

We’ve made it faster and easier to use new project templates

If you have the ability to create new projects in Jira, you can choose to start from a template, such as Kanban or Scrum. Additionally, you can utilize templates from other apps, like Jira Product Discovery.

In the past, navigating through templates in Jira made it challenging to visualize what each project would look like. Users had to go through multiple clicks before they could actually begin using a selected template.

Now, the templates featured in the ‘Made for you’ section of the template gallery clearly display their functionalities and distinctions. The user experience has also been enhanced, allowing you to start using a template with significantly fewer clicks.

Add and edit statuses on work items in team-managed projects

To help you keep your statuses up-to-date, we've introduced the ability to quickly create and edit statuses while viewing work items in team-managed projects.

Please note that you must be a project admin to add and edit statuses on a work item.

To create statuses when viewing a work item:

1. Go to your team-managed project.
2. Open a work item.
3. In the Status dropdown, select Create status.
4. Add a name and category for the new status, and select Create.

To edit status when viewing a work item:

1. Go to your team-managed project.
2. Open a work item.
3. In the Status dropdown, select Edit status.
4. Update the name and/or category of the status, and select Save.

Dedicated page for Atlassian Intelligence answers in the virtual service agent

We've moved the toggle for Atlassian Intelligence answers in the virtual service agent out of the Settings page and into its own AI answers page.

To turn Atlassian Intelligence answers on or off in your project's virtual service agent:

1. From your service project, select Project settings, then Channels & self service, then Virtual service agent.
2. Select AI answers.
3. To activate Atlassian Intelligence answers, turn the toggle on next to Atlassian Intelligence answers, and then select Activate.
   • Atlassian Intelligence answers will start working immediately in all of your connected channels.
4. To deactivate Atlassian Intelligence answers, turn the toggle off next to Atlassian Intelligence answers, and then select Deactivate.
   • Atlassian Intelligence answers will stop working immediately in all of your channels.

Read more about Atlassian Intelligence answers.

Create issue types from the list or board view

Admins in team-managed projects can now create issue types while creating new issues from the list or board.

From the list or board view:

• Select Create at the bottom of the items.
• Open the drop-down menu (next to 'What needs to be done?').
• Then, select Create issue type.
• Name the issue type, add a description, and Create.

Address gaps in your knowledge base with suggested topics

You can now quickly identify the topics that require knowledge base articles in your project with suggested topics powered by Atlassian Intelligence. This feature gives your team a headstart on knowledge articles you should be creating to deflect requests and increase self service among your customers.

To generate a list of topics, we analyze the details of recent requests in your project and check for related articles. The list of suggestions will be refreshed every 7 days, ensuring that your team remains informed of the most relevant topics.

Read more about suggested topics in knowledge base.

Create new statuses from the list view

Admins in team-managed projects can now create new statuses directly from the list.

From the list view:

• Select a status (from the Status column).
• Then, select Create status from the dropdown menu.
• Name the status, select a category, and Submit.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Prevent people from downloading attached files

Data security policies allow you to use rules to control how users, apps, and people outside the organization interact with content in Confluence and Jira.

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. We found that organizations that needed to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policy currently block exports:

1. Go to Atlassian Administration. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

Get more work done in less time with suggestions in Jira Service Management

We’re introducing suggestions on the issue view to help your teams gather context and start working on issues quickly based on a list of actions. Powered by Atlassian Intelligence, this feature is currently available for service requests and incidents only.

To turn on suggestions for a project:

1. From your service project, select Project settings, then Features.
2. Turn on Suggestions.

After the feature is turned on, the suggestions will appear automatically in the issue view for requests and incidents along with other context fields.

Read more about suggestions.

Tailor your Jira Service Management sandbox setup

We're excited to introduce a new feature that allows you to save time by copying only the specific Jira Service Management (JSM) projects you need to your sandbox. This enhancement streamlines the setup process, ensuring you have exactly what you need without unnecessary clutter. Additionally, audit logs now track the copying of specific projects, providing a clear record of changes for better management and oversight. Understand how to select data to copy

To copy specific Jira Service Management (JSM) projects from your production to its sandbox:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Products > Sandbox.
3. Under Actions in the product table, select Copy production data.
4. Select the Specific Jira Service Management projects.
5. Follow the prompts to copy data into your sandbox.

Learn about what we copy to sandbox

Enhanced customer and organization directory

We are excited to introduce a refreshed directory experience in Jira Service Management, featuring separate views of Customers and Organizations. This update provides a more modern and user-friendly interface, allowing you to easily switch between customer and organization views, reducing clutter and enhancing focus. The new layout is available to all service projects, enhancing navigation and clarity without requiring any additional setup.

To get started with this change:

1. From your service project's sidebar, go to Directory.
2. Select Customers to view the customers in your project.
3. Select Organizations to view the customer organizations associated with your project.

New AI features to find similar issues, triage issues, and more

We’re excited to announce that the following Atlassian Intelligence-powered features in Jira Service Management are now generally available:

Similar requests panel that helps agents easily find issues similar to the one they’re working on.

Customer sentiment that helps you quickly understand how customers are feeling based on their comments.

Triage issues that suggests new request types for multiple issues in your queue.

Read more about Atlassian Intelligence features in Jira Service Management.

Introducing a brand new way to complete bulk actions in the issue navigator

We’re introducing a toolbar in the issue navigator so users can update multiple issues even more seamlessly.

To use the new toolbar:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. Use the issue checkboxes.
   2. Hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. You can either select Edit fields to make edits to fields in your issues or Change status to transition your issues.

See the Premium features in-product before starting a trial

We're introducing a new and faster way to understand and upgrade to Jira Service Management Premium trial. Whenever you choose to upgrade to Premium or start a trial, you will see a modal which lists all new features available to you.

Virtual service agent in email is now generally available

We’re excited to announce that the virtual service agent in email is now generally available. You can activate the virtual service agent in email so that your customers can find the help they need. When your customers send requests to the email address connected to your project, the virtual service agent responds using Atlassian Intelligence answers.

Find out more about using virtual service agent in email

Improvements for Jira notification emails

We’re moving Jira notifications to a central platform to enhance the delivery and consistency of your emails.

Adaptive handling for large payloads: For emails exceeding the 230 KB payload limit, we’ll remove the attachments, try a different template, or send your emails directly to ensure you don’t miss any notifications.

More consistent email design: All emails not related to work items will be sent with a more modern, consistent design. And if you’re required to comply with HIPAA, you’ll now receive emails with the same design as non-HIPAA customers (with the necessary redactions, of course).

New automation rules and the Service Triage Agent

We’re introducing new automation rule templates that trigger the Service Triage Rovo Agent and use its responses to automate field updates for requests in your service project.

Currently, we’ve introduced the following templates:

• A rule that updates the summary based on the issue description
• A rule that updates the priority for an issue based on similar requests
• A rule that updates the request type for an issue based on similar requests
• A rule that generates a summary of the issue when it’s closed

For example, when a new request is created in your project, Service Triage can suggest a priority based on similar requests and update the priority field if the suggested value is different from the current value. The Agent also adds an internal comment to describe the updates, so that anyone working on the request can view the changes.

The fastest way to get started is to use a template:

1. In your service project, go to Automation.
2. Select the Templates tab.
3. Select the Service Management category
4. Select a template and follow the prompts to configure it.

When you use the template, you’ll need to connect Rovo to your instance.

Read more about how to connect to Rovo.

Read more about Rovo Agents in automation.

The 'External Assets Platform' Custom Field is shutting down

The ‘External Assets Platform’ is shutting down as part of our ongoing efforts to deliver the most streamlined and integrated service management solution. Learn more about the shutdown of the 'External Assets Platform'.

If you’re a customer currently using the ‘External Assets Platform’ to add context to your Jira issues, we recommend you consider adopting Assets in Jira Service Management, available to Premium and Enterprise customers. Assets allows you to use the Assets objects custom field to display your objects on Jira tickets, and gives you the ability to display your Assets data within Confluence, along with many other features.

Introducing a brand way to delete multiple issues in the issue navigator

We’re introducing an easier way for users to delete multiple issues from their projects.

To delete multiple issues from the issue navigator:

1. Select multiple issues from the list view in the issue navigator. You can either:
   1. use the issue checkboxes
   2. hold Ctrl (Windows) or Command (Mac) while selecting issues
   3. hold the Shift key to select a group of adjacent issues
2. The new toolbar will appear. Select Delete to delete the selected issues.

Updated endpoint for new rules containing incoming webhooks

We're updating the incoming webhooks trigger in Atlassian automation. All rules containing incoming webhook triggers will begin to be routed through more secure endpoint. This update is part of our continuous focus to uplift the security and reliability of Atlassian automation.

Starting today, all new rules created with incoming webhook triggers will automatically be routed through the new endpoint. Any existing rules will continue working as before, however, please note that further action will be required in the future, as these rules will also need to be routed through the new endpoint eventually.

What's next?

• We’ll be providing more information about how to migrate existing rules with incoming webhooks triggers over the next few weeks - this will be announced via community post and email, so keep an eye out for updates!
• Once this information is released, you’ll be able to update your existing rules so that they're routed through the new endpoint. We'll give you instructions on how to transition your existing rules to the new incoming webhook endpoint, and share further details about the eventual retirement of the current legacy webhooks.

View recent automation community posts

The end is near for Epic Link and Parent Link fields

For a little over a year, we've been working to combine the Epic Link and Parent link fields in company-managed projects into the new universal Parent field (which you can read about here). To prevent data loss, the values from both fields have been automatically ported into the Parent field.

With this change, the values in the Epic Link and Parent link fields are no longer visible on the Issue view. If your issue view still includes these fields, simply swap it for the Parent field instead.

Read more in our documentation

Trigger Workato recipes during a virtual service agent conversation flow

Use our new Workato integration with Jira Service Management’s virtual service agent to automatically fetch information and take actions across hundreds of applications!

The new trigger Workato recipe step in the virtual service agent allows you to trigger an existing Workato recipe during a conversation flow.

Find out how to connect the virtual service agent to Workato, and then read more about triggering Workato recipes in conversation flows.

Send emails from a custom address using the new Automation action ‘Send customized email’

We’ve introduced the ability to customize the emails that are sent as part of your automation rules.

You can now send emails from a custom email address, add images, and use plain text, rich text, or HTML formatting for the email content. This allows for improved personalization and branding of emails that you send to employees, customers, and more.

To customize your emails:

• From your project settings, go to Automation.
• Select an existing rule or create a new one by selecting Create rule.
• Select Add component and then select THEN: Add an action.
• In the search bar enter ‘email’, then select Send customized email.
• In the Settings tab, enter the email details.
  • For the Recipient(s) field, from the dropdown list you can select user fields or groups. You can also enter smart values, or email addresses for recipients internal or external to your organization. Recipients receive separate emails and will not see other recipient addresses.
  • For the From field, you’ll have the option to customize the email prefix of the default email domain that comes with your site. You can also send emails from any custom email address added at admin.atlassian.com by your organisation admins. Read how to set up custom email addresses.
• In the Content tab, select the content type you want to use for your email. You’ll have the choice of:
  • Plain text – no content formatting, but can include smart values.
  • Rich text – content formatting via the editor toolbar including links and images, and can include smart values.
  • HTML – content formatting via HTML, and can include smart values.
• Enter your content into the Content field. When you’re done filling in the fields in both tabs, select Next.
• Save or Update your rule.

Note that some emails may be blocked and not sent to some recipients if your organization has an external user security policy.

Updated search and filtering options for queues ✨

Filter your queues further with dropdown filtering! This is a highly requested feature of queues that we're excited to announce for Jira Service Management. By default, the Request type, Status, and Assignee filters are always available, but you can also use More filters to add additional filtering options based on other fields in your project.

We've also updated the search bar in queues so that it can now search through almost all text fields on your work items, including the issue key.

Read more about queues.

Create unique, customizable pages in your help centers

Jira Service Management Premium and Enterprise users can create and design landing pages in their help centers.

Admins can use landing pages to curate and efficiently organize help resources for specific subjects or audiences in a visually appealing manner. These stand-alone pages have customizable layouts to which admins can add rich content, images, videos, links, and more.

To create a landing page:

1. Go to the help center of your choice.
2. Select your avatar, and from the dropdown, select Landing pages.
3. Select Create page.
4. Give your page a name and description and select Create.

Read more about creating, customizing and managing landing pages.

See request type and customer satisfaction metrics on the project summary page

You can now access two new charts on the project summary page in Jira Service Management!

The Request types chart shows you how many open issues are in each of your project’s request types.

The Customer satisfaction graph helps you visualize your project’s average CSAT over the last 12 months.

As well as these two charts, we’ve also made some other improvements; now, you can get the most up-to-date data at any time using the refresh button, and share the summary page with your team members by email.

To enable the project summary page:
1. From your service project, select Project settings, then Features.
2. On the Features page, look for the Feature lab heading and find the Project summary toggle.
3. Use the toggle to turn on the feature.
4. Select Summary in your service project navigation to see metrics across your project.

See all your Asset attributes now in Forms

Take the guesswork out of selecting the right Asset when filling out a form and find all attributes now visible on Asset form fields. Previously when filling out a form, customers would only be able to see the object name which made it hard to know what option to select. Now you’ll see the same attributes listed alongside each object - just like you do on request types.

Add and remove fields from field configurations; new tools to optimize fields in your projects

We’re introducing a number of improvements to the way field configurations and field configuration schemes work. In addition, we’re also adding some new tools which make it easier to remove unused work types and fields from schemes. Here are more details about what’s changing.

You can now remove and add fields to field configurations

Removing a field from a field configuration is similar to hiding it. However, when a field is removed, its configuration isn’t preserved. It will need to be entered again if the field is re-associated.

Adding a field to a field configuration is similar to unhiding it. Once unhidden, it becomes available to the projects associated with the field configuration scheme.

You can manage field associations in the Jira admin panel or using the new field association REST API.

We’re releasing tools which allow you to optimize fields

These tools will automatically identify and remove unused work types from a scheme, as well as unused fields from a field configuration scheme and field configuration. For more details about these tools, see this Atlassian community announcement or type: entry-hyperlink id: 5m0df9oFEgswh305bKEQ1v

Unlocking another level of help center customization

The Jira Service Management help center is getting a sleek and modern design update across all its pages, offering new opportunities for customization. Admins will be able customize the help center navigation and manage background and text color for sections in their home page.

To customize the navigation:
1. Go to the help center of your choice.
2. Select Customize, then Customize look and feel from the navigation.
3. Scroll down the side panel to find the navigation color settings.

To manage section settings:
1. Go to the help center of your choice.
2. Select Customize, then Edit page layout from the navigation.
3. Select the section you want to customize and manage its settings on the side panel.

Copy project configurations to create new Jira Product Discovery projects faster

We’re excited to introduce a new way to speed up project setup in Jira Product Discovery. When creating a new project, you can now reuse the configuration of an existing project instead of starting from scratch.

To reuse a project configuration:

• Go to Create project > Product Management.
• Select Reuse a project configuration.

Read more about creating Jira Product Discovery projects.

AI drafts to help you write knowledge articles faster

To make it easier for your team to write articles, we’re releasing a new feature that uses Atlassian Intelligence to generate drafts for the most common requests you receive from your customers. AI drafts are based on details such as summary, description, and comments in issues.

To access AI drafts, you need to have an active knowledge base and Atlassian Intelligence turned on for your site.

To view AI drafts:

1. From your service project, go to Knowledge base.
2. Select Suggested topics.
3. Under the Topics column, you can view specific topics for which customers are submitting requests but your knowledge base doesn't have corresponding articles.
4. Select View draft.

Make necessary edits to the draft and create an article to add to your knowledge base.

Views added to queues in Jira Service Management

We're introducing the ability to choose how you view work items (issues) in your Queues in Jira Service Management. Providing more flexibility to support how your team likes to track and manage their work, this upgrade means there are now three ways to view each of your queues: as a list, a board, or a calendar.

The current default view of your queues will be renamed to 'list view' and will become just one of the ways you can view the work items in each queue. You can have different views on each queue and any views that you add will appear as tabs, allowing you to easily switch between the different views.

You need to be a Jira or project admin to add or remove views from your queues.

Add a view to a queue

1. From your service project, go to Queues and select the queue to which you'd like to add a view.
2. From your queue, select the Add to navigation button. You'll find it in the tab bar between the queue name and the search bar.
3. Choose the view you would like to add, then select Add to navigation.

Once you've added multiple views to a queue, you can use the tabs to quickly switch between them.

Remove a view from your queue

1. From your service project, go to Queues, then select the queue from which you'd like to remove a view.
2. From your queue's tab bar, hover on the view you would like to remove, then select Tab options next to the view name.
3. Select Remove. You can add the view again at any time.
4. In the Tab options menu, you'll also have the option to edit the name of each view and change its position on the tab bar.

Customize the settings for each queue's views

The ability to customize each view for each queue can be managed from Queue setttings.

1. From your service project, select the More actions menu next to Queues, then select Queue settings.
2. In the Actions column, select Edit queue to access the settings for that queue.
3. Here you can access the general settings for your queue, along with the specific settings for the list, board, and calendar views if you have added those views to the queue.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

New Workato action in Jira Automation

We’ve built a new integration with Workato. The integration connects your enterprise stack with Jira Service Management, unlocking powerful use cases for both IT and business teams.

With the new Workato integration you can connect and run Workato recipes, allowing you to fetch information and take actions across hundreds of applications directly from Jira Automation via the Trigger Workato recipe action in your automation rule.

Before using the Trigger Workato recipe step or action for the first time, Premium and Enterprise Jira Service Management Cloud customers will need to create a connection with Workato by:

1. Generating a Developer API token and a Platform API/auth token from Workato.
2. Using these credentials to create a Workato connection from Jira Automation.

You can create a connection with Workato by creating an automation rule that uses the Trigger Workato recipe action. This action triggers a Workato recipe that runs at a specific point in an automation rule. You can use smart values to access Workato request response data in subsequent rule actions.

Read how to create a Workato connection from Jira Automation

Read how to set up the Workato action in your automation rule

Connect and manage on-call schedules in Slack

You can now connect on-call team schedules to your team's Slack channel and receive notifications about any changes to on-call shift changes.

While connecting the on-call schedule to Slack, you can also set up an alias like !Hello that can be used to tag or @mention the current on-call member in a message. It lets you easily see who's on call and notifies the on-call member.

To link a schedule to your team's Slack channel,

• Run the command /jsmops oncall on the channel and click Connect schedule.
• Alternatively, you can run the command /jsmops connect schedule to start connecting the schedule.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

We've launched a new prioritization project template

When you set up a new project in Jira, you can use project templates. There are many to choose from, including specific templates from different apps like Jira Product Discovery and Jira Service Management.

We've just added a new template for projects that are all about gathering ideas and prioritizing them. With this new prioritization template you can list ideas and add data to them. You can then use this data with common frameworks (such as RICE) to prioritize. The project has multiple views, like an effort and impact matrix, list, or roadmap view, so you can see and share your priorities in a way that suits you.

Anyone who has Jira Product Discovery and permission to create projects can use this template.

Add knowledge from Confluence on a different site

To make it easier for service teams to add more knowledge to their service projects, it’s now possible to link Confluence spaces on a different site (within your organization) to your service project. On linking Confluence spaces to your project, your agents and customers will be able to access knowledge articles within work item view, portal, and help centers.

To link a space from Confluence on a different site:

1. From your project, go to Project settings, select Channels & self service, and then select Knowledge base.
2. Select Add knowledge.
3. Select Confluence as your knowledge source.
4. Select a site of your choice.
5. Select the space you want to link to your project.
6. Select Link.

Trigger an Automation rule during a virtual service agent conversation

Use the new run Automation rule step to trigger Automation rules during virtual service agent conversations!

Your customers won’t notice when an Automation rule is run – it all happens in the background while they're chatting with the virtual service agent.

Find out how to run an Automation rule in a conversation flow

Introducing the Fields page in team-managed projects

With this change, project owners need to add a field to the Fields page in team-managed projects before they can use it in a work item layout. You can read more about this process in our documentation.

If you've seen this message before, you're not alone: this feature was announced a few months ago in the Jira community. The main difference is that now it's rolling out to all sites.

There’s a small chance that this may cause some Jira Automations to fail. To resolve this, you’ll need to add the fields to the team-managed projects included in your automations.

See the Premium features in-product before starting a trial

We're introducing a new and faster way to understand and upgrade to Jira Service Management Premium trial. Whenever you choose to upgrade to Premium or start a trial, you will see a modal which lists all new features available to you.

Unblock customer’s email address directly from your project

You can now unblock a customer’s email address directly from your project if their email address is added to a suppression list. Unblocking email addresses without having to reach out to Atlassian support ensures that your team can provide smooth and timely service to customers.

To access this feature, from your service project, select Customer notification logs, and go to Request notifications.

If a notification is undelivered because the email address is blocked, you’ll see an option to unblock the email address. Once you select Unblock email address, your customer will start receiving new email notifications again within an hour.

Configure fields directly from All work

Introducing inline field configuration in All work, giving you greater flexibility and control over how you use and manage your view.

Now, it’s more intuitive and efficient to add, edit, and create fields directly from the All work tab.

1. Navigate to the All work tab.
2. Hover between columns. Select Add to include new fields.

If you’re a team-managed project admin:

1. Select + Create field to define new fields inline.

Playbooks in Jira Service Management

You can now use playbooks to create clear, step-by-step instructions and automated rules for resolving issues. Similar to Standard Operating Procedures (SOPs), playbooks help standardize and optimize your issue resolution processes. Read more about playbooks.

To view a list of playbooks, go to Project settings > Playbooks.

Click a playbook to open it, or create a new playbook using the Create playbook button.

Filtering is now available in the summary view

We’ve added filters to the summary view so you can customize your view with the information that’s most relevant. You can filter by the following:

• Date range (for when work items were updated, created, or due)
• Assignee
• Work type
• Status
• Parent
• Priority

To try out filtering on the summary view:

1. Start in your Jira project.
2. Select Summary.
3. Select Filter.
4. Choose a filter and select the data you want to see in the summary view.

Use custom fields as filters in alert processing rules for Syncs

In alert processing rules, you can currently only apply conditions using predefined fields in the alert configuration. This limitation sometimes prevents you from using custom or user-defined fields from these tools as filters. With this new feature (previously available for different types of integrations), you can also use custom fields in Syncs, and Jira Service Management-Jira Software Cloud integrations as filter criteria when setting up your alert processing rules.

We're making it easier to compare plans during a trial

When you're in a trial, you can now click on the trial button in the top navigation and see the plan options available to you. This way, it'll be easier for you to understand the plan that is best for your team based on the features that plan includes. You can also easily upgrade and pay from the plans page.

Automation rules triggered by old incoming webhooks are now marked with warning icons for visibility

We’ve added a new feature to Atlassian Automation to help you easily identify rules that were recently triggered through a legacy incoming webhook. Now, when you open the rule list in Jira or Confluence Automation, warning icons will appear next to rules that are triggered through a legacy incoming webhook endpoint. For these rules to continue working after 30 May 2025, you’ll need to make updates in the connected applications which trigger them.

Please note - the warning icon will continue to be shown 14 days after the rule was last triggered through the legacy endpoint, even if you have updated your connected applications to use the new endpoint. The icon will disappear once 14 days has passed without the rule being triggered through the legacy webhook. You can confirm when your rule was last triggered by viewing the ‘latest call’ timestamp next to the legacy URL.

If you have already made updates in your connected application to use the new endpoint, but there are still requests coming through the legacy endpoint, this may indicate there’s more than one application using the webhook trigger in the same rule. You can confirm if this is has happened by looking at the ‘latest call’ timestamp next to both the legacy and new URLs. In this case, find all the applications connected to your rule and replace the URL and secret in all of them.

To get started with this feature:

1. Open the automation rule list in Jira or Confluence.
2. Click on the ‘Trigger' filter and select the ‘Incoming webhook’ filter. All rules triggered by an incoming webhook will be shown. These rules need to be updated before 30 May 2025.
3. Within these filtered rules, any which have recently been triggered through a legacy webhook will have a warning icon next to their name. This shows which rules are actively using the legacy URL. To learn how to update these rules, you can read our support documentation.

Get notified when email requests fail

Project admins now receive notifications right in their inbox whenever emailed requests are not processed successfully. This proactive means of communication ensures that admins are informed timely of failed email requests or connection issues with email accounts connected to their project.

By default, notifications are sent to all listed admins of a project. There is also an option to send these notifications to a specific email address instead of all admins.

In cases where self-signup is disabled or a customer doesn't have access to a service project, we will also notify customers so they are aware their request was not processed.

To specify who receives these notifications for your existing connected accounts:

1. From your service project, go to Project settings, select Channels and self service, and then select Email.
2. Select Edit against the required email address.
3. Enter the email address of your choice in Error notifications email address.
4. Select Save.

Filters added to project summary

Filters have been added to the project summary page, so you can customize chart data to show the information that's most relevant to you. Read about the project summary page in Jira Service Management.

Navigate to your service project, then select Summary in your project’s sidebar. You’ll see data as long as you have at least one assignee, and any number of work items in your project.

Between the page title and key metrics are filters similar to those on the list, board, and calendar views of your Queues. You can use filters like Status, Assignee, and Created to filter your chart data.

Bulk connecting Rovo connectors

We've made it easier to see and connect to all the connectors that are available to Rovo users, so you can get the most out of your Search.

To get started, select the connect banner in the top of quick find to see and connect all your available Rovo connectors.

Journeys chart added to project summary

A new Journeys chart has been added to the metrics and charts that can be found on the project summary page. Read about the project summary page in Jira Service Management.

Navigate to your service project, then select Summary in your project’s sidebar.

At the bottom of the page, you'll see the Journeys bar chart showing the count of in-progress journeys by journey name.

• Note that you'll only see the Journeys chart if Journeys is available in your project. Read more about journeys.
• If Journeys is available but you are yet to create or run any journeys, you'll see a placeholder for the chart with a message that there's no journey data available. Create and run some journeys to populate the chart with data.

Avoid accidentally deleting work items

We’re changing the way Premium and Enterprise users delete work items to help avoid accidental deletions. When you attempt to delete a work item, you can now choose to archive it, or confirm that you want to delete it.

Project summary page enabled in all newly created service projects

The project summary page in Jira Service Management is now enabled by default for all newly created service projects. If it is enabled in your project, you’ll see Summary in the sidebar under your project’s name.

To view the project summary, navigate to your service project, then select Summary in your project’s sidebar. You’ll see data as long as you have at least one assignee, and any number of work items in your project. The more people and requests in your project, the more insights you’ll be able to make use of.
Read about the project summary page in Jira Service Management.

Jira and project admins can enable your project’s summary page from the Feature lab. Once enabled, the project summary page can be viewed by both admins and agents.

1. From your service project, go to Project settings, then select Features.
2. On the Features page, look for the Feature lab heading and find the Project summary toggle.
3. Use the toggle to turn the feature on (or off).

Create and manage email templates for stakeholder notifications

Jira Service Management Premium and Enterprise users can now save time and customize stakeholder notifications on the go with email templates.

Email templates provide an easy and efficient way to customize stakeholder notifications. They eliminate the need to draft new emails from scratch, especially when teams are responding to incidents, allowing for quick customization and notification. Templates ensure consistent messaging by structuring emails to include all necessary information. You can also use predefined placeholders and dynamic fields, which help minimize the likelihood of omitting critical details.

To create an email template:

1. Go to Settings, then Products.
2. Under Jira Service Management, select Incident management.
3. Go to Email templates.
4. Select Create template.
5. Type in name, sender and reply address, upload header image, if any, and type in the email body.
6. Select Save template.

Find out more about creating and managing email templates.

New option added to the delay action in Atlassian Automation

We've added a new option to the delay action in automation rules. Now, when you add the delay action to your rule, you can either specify the exact amount of delay that you want to occur before your rule runs (such as 5 seconds) or select a random period for the delay to occur over (such as between 3 to 10 seconds). Previously, you could only select a specific amount of delay, so the randomised option provides you with more flexibility in choosing when and how your rule is executed.

Add tags to alerts in Slack for better organization

If you're using the Slack integration with your alert management, you can now add tags to your alerts directly from Slack. This will help you organize, categorize, and filter your alerts based on specific criteria.

• To add tags to a new or an active alert, select the more actions menu (•••), then select Add tags.
• To add tags to a closed alert, select Add tags.

You can add multiple tags at once by separating them with commas.

A cleaner All activity tab in work items

We’ve updated the All tab in the activity section of each work item. This improves readability and reduces clutter.

It's easier to scan and understand updates in a work item’s history, at a glance:

• Entry grouping: Similar updates are now grouped together to reduce clutter.

• Modern UI: Improved alignment, formatting, and date presentation for a cleaner look.

• Progressive disclosure: Long descriptions and details are now collapsible, reducing excessive scrolling.

This more structured and intuitive layout helps you quickly access relevant updates without the overwhelming detail.

Jira: Improvements to the child work item panel

The child work item panel is faster to load and more responsive.
You now get smoother scrolling, better performance and real-time, instant updates (without needing to refresh).

Performance and reliability improvements for Assets in Jira Service Management

As announced last year, we’re rolling out several changes to the Assets platform in Jira Service Management designed to improve the system's overall performance and reliability. This includes adding new limits and removing support for several AQL operators, functions, and endpoints. See the following Changelogs for more details:

https://developer.atlassian.com/changelog/#CHANGE-1739

https://developer.atlassian.com/changelog/#CHANGE-1915

https://developer.atlassian.com/changelog/#CHANGE-1905

https://developer.atlassian.com/changelog/#CHANGE-1906

https://developer.atlassian.com/changelog/#CHANGE-2198

Jira: Introducing an improvement to attachment previews

Introducing Grid view for attachments.

This change improves the organization and visualization of attachments.

Attachments appear in a grid view rather than the strip view and list view. You'll still be able to switch to another view, and save that as the default if you prefer.

Grid view helps you to more easily navigate through your content.

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

Make a copy of the playbook

Want to create a playbook similar to an existing one? You can now use the Make a copy option to duplicate the existing playbook and tailor it to your needs.

To make a copy of an existing playbook:

1. Open the playbook in edit view, then click Make a copy from the More options (⋯) menu. This creates a duplicate of the current playbook.
2. Update the playbook as needed and rename it.
3. Click Create playbook to save it.

Jira: Making the status of work items more prominent

The status of a work item will now appear between the title and description of each work item.

phantom-3037-playbooks-admin-navigation-spotlight

You can now use playbooks to create clear, step-by-step instructions and automated rules for resolving issues. Similar to Standard Operating Procedures (SOPs), playbooks help standardize and optimize your issue resolution processes. Read more about playbooks.

• To view a list of playbooks, go to Project settings > Playbooks.
• Click a playbook to open it, or create a new playbook using the Create playbook button.
• To control the visibility of playbooks, go to Project settings > Features > Playbooks. By default, playbooks are visible.

You must have project admin permissions to view and access playbooks.

Subscribe to your change calendar and explore the new filters

We’ve made major improvements to the change calendar to help you stay on top of change events and avoid conflicts across your services, Assets objects, and teams.

Subscribe to change calendar from your external calendar
You can now generate an iCal link and subscribe to your change calendar from apps like Google Calendar, Apple Calendar, and Outlook. This lets you stay updated on change activity without logging into Jira Service Management.

New JQL filtering in change calendar
Use JQL to filter work items shown in the calendar view. Filter by affected services, affected Assets objects, change types, or any custom fields, so you can focus on exactly what matters.

Show or hide change events by type
Choose which types of change events to display on the calendar, including freeze windows, maintenance windows, and standard work items.

Link your change calendar with affected services and Assets objects
You can now select affected services and Assets object fields when creating a new change window. This helps surface change conflicts more clearly and ensures better risk insights for service-dependent work. Read how to connect Assets schemas with changes

Generate a subscription link directly from your change calendar following these steps:

• Navigate to Operations > Change calendar in your service project.
• Select Subscribe to change calendar icon in your toolbar.
• Choose the event types and calendar format, then generate your calendar link.
• Paste the link into your external calendar app (Google, Apple, or Outlook). Read more about subscribing to change calendar

Once subscribed, you’ll automatically see any future updates to change events in your external calendar.

You don’t need to take any action to start using the new filters or event fields. They’re already available in the change calendar and the change event creation form.

Set up operations from Your work

You can now easily set up operations from the Your work page in Jira Service Management if you haven't set them up yet.

With operations, you can empower your team to stay on top of alerts with advanced alerting and on-call capabilities.

* Integrate your apps and keep alert data in sync

* Route alerts to the right people


• Create and manage on-call schedules to respond to alerts faster

Additional fields now editable in the All work list view

You can now edit Confluence items and linked Goals from the All work list view.

Confluence items and comment summaries are also now included when exporting work items to CSV or HTML.

• In the All work tab, view work items in list view.
• Select Configure columns in the column bar to add the Confluence items or Goals fields to the list view.
• They can now be edited directly in the list.

Enable your project summary page in Jira Service Management

For projects that have never had the project summary page enabled, admins will see a prompt that provides information about the summary page, with the option to enable it in one step. Read about the project summary page in Jira Service Management.

Jira and project admins can enable a project’s summary page from the Feature lab. Once enabled, the project summary page can be viewed by both admins and agents.

1. From your service project, go to Project settings, then select Features.
2. On the Features page, look for the Feature lab heading and find the Project summary toggle.
3. Use the toggle to turn the feature on (or off).

New 'offer options' standard flow in the virtual service agent

We heard your feedback about the escalate standard flow creating too many work items, so we've introduced a new standard flow, called offer options. Depending on the situation and the channel, offer options is sometimes used instead of escalate.

Offer options is configurable, and lets you choose 1–3 options to present to your customers. These appear as buttons:

• Raise a request starts the escalate standard flow, which lets the customer know a request has been raised and creates a work item.
• See search results takes the customer to the relevant portal, and shows search results based on their first message in the conversation.
• Ask another way tells your customer to try rephrasing their question.

Read more about the 'offer options' standard flow, or find out how to configure 'offer options' in the virtual service agent.

Refined drag and drop experience in the work item

We’re refining the drag and drop experience in the work item to make it more consistent and intuitive across different views in Jira.

We’re running an experiment with two variations.

Reorder starred projects in the sidebar navigation using drag and drop

You can now reorder the starred projects in your sidebar navigation to more easily organize your projects according to your preferences.

Here's one way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Hover over the starred project you want to move.
3. Drag the project to your desired position.
4. Drop it to set the new order.

Here's another way you can reorder your starred projects:

1. Navigate to the sidebar in your project.
2. Select the More actions for the starred project you want to move, then select Move in sidebar.
3. Select where you'd like to move it in the order.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Create and reorder work items faster in the All work tab

We’re rolling out sibling create and drag and drop re-ranking in the All work tab, so it’s easier to structure and prioritise related work items without switching views.

You can now quickly create a new work item at the same level (a sibling), and re-rank work items by using drag and drop (select and move) when sorted by rank.

Now available for both team-managed and company-managed projects in the All work tab.

Key benefits:

• Plan faster by creating structured work items in context.
• Prioritise quickly with drag and drop (select and move) ranking.
• Avoid unnecessary actions and switching views.

1. Go to the All work tab.
2. Check that your view is sorted by Rank.
   1. Select a work item, then drag and drop (move) to reorder based on priority.
   2. Select a work item, then + Sibling to create a related work item.

Jira: Collapsible sections in work items

You can now collapse sections in a work item view to reduce scrolling and highlight key information.

To use collapsible sections:

1. Open a work item in Jira.
2. Find the section you want to collapse, such as Description or Activity.
3. Select the chevron or section title to collapse or expand it.

Due date notifications now available

As the assignee of work items that are overdue or due today, you'll now receive daily notifications within Jira and via email. Each notification links to a pre-filtered page showing your overdue and due work items. Manage your due date notification preferences by:

1. Select your profile image at the top-right navigation.

2. Select Notifications, then you can manage how you receive notifications for overdue work items.

For more details, join the conversation and provide feedback on our Atlassian Community.

Easily spot your company's top priorities with one focus area icon

All focus areas now share the same icon. We thought having different icons for each type would make things easier, but we got feedback that using words to communicate the type was more effective. If you hover over a focus area icon, you can see the name of the Type in the tooltip. If the focus areas are displayed in a table, you'll see a Type column and can filter by the focus area type.

Parent link and Epic Link fields have been removed from the Board view

With this update, the Parent Link and Epic Link fields can no longer be shown on your board. This is part of our work to combine the two fields into one unified field called Parent field. Read our community post about this change

In a previous change, these fields were converted to read-only fields, and the values ported into the new Parent field. This update removes the ability to view this old data.

Jira: A wide view for work items

Reduce visual clutter and surface essential details only by switching your work item to the wide view layout.

To switch your layout:

1. Open a work item in Jira.
2. Select Switch layout.
3. Choose Wide view.

Parent link and Epic Link fields have been removed from CSV export

With this update, the Parent Link and Epic Link fields are no longer included in CSV or HTML exports of Jira work items. This is part of our work to combine the two fields into one unified field called Parent field. Read our community post about this change

In a previous change, these fields were converted to read-only fields, and the values ported into the new Parent field. This update removes the ability to view this old data.

Improve visual and hierarchy of the Quick actions menu in the work item

We’ve improved the Quick actions menu in the work item with a cohesive visual look, and better action hierarchy and grouping, making it easier for you to find and use the tools you need.

We’ve also added Goals and recommendations to the menu.

Open a work item and select the Add button under the summary.

Jira: Select a work item from the Summary column in All work

The Summary column in the All work tab now includes Select work item.

1. Go to the All work tab.
2. Hover over the Summary column or focus on Select work item by pressing the Tab key.
3. Select to open the work item view.

Import workflow from Marketplace feature has been deprecated

With this release, users will no longer be able to import workflows hosted in marketplace apps.

Update more fields with AI triage

You can now update additional fields such as Priority and Assignee while triaging work items in your queues. When you triage work items, AI will suggest values for priority and assignee. If the suggestions don't match what you need for your work items, you can select more suitable values from the list and continue the bulk update.

Opsgenie on-call is moving to Jira Service Management

Atlassian ended new sales of Opsgenie on June 4, 2025, and will end support on April 5, 2027.

With this change, we’re moving to a better alerting and on-call experience with Jira Service Management, which offers advanced incident response capabilities including AI-powered automation and streamlined workflows to fully support your team’s operations.

To continue using on-call features and access a range of powerful new capabilities, move to Jira Service Management.

We’ve made looking up Assets objects in Automation easier

You can now use filters to generate an AQL query when using the Lookup objects action in Automation. Simply select Basic to choose an object type plus any attributes, and an AQL query will be generated for you. This query will use attributes as placeholders for you to then customize with relevant smart values. The results of this query can also be used in other Automation actions using the lookupObjects smart value. Read more about using smart values for Assets.

Improvements to the Fields pages in Jira Admin - Part 1

We're rolling out the first phase of our improved fields management experience in Jira that we announced in the Atlassian Community at the start of June. Our post outlines the full list of changes as well as how this fits into our larger plan. The Atlassian Community is also where we'll share updates, announce future changes in full detail, and engage with the community to make sure we're delivering an experience that meets your needs.

This first release includes changes that make field management simpler and more efficient for Jira admins, such as a redesigned Fields page (formerly Custom fields) that now shows fields created by Jira or plugins (i.e., System fields). You can also create and add new fields to configuration schemes without leaving the page, and filter and sort fields based on Field category type.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

Add knowledge from third-party products

To make it easier for service teams to use knowledge in external products to resolve and deflect requests, it’s now possible to link folders in Google Drive and Microsoft SharePoint to your service project. After you’ve linked folders, people can access documents from linked folders within the work item view, portals, and help centers after authenticating their account.

Before you begin:

• Activate Rovo and AI for your organization.
• Connect external products to Rovo.

Read more about adding knowledge from third-party products

Mark completed step as undone in playbooks

You can now mark an instructional step in the playbook as undone, even if it was previously marked as done. This helps indicate that the step still requires action. The step’s status history is available in the Execution log for reference.

Attachments now supported for the 'Send customized email’ action in Automation

We’ve introduced the ability to add attachments to emails sent as part of your automation rules.

Once a rule has been saved or enabled, you’ll be able to upload files as part of the email content. When the rule executes, any uploaded files will be included as attachments to the emails that are sent.

This capability will be available when using the Send customized email action as part of your Jira automation rules, and will become available for use in other Atlassian apps in the future.

Read more about the Send customized email[ action in Automation.|https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Send-customized-email]

This highly-requested update includes:

• Attachment support: You can now add attachments (in most file formats up to a total of 5MB) to your automated emails.
• Secure storage: All attachments are stored securely in Atlassian’s media platform, ensuring reliability and compliance.
• Easy preview: Once uploaded, you can open a preview of an attachment by selecting a card in the Attachments field.

To add attachments to your automated emails:

• Add the Send customized email action to an automation rule, then fill in the email details in the Settings tab.
• Select the Content tab, then from the Attachments field browse or drop the files you want to attach to the email.
• Select Update.

Note that the rule must be saved or enabled before you can add attachments to the email action.

Jira Plans - View your calendar one week at a time

When looking at the Calendar view in your plan, you can now isolate to see one week at a time.

Prompt inactive Confluence users to create content from work items

We're introducing a feature that encourages inactive Confluence users to create content directly from Jira work items. This feature targets users who haven't been active in Confluence for the past 28 days and belong to sites that have had Confluence for more than 14 days. When these users view certain Jira work items, they'll see a suggestion to create a relevant project document in Confluence.

To start using this feature:

1. Open a Jira issue of type epic, story, or bug.
2. Look for the Confluence content section.
3. Select the suggested template to create a project document in Confluence.
4. Follow the prompts to complete and publish your document.

The legacy Microsoft Teams connector has been deprecated in Atlassian Automation

As of today, all automation rules that use the legacy Office 365 connector webhook in the Send Microsoft Teams message action can no longer be saved or updated, until they are migrated to the new Microsoft Teams workflow.

To update your automation rules:

1. Go to your Teams channel and select … > Workflows > Post to a channel when a webhook request is received.
2. Copy the new webhook URL.
3. Paste this URL into the Send Microsoft Teams message action in your automation rule.
4. Save your rule.

New suggestions in search box

We're introducing some new personalised and smart suggestions when you open the search box, but before you begin to type. These will more easily help you find information relevant to you.

We're deleting unused field associations

Starting today (June 16, 2025), we’re beginning the process of removing unused field associations from your field configuration schemes. We expect this process to take several weeks from today. Once finished, this will improve the performance and stability of your Jira instances.

If this causes any issues in your projects, we have documented the steps for adding fields back in this Atlassian community announcement. The page also covers how we determine which associations to delete. If you have any questions about this scheduled deletion, you can ask them in the comments section of the linked announcement.

Delete, copy and export rules directly from the automation rulebuilder

We're excited to announce a new feature in Atlassian Automation that enhances your workflow efficiency. You can now quickly copy, delete, and export rules while in the rulebuilder. Previously, you could only complete these actions from the rule list.

This update aims to streamline your rule management process by reducing the number of steps needed to perform these actions. Whether you're setting up new rules or maintaining existing ones, this feature will help you manage your rules more effectively.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Control playbooks visibility using JQL

You can now use JQL in the playbook details section to control playbook visibility. This helps agents see only the most relevant playbooks, improving process efficiency and reducing noise. Read more about playbook details.

Enable Free access level in Jira Product Discovery

If your site is on the Free plan, as of November 15th, 2024, everyone with creator product access will be a project admin. The access permission scheme cannot be changed.

Connections between different type of ideas

You can connect ideas through connection fields, such as connecting an opportunity type of idea to a solution type of idea. These relationships don’t have a predetermined hierarchy, but you can visually represent one in your views by playing with filters, grouping, and fields.

See linked ideas inside the Jira issue view

The new ideas section inside the issue view enables you to see linked ideas and also search and link existing ideas from within an issue.

1. In Jira Product Discovery, select an idea, and on the right-side panel, click Delivery.
2. Create or link an issue to the idea and then go inside the issue view. You can now see a section for ideas.
3. Click the idea to display its details on the right-side panel.
4. In the issue view, click and search existing ideas that you might want to link to the issue.

Pin fields for ideas

You can now pin fields for ideas. This enhances the integration between Jira Plans (Premium) and Jira Product Discovery. Users can preview ideas directly within Plans, and hovering over an idea shows all fields pinned to it, providing a more seamless and informative experience.

To use this feature, the user needs to:

• Have access to Jira Plans and Jira Product Discovery.
• Have an Ideas column and have something pinned for these ideas.

Copy project configurations to create new Jira Product Discovery projects faster

We’re excited to introduce a new way to speed up project setup in Jira Product Discovery. When creating a new project, you can now reuse the configuration of an existing project instead of starting from scratch.

To reuse a project configuration:

• Go to Create project > Product Management.
• Select Reuse a project configuration.

Read more about creating Jira Product Discovery projects.

New inline edit option for roadmaps

You can edit ideas inline on any roadmap view.

Configure your financial year dates

Jira Product Discovery allows you to play with the timeline's time scale by enabling you to select the start date of your year.

Once you have updated the dates, you can always change them again by accessing the configuration options through the timeline settings panel. Click the dates in the timeline header and select Edit next to The year starts in…

The change is also reflected in the date fields. To change a quarter, select the date field name and make the changes in the menu.

Idea types

You can now create your own type of ideas such as a user problem, a customer, a bet, an opportunity, or a solution.

Before you begin

• You must be a Creator with Administer project permissions.

Steps

1. Next to your project name, select (…) > Project Settings > Types.
2. Click +Add type, select an icon and enter the type name, then Save.

Team field support update

You can now use the Team field in Jira Product Discovery and see it in Jira when you open a linked idea.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Improved Database Creation: Templates & Import Options

Templates and import options are now organized into separate tabs, making it easier to start a new database. You can select from an expanded library of over 11 templates or import your own data.

Open the database creation screen and select either the Templates or Import tab to select your preferred method.

Add AI descriptions to dynamic cards

Dynamic cards now feature AI-generated descriptions. When you use dynamic cards in Company Hub or Confluence, you can now have a summary of the content added to the card.

AI-generated summaries can contain errors or inaccuracies. The use of AI in dynamic cards is optional and can be turned off.

Descriptions are now enabled by default on new dynamic cards elements. To remove the AI-generated descriptions, select the element, then the pencil icon to edit settings. Turn the Description toggle off.

Editor: Dynamic AI button in toolbar

The AI button in the Confluence editor toolbar now adapts based on your selection. If you select three or fewer words, you'll see the Define option instead of Improve Writing. This change enhances the toolbar's functionality for concise selections.

To experience the new AI button functionality:

1. Open any content type in Confluence.
2. Select three or fewer words.
3. Observe the AI button in the toolbar offering the Define option.

Catch up quickly with page comments summary

Now, Atlassian Intelligence can summarize page comments for you, making it easier and faster to catch up on important feedback. Just navigate to the bottom of the page, above the first page comment, and select Summarize comments.

New comments since you last checked? Select the refresh icon to generate a summary that includes all the latest feedback.

A better way to browse, preview, and select page templates is here

From a blank page, page templates can now be previewed with improved clarity and context. Users can also browse all template options, or undo a template selection if need be, with greater ease.

Create Confluence whiteboards directly from your Jira backlog

With Confluence whiteboards, you can plan freely and execute quickly. Create a whiteboard directly from your Jira backlog, copy backlog issues to the whiteboard, and plan however you want.

Here are some suggestions for things you can do with Confluence whiteboards:

• Use award-winning templates such as a prioritizing and planning matrix
• Import Jira issues directly into your new planning whiteboard
• Link sticky notes and issues to show dependencies and timelines
• Turn sticky notes into Jira issues
• Engage teammates with real-time, group editing
• Collaborate using stamps, timers, and more

If an admin has three or more issues in their backlog, they'll see the button that allows them to add Confluence and start using a whiteboard. Once a team has Confluence, anyone with access to Confluence — including admins and end users — will see the button on their backlog that allows them to create a whiteboard.

You can remove this button anytime by turning off all product recommendations at in your Jira settings. Note: if you add Confluence and then turn off product recommendations, you will lose this button.

Enhanced inline commenting

You can now comment directly on inline elements such as emojis, statuses, mentions, dates, and inline cards (Smart links). Users can now leave comments on these specific elements, streamlining the commenting process and making it more intuitive and efficient for providing feedback and collaborating on documents.

Blogs are moving

To help you keep your spaces clean and tidy, we're hiding blogs for new spaces and current spaces where blogs aren't being used.

For all other spaces, we're moving blogs into the content tree so they're close to the rest of your work. You can find them in their own section, below Content.

To turn blogs back on, or turn them off if you're no longer using them:

1. Navigate to the space, then select Space settings.
2. Under Manage space, select Features (only space administrators have this option).
3. Select the toggle next to Blogs to turn them on or off.

Add hyperlinks to whiteboards

Hyperlinks can now be added to whiteboards text.

Easily share links with your collaborators on a whiteboard through free text or text within an element. Hyperlinked text will appear blue.

A unified way to share and manage access to content

Confluence sharing and access just got a revamp. It’s now clearer who has access to content and who needs access and how to give it to them. It’s also easier to distribute content, with more control over when and how you send notifications.

You can find visuals and a video walkthrough of the new experience in the announcement in Atlassian Community.

Prevent people from downloading attached files

Data security policies allow you to use rules to control how users, apps, and people outside the organization interact with content in Confluence and Jira.

We’re extending the data export rule to also block the downloading of files attached to Confluence and Jira. After this rule takes effect, users will no longer find a download button in sections like the attachment list, macros, and file previews.

We opted to extend the data export rule rather than introduce a new one because of the considerable overlap between export and download. Our findings showed that the types organizations needing to block exports also wanted to prevent attachment downloads.

This change will affect any existing policies that have configured the data export rule to block exports.

The data export rule requires Atlassian Guard Standard.

To check whether your data security policies currently block exports:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.
3. Select a policy, and check whether exporting data is blocked.

We've simplified space creation

With just two kinds of pre-set spaces, each made to suit a specific purpose, creating a space is easier than ever before. Choose between Knowledge base and Collaboration, add a description to the overview, and dive into content creation faster than ever before with one of our suggested templates. Or, if you know you want something really specific, choose Custom to manually configure the features and settings for your space.

To read about these changes in more detail, check out the Community post.

To create a space:

1. Select Create from the Confluence navigation bar at the top of the screen.
2. Select Space from the dropdown menu.
3. Choose the option that best fits the purpose of the space you're creating.
4. Confirm your choice, making changes to the defaults as needed.

Creating a Jira issue can now trigger an automation in Confluence

We're adding a new trigger to Confluence automation that will let you run a rule when a new issue is created in a specified Jira project.

Space and product admins can build a rule by navigating to a page and selecting the Automation (lightning bolt) icon.

1. Select Issue created in Jira as your trigger.
2. Select Connect to connect Confluence to your Jira project.
3. If your organization has multiple Jira sites, you will need to select a Jira site from the Create connection menu.
4. Select one or more projects from the dropdown menu.
5. Continue to build your rule.

Whiteboards voting improvements

Run more flexible voting sessions in Confluence whiteboards with anonymous voting and the ability to mark yourself as done.

You can also delete old voting sessions, and hide votes on the whiteboard as needed.

Summarize changes to a page or blog post

Now when Premium and Enterprise customers visit a page for the first time in a while, they can use Atlassian Intelligence to generate a brief summary of changes since their last visit. Use this feature to quickly catch up on changes to a project plan after an important review, or to get a sense of what you missed while you were on vacation.

Atlassian Intelligence will only generate a summary if someone has edited the page since your last visit. If there aren't any changes to summarize, it will present you with a summary of the page to help you refresh your memory on the key points.

Atlassian Intelligence is available to all customers with Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

To summarize changes using Atlassian Intelligence:

1. Navigate to a Confluence page or blog post that you’ve visited before.
2. Select Summarize changes from the drop-down menu in the Summarize button on the top right.
3. Atlassian Intelligence will generate a summary of changes since you last visited the page or post.

You can copy the summary to your clipboard, rate the quality of the summary, and provide feedback on the feature using the buttons at the bottom of the summary panel.

Page previews are better than ever before

Premium and Enterprise customers will see a new and improved page preview when they hover over a page title in the content tree. This preview will contain a sampling of three short sentences taken from the page, selected and ranked for relevance by Atlassian Intelligence (AI).

Because this feature uses Atlassian Intelligence (AI), it is only available to customers on the Premium and Enterprise plan. There won't be any change to page previews for Free and Standard customers.

A streamlined setup experience for new Confluence users

We've updated the setup screens for teams and spaces in Confluence to make the onboarding process smoother for new users. This change simplifies the experience for those joining a team, making it easier to get started with Confluence.

Prevent people from using public links in specific spaces

Data security policies allow you to use rules to control how users, apps, and people outside the organization can interact with content such as Confluence pages and Jira issues.

You can now use the public links rule to prevent people creating and accessing public links in particularly sensitive Confluence spaces. Previously, this was only available for policies that covered classification levels or entire Confluence instances. How the public links rule works

The public links rule requires Atlassian Guard Standard (formerly known as Atlassian Access).

To create a new data security policy or view existing policies:

1. Go to admin.atlassian.com. Select your organization if you have more than one.
2. Select Security > Data security policies.

Creating Jira issues from Confluence is easier than ever with Atlassian Intelligence

Use Atlassian Intelligence (AI) to automatically generate issue summaries and descriptions when you create multiple Jira issues from a Confluence page.

This feature is only available to customers on the Premium and Enterprise plan.

To use Atlassian Intelligence to create Jira issues from Confluence:

1. Select the AI button on the bottom right of the page, then select + Create Jira issues. Confluence will generate a list of issues for you in the right side panel.
2. Hover over an issue and select the pencil icon to review the summary and description for accuracy, make any necessary changes, and add additional information as needed.
3. Select Create to save your changes and create the issue in Jira or Cancel to discard changes.
4. To remove an issue from the list, hover over the issue and select the X.

Create Jira issues from tables

We’ve made it easier to create Jira issues from tables on Confluence pages. Just highlight the relevant rows in your table and select “Create Jira issues”. We will generate a preview of your Jira issues and automatically prefill the issue description and summary using your highlighted text. You can then edit, delete or create the issues.

Confluence: Import multiple Miro boards

You can now easily import multiple Miro boards into Confluence, transforming them into editable Confluence whiteboards. This feature streamlines the process of migrating your content from Miro to Confluence.

To import your Miro boards into Confluence, anyone with create space permission can:

1. Navigate to the Confluence space where you want to import the boards.
2. Select the option to import Miro boards.
3. Follow the on-screen instructions to upload your Miro boards.
4. Confirm the import to complete the process.

Better database indexing to improve search results

We're making it easier to find information in Confluence by including the content within databases in search results. Previously, searches only considered database titles, but now, the text inside databases will also be indexed, providing more comprehensive and relevant search results.

Shapeable lines in whiteboards

Create more customizable lines and connectors in Confluence whiteboards. Added drag handles on lines now allow you to create more complex and flexible lines for all your diagramming and brainstorming needs.

Start dragging to get started. As you shape a line, more drag handles will appear.

Editor AI: Generate titles on publish

We're introducing a new feature that automatically generates a page title using AI when you attempt to publish a page without one. This update reduces the need for inserting a title before publishing a page.

What's new:

• AI-generated titles on publish: Automatically suggests a title when you publish without one.
• User confirmation required: You can accept or edit the AI-generated title before finalizing.

Open Smart Links in new tab

Open embedded Smart Links from Confluence in a new tab with easy access.

Editor: Improved conversion of legacy pages to cloud

We're improving the experience for converting pages from the legacy editor to the cloud editor in Confluence. When you edit a page in the legacy editor that is fully compatible with cloud, you'll be able to convert it straight away. This will reduce the number of pages left in the legacy editor.

What's new:

• Conversion notification on edit: When you edit a fully compatible page created with the legacy editor, you'll be notified that it's ready to convert to cloud. This is only visible on legacy pages where 100% of the content is possible to convert.

Curved lines in whiteboards

Create curved lines and connectors in Confluence whiteboards, in addition to the existing straight and dynamic lines, for more flexible and customizable diagramming.

To create a curved line, select a line on the whiteboard, select Line type, and choose the Curved option. Then start moving the drag handles to shape the line however you like.

Change the assignee straight from Smart Link list view

Change the assignee using a Smart Link list without the need to open the issue.

What is Smart Link list view?

While viewing Jira issues in Smart Link list view, select assignee from one of the items. Once the dropdown appears, you can change the assignee straight from the cell.

Editor: Nested tables in Confluence

We are introducing support for nested tables in Confluence to address a key limitation in the cloud editor. You can now insert tables within tables up to one-level deep. This aims to assist migrations from the legacy editor to cloud, and improve content creation.

What's new:

• Nested table insertion: In the cloud editor you can now insert tables within tables, up to one level deep.
• Migration support: This feature aids in migrating content from the legacy editor, allowing pages with nested tables to be migrated to cloud.
• Improved editing experience: You can maintain complex table structures post-migration.

Rename your managed teams in Atlassian

Back in March 2025, we released Managed Teams for Premium and Enterprise customers. This allowed organization admins to sync an Atlassian team to a group to better control team information and membership, but this change meant the team name would change to match the synced group. Now, organization admins can change a managed team's name from the team profile and while staying synced to the group.

To change a managed team's name:

1. Go to the managed team's profile.
2. Select the team's name, or select the Team settings button.
3. Enter the new name you want to use in the Team name field.

Inbound and Outbound links now available for page analytics

Confluence page analytics now feature inbound and outbound link click analytics. Inbound link analytics show pages that link to the current page and how often users arrive through those links. Outbound link analytics show click counts and click-through rates for links included on the page.

Analytics data includes Confluence active pages and blogs after Jan 31, 2025. Deleted and archived aren't included.

To access page analytics:

1. Navigate to a page.
2. Select the "X people viewed" link in the page's byline.
3. The Analytics summary displays. Select Links to see a summary of the top outbound and incoming links.
4. Select View more insights to enter the fullscreen Analytics page and view the Linked content tab.
5. Choose between the outbound and inbound links and select a time range or a set a specific date range.

Whiteboards improvements

Improvements to Confluence whiteboards include the ability to:

• attach lines to the same shape and snapping lines to shapes to improve precision and complexity in diagrams
• drag sections from their title, smart sections won’t action on every load
• bulk import all Jira issues from a JQL query
• click on the zoom percentage to easily adjust zoom level

Improved error for Smart Links in the content tree

When we can’t render the link you’ve inserted as an embedded Smart Link in the content tree, you’ll see why it can’t be displayed, and you can navigate you to the original link.

Editor: Default image insertion update

We're changing the default behavior for image insertion in the editor to always insert images as blocks rather than inline. This update addresses user feedback and analytics showing a preference for block images, enhancing document layout and usability.

Default block image insertion: Images will now be inserted as blocks by default, improving document structure.

Import your Mural boards into Confluence whiteboards

Bring your Mural boards into Confluence whiteboards to collaborate seamlessly with your team. Convert your Mural content into editable, native elements within Confluence whiteboards and keep all your work organized in one place.

To import your Mural boards into Confluence whiteboards

1. In Mural, open the board you wish to export.
2. Open the export menu in the top-left corner of the board, then select Download mural, or right-click on your board’s background and select Download.
3. Select the PDF Format and the selection of content you would like to export (All content, Selection, or Outline).
4. Select Download and choose a location to save your file.
5. Navigate to the Confluence whiteboard where you want to import the PDF.
6. Drag your PDF into the whiteboard. You can also use the More menu in the toolbar at the bottom of the screen to select Whiteboard import and navigate to your file.
7. Select Mural as your content type to complete the import process.

Rovo Search can now filter by incidents

You can now use the Rovo Search 'type' filter to show only incidents from Jira Service Management (JSM).

Draggable line labels in whiteboards

Drag and reposition line labels anywhere on the line for greater flexibility and customization on your diagrams in Confluence whiteboards.

Find text easily within your whiteboards

Quickly find text within your whiteboards by using the familiar ctrl+f or cmd+f shortcut. This feature allows you to search for text across your board, making it easier to navigate and locate specific text elements without manually scanning through everything.

To use the new search feature in whiteboards:

1. Open a whiteboard and make sure to focus on the whiteboard.
2. Use ctrl+f or cmd+f to open the search menu.
   • You can also access the search feature from the top More actions (three dots) menu.
3. Input your search query into the search box.
4. Use enter or shift+enter to navigate through the search results.

Summarize differences between versions of a page

Now, Premium and Enterprise customers can use Atlassian Intelligence to generate a summary of differences between two versions of a page. This feature makes it easier to get a sense of what's changed between versions quickly.

Atlassian Intelligence is available to all customers with Premium and Enterprise plans. Organization admins can manage Atlassian Intelligence preferences from Settings > Atlassian Intelligence in Atlassian Administration.

To use this feature as a Premium or Enterprise customer:

1. Navigate to a page in Confluence Cloud.
2. Select ••• from the top right, then select Page history.
3. Select two versions to compare, then select Summarize differences.

Atlassian Intelligence will display a summary of changes made to the page between the versions you selected.

Third-party apps are now organized together and easier to find

From the More actions (...) menu of a page, you can now find and access third party apps from their own special section called Apps.

Updated endpoint for new rules containing incoming webhooks

We're updating the incoming webhooks trigger in Atlassian automation. All rules containing incoming webhook triggers will begin to be routed through more secure endpoint. This update is part of our continuous focus to uplift the security and reliability of Atlassian automation.

Starting today, all new rules created with incoming webhook triggers will automatically be routed through the new endpoint. Any existing rules will continue working as before, however, please note that further action will be required in the future, as these rules will also need to be routed through the new endpoint eventually.

What's next?

• We’ll be providing more information about how to migrate existing rules with incoming webhooks triggers over the next few weeks - this will be announced via community post and email, so keep an eye out for updates!
• Once this information is released, you’ll be able to update your existing rules so that they're routed through the new endpoint. We'll give you instructions on how to transition your existing rules to the new incoming webhook endpoint, and share further details about the eventual retirement of the current legacy webhooks.

View recent automation community posts

Version history now available for databases

You can now view and restore previous versions of your databases, giving you greater flexibility and control over your database content.

To view a database's history, open the database's ••• menu in the top right and select Version history.

From there, you can view previous versions of the database. You can restore a previous version by selecting it and then selecting Restore as new database. This will create a new database using that version’s content. Permissions on the new database will be the same as the original.

Editor: Select and drag multiple elements

We're introducing a new feature to the Confluence Cloud and platform editor that lets you drag and drop multiple selected elements. This update allows you to move multiple elements together using a drag handle.

What's new

• Multi-select drag and drop: You can now select and move multiple elements simultaneously by using the drag handle.

Validate additional fields input in Atlassian Automation

We're introducing a new feature that allows you to validate additional fields input in Atlassian Automation rules, including JSON syntax. This feature will help you to find possible warnings and errors that may impact your rule, so you can fix them before it runs. It'll be available across components that allow you to provide additional fields input, including the Create issue, Clone issue, Edit issue, Transition issue and Create incident actions.

You can also validate input containing smart values that are wrapped in double curly brackets, such as assignee.displayName. This feature has limited capacity to validate input that contains smart values without these brackets. We currently don't support validating input that only contains smart values (which may occur if you try to enter your JSON through smart values alone) or smart values sections.

To get started with this feature:

1. Open the Automation rulebuilder.
2. Select a trigger for your rule, plus an action that supports additional fields, like Create issue.
3. Enter your desired input into the Additional fields section.
4. Open the dropdown menu next to Turn on rule.
5. Select Validate rule.
6. Any errors or warnings found in your rule, including the additional fields, will be displayed.
7. Fix any errors or warnings before turning on your rule. Warnings don't need to be fixed before the rule is enabled, but we recommend resolving them as soon as possible, to ensure your rule will run as planned.
8. Select Turn on rule.
9. Your rule is now ready to use.

Learn more about additional fields in Atlassian Automation

Confluence: "Watch" all items in content tree

You can now watch all items within a content tree in Confluence. This update improves your ability to track relevant updates and changes effectively.

What's new:

• Watch items within content tree: Monitor sub-trees of nested content, including pages, whiteboards and databases.
• Simplified notifications: No need to individually watch nested content under its parent.
• Improved tracking: Stay updated with changes across all related content.

Improved mission control and analytics with live docs

We've enhanced mission control and analytics in Confluence by integrating live docs into all charts and analytics. This update provides a more complete experience for managing and analyzing your content.

To explore the new live docs feature in mission control and analytics:

Go to your Confluence space.

Access the mission control or analytics section.

View and interact with the updated charts and analytics that now include live documents.

Automate entire business processes with advanced automation rules

Add more functionality to your automation rule, allowing you to link multiple connected processes together in a single rule. This can help reduce the number of rules you need to maintain. We’re beginning with Advanced components such as Branch at the same time, which enables execution of multiple components in parallel. Rule groups enable execution of multiple components in specific segments.

Available for Cloud Premium and Enterprise editions only. Find the new Advanced component type available to select from after you’ve added a trigger to a rule and select +Add component.

Databases: Improved cell interactions

We're making it easier to interact with database cells by improving drag and drop functionality, updating styling for easier editing, and fixing bugs related to clearing behavior and menu interactions.

Loom AI-powered meeting notes in Confluence

When AI-powered meeting notes is enabled in Loom, a Confluence page containing the meeting recap, links shared in the meeting chat, and a recording link is automatically generated for each meeting recording and can be found in the user's personal Confluence space. The page is available when the meeting has ended, and is restricted to only meeting invitees.

If meeting recordings is enabled, users can turn on AI-powered meeting notes by toggling the "Generate meeting notes in Confluence" in their meeting recordings settings.

Visually organize ideas with mind maps in Confluence whiteboards

Mind map elements are now available in Confluence whiteboards. These are branching connectors between nodes that help you and your team visualize relationships between different aspects or subtopics of a central idea to brainstorm and structure information more effectively.

To use mind maps in Confluence whiteboards:

1. Open a Confluence whiteboard.
2. Select the "Mind maps" feature from the more (plus) menu in the main toolbar.
3. Start adding nodes and branches to create your mind map.

Editor: Legacy content macro for nested bodied macros

We’re introducing the legacy content macro to support the migration of nested bodied macros from the legacy editor to the cloud editor.

What’s New:

• Editable nested macros: You can now edit bodied macros nested within other macros on pages converted from the legacy editor to the cloud editor.
• Page conversion support: The legacy content macro automatically preserves complex nested structures during conversion from the legacy editor to the cloud editor.
• Note: Marketplace app macros that currently don’t support nesting in the legacy editor will not work when converting a page to the cloud editor.

Convert pages to live docs in bulk

Space admins can now use content manager to convert pages to live docs. Live docs allow collaborative real-time editing without the need to publish.

1. In the left navigation bar, select the more actions menu in the space's name, then select Space settings.
2. Select Content manager.
3. A list of all space content displays. Select one or more pages.
4. A toolbar opens at the bottom of the screen. Select Convert to live docs.

You will see a progress bar and success message in the bottom left part of the screen.

New navigation: A faster way to find work

Key parts of the top navigation have moved to the sidebar, giving you access to multiple spaces at once. The new navigation is centered on customization capabilities and ease-of-use improvements, including:

• A customizable sidebar you can personalize to the unique way you work

• Expand or collapse sidebar options to maximize screen space when needed

• Navigation across all spaces and space settings for admins

Admins can now turn on the new navigation for their team.

Find out more about the new navigation

New interface for PDF export

We're introducing a new interface for exporting spaces as PDFs. This update streamlines the experience with a more intuitive interface without changing the output or permissions required for export.

Space admins can find the space name in the sidebar, select the more actions menu (three dots), and select Space Settings. Expand the Look and feel menu and select PDF export.

View reactions in email notifications

We're updating Confluence email notifications to display the actual emoji reaction a user has made to content or comments. This will only include standard emojis and not custom ones.

What's new:

• Display of reactions in emails: See the actual emoji reaction in email notifications.
• Improved clarity: Know exactly what emoji a user reacted with.

The Rovo button gives instant access to AI features in Confluence

The Rovo button is now available in Confluence. You can think of it as a front door to all your AI-powered actions. The button, displaying the Rovo icon, will float at the bottom right of your screen.

When the Rovo button is open, you can use the input field to enter a prompt and start a chat, or you can use it to search for available actions.

To start using the Rovo button in Confluence:

1. Open a Confluence Page, Live Doc, or Whiteboard.
2. Look for the Rovo button, it should be floating in the bottom right of your screen.
3. Select the button to explore available AI actions and tools.

Create work items using AI

You can now create work items using AI when Atlassian Intelligence is enabled for Jira or Confluence for your organization. The Jira and Confluence products must be on the same site.

Previously, you could only create work items using AI when Atlassian Intelligence was enabled for Confluence.

Automation rules triggered by old incoming webhooks are now marked with warning icons for visibility

We’ve added a new feature to Atlassian Automation to help you easily identify rules that were recently triggered through a legacy incoming webhook. Now, when you open the rule list in Jira or Confluence Automation, warning icons will appear next to rules that are triggered through a legacy incoming webhook endpoint. For these rules to continue working after 30 May 2025, you’ll need to make updates in the connected applications which trigger them.

Please note - the warning icon will continue to be shown 14 days after the rule was last triggered through the legacy endpoint, even if you have updated your connected applications to use the new endpoint. The icon will disappear once 14 days has passed without the rule being triggered through the legacy webhook. You can confirm when your rule was last triggered by viewing the ‘latest call’ timestamp next to the legacy URL.

If you have already made updates in your connected application to use the new endpoint, but there are still requests coming through the legacy endpoint, this may indicate there’s more than one application using the webhook trigger in the same rule. You can confirm if this is has happened by looking at the ‘latest call’ timestamp next to both the legacy and new URLs. In this case, find all the applications connected to your rule and replace the URL and secret in all of them.

To get started with this feature:

1. Open the automation rule list in Jira or Confluence.
2. Click on the ‘Trigger' filter and select the ‘Incoming webhook’ filter. All rules triggered by an incoming webhook will be shown. These rules need to be updated before 30 May 2025.
3. Within these filtered rules, any which have recently been triggered through a legacy webhook will have a warning icon next to their name. This shows which rules are actively using the legacy URL. To learn how to update these rules, you can read our support documentation.

Improved visibility of Company Hub

Company Hub is moving to a new section in the new Confluence navigation. It's now accessed from the customizable sidebar in Confluence.

Hub admins will see the Company Hub in the sidebar and app switcher, even when it's not published. Users will only see it when your Company Hub is published.

Each of the new locations will also show your customized Company Hub name. Note that if you change the name, it may take a few hours for all users to see the new name.

Get notified about your first page view

You will now get an in-app notification when a page you created is viewed for the first time.

Bulk connecting Rovo connectors

We've made it easier to see and connect to all the connectors that are available to Rovo users, so you can get the most out of your Search.

To get started, select the connect banner in the top of quick find to see and connect all your available Rovo connectors.

Deprecating infrequently used macros

In 6 months on September 25, 2025, we will be removing some infrequently used macros from Confluence Cloud. To learn more about which macros are being removed, read our deprecation article, and look for macros whose “Status” column says “Will be removed from Confluence Cloud on September 25, 2025.” If you’d like to replace those macros with an alternative, you can use the Macro Usage feature of Confluence Administration to identify where they are being used.

A special look at refreshed and new experiences will be featured in-product

We're introducing a preview of some new and upgraded Confluence features that will vastly improve our user experience. Customers already enrolled in the beta programs for Live Docs or new content layout will see a large informative modal when they access Confluence showcasing these updates.

More filters in Rovo Search

Filters such as Confluence, Slack and Google Drive will now show in Quick find in Confluence and Atlassian Home as you start a search, making it easier to quickly filter to what you need.

New option added to the delay action in Atlassian Automation

We've added a new option to the delay action in automation rules. Now, when you add the delay action to your rule, you can either specify the exact amount of delay that you want to occur before your rule runs (such as 5 seconds) or select a random period for the delay to occur over (such as between 3 to 10 seconds). Previously, you could only select a specific amount of delay, so the randomised option provides you with more flexibility in choosing when and how your rule is executed.

Space owner ID is now available in API calls

We're introducing a new attribute returning the space owner ID to the public Get Spaces and Get Space APIs. This update provides developers with more detailed information about space ownership without affecting existing functionalities.

Live docs: Invisible cursor when opening

When you open a live doc in Confluence that already has content, the cursor will no longer automatically appear, and the editor won't be focused. This change helps you stay focused on the content without unnecessary distractions.

1. Open a live doc in Confluence that already contains content.
2. Notice that the cursor does not automatically appear, and the editor is not focused.
3. Click anywhere in the document to start editing.

Quickly copy links to audit log entries in automation

We've introduced a new feature which allows you to quickly copy the link to an automation audit log and share it with others. This feature is designed to improve communication and streamline your workflow, by making it easier to copy and share links to your audit log.

To get started with this change:

1. Navigate to Jira or Confluence Automation.
2. Open the audit log.
3. Find the audit log entry you'd like to copy a link to.
4. Hover your mouse next to the audit log ID. A copy link button will appear.
5. Click on this button.
6. The link is now copied to your clipboard!

A seamless way to animate card reels in Company Hub

The new autoscroll feature in Company Hub allows you to animate a continuous reel of cards. This feature enhances the visual appeal of your content by automatically scrolling through cards, making it easier to showcase multiple items without manual intervention.

To enable and use the autoscroll feature in Company Hub:

1. Navigate to the Company Hub.
2. Add a new Cards element (/cards) or edit and existing one.
3. Select the Styles tab and turn on the "Autoscroll" feature to start animating your card reels.

Recommendations to help you get started with Confluence

When you join a team already on Confluence, you'll see recommendations on what to do next in the bottom right corner to help you quickly onboard and get up to speed. These prompts will help you: create a space, create a page, and create a whiteboard.

That means it’s easier to know what to do first in Confluence so that you’re getting the most out of it. You can dismiss these recommendations anytime.

Reading related pages is getting easier

When you're done reading a page on Confluence, you'll now see a message that will direct to you another related page so you can keep reading valuable information from your team.

Introducing the freehand pen tool on Confluence Whiteboards

The new pen tool in Confluence Whiteboards lets you draw freely on your digital canvas, making it easier to express your ideas visually. You can now create, edit, and format drawings directly on your whiteboard.

To use the new pen tool:

1. Select the pen icon from the main toolbar.
2. Begin drawing by clicking and holding your mouse or stylus. Release to finish your line.

Improvements coming to Carousel

We've improved the look and feel of Carousel while adding additional configuration options.

You can now add up to 10 cards (an increase from three).

For pages, live docs, and Company Hub, we are adding new features such as autoplay, new layouts, colors, and scrolling options. You can also style your buttons and use a new media picker.

For Company Hub only, editors will be able to select two styles of corners for each frame.

To add a Carousel, type /carousel in the Confluence editor or Company Hub editor.

Add Live Docs to the founding admin onboarding experience

For those with access to Live Docs, we've made it possible to add this feature during Confluence account setup for founding admins. Anyone who creates a new instance of Confluence can now select Live Docs as an option alongside other existing features such as pages, whiteboards, and databases.

To add Live Docs to your Confluence setup:

1. Begin setting up a new Confluence instance as a founding admin.
2. Navigate to the feature selection screen during the setup process.
3. Select Live Docs along with any other desired features.

A new way to display banners on Confluence content

We're introducing a new extension point in Confluence called confluence:pageBanner. This feature allows you to display a banner at the top of Confluence content, except for Whiteboards, Embedded content, and Databases. This is part of our ongoing effort to expand extension points in both Jira and Confluence.

To start using the new page banner feature:

1. Use the Forge CLI to create an app with the confluence:pageBanner module.
2. Deploy and install your app to see the banner in action.

Create Jira work items in the Confluence editor and in Live Docs

You can now create Jira work items directly from highlighted text in the editor and in Live Docs. This feature allows you to seamlessly move actionable work into Jira without having to publish your Confluence page or navigating to Jira.

To create Jira work items in the Confluence editor or in Live Docs:

1. Highlight the text you want to convert into a Jira work item.
2. Select the … overflow menu in the contextual toolbar.
3. Choose Create Jira work item.

Improvements to presence on pages and live docs

We’re introducing some updates to telepointers on pages and live docs – specifically when users are editing.

1. We’ve deduplicated telepointers, so you will only ever see one telepointer for each user.
2. Telepointers now temporarily expand to show a user’s full name when you hover.
3. You can now find an editor's telepointer by clicking on their avatar in the header. You can only find a currently active editor’s telepointer, not people who aren't currently editing.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Audio briefing: Listen to an AI overview of a page or live doc and its links

In just a few minutes you can catch up on long, detailed pages and live docs by listening to a briefing by Rovo.

• Look for the headphone icon on a Confluence page or live doc.

• Customize your experience to make your Overview short or long, and change the tone to professional, conversational, or playful.

• Include the info from up to 9 links embedded in the page or doc.

• Add more links to other Confluence pages and docs for even richer results.

• Start a briefing with the play button.

Please note that this new feature is generated by AI and you should verify the results. It’s your own personal work podcast, just press play.

Select the headphones icon on a Confluence page or live doc and customize or choose the Play button to start.

A unified commenting experience across pages, live docs, whiteboards, and databases

We’ve introduced a unified comments panel across pages, live docs, whiteboards, and databases in Confluence. This provides a consistent experience that makes it easier for teams to collaborate and manage feedback, no matter where they work.

• Open a page, live doc, whiteboard, or database in Confluence.
• Select the comments icon on the action bar at the bottom right of the screen to open the new comments panel.
• Use the panel to view, reply, resolve, and manage comment threads.
• Comments are now visually aligned across all features.
• Navigate between comments using up/down arrows.
• Selecting a comment in the panel scrolls or zooms to its anchor in the content (paragraph, whiteboard area, or database cell).

Number fields now support three numerical options in databases

We are updating the definition of number fields to ensure greater consistency and clarity. With this change, number fields will now strictly accept only numerical values. Any custom format number fields that include special characters (such as text or custom prefixes/suffixes) will be moved to text fields. This ensures that number fields are used exclusively for numerical data.

Number fields now support three formatting options: number, currency, or percentage. These can be selected when customizing a number field.

If your existing custom number field contains special characters or text, it will be converted to a text field to preserve your data.

Last updated filter option in Confluence Search

In Confluence search, you can now filter results based on the person who last updated the content.

Definitions are now available in Confluence comments

We've now made our definitions feature available within Confluence comments. Select an auto-highlighted acronym or word to look up a definition.

Confluence: Hover card visual update

We've revamped the hover cards in Confluence to provide a smoother and more visually appealing experience. This update prevents layout shifts and ensures that hover cards are not displayed for the content you're currently viewing.

To explore the new hover card design in Confluence:

1. Open relevant Confluence content.
2. Hover over a link to another page or user.
3. Experience the updated hover card design.

Confluence: Authenticate to view linked work items

You can now authenticate to view Jira work items directly on your Confluence content. This change makes it easier to access and manage your tasks without leaving Confluence.

To authenticate and view linked work items on Confluence:

1. Open the Confluence content where you want to view linked work items.
2. Locate the linked work items section.
3. Follow the prompt to authenticate your account.
4. Once authenticated, the linked work items will be displayed.

Recent Smart Links now findable in Quick Find

Now, when you use the Quick Find search bar, you'll see recently viewed items that include third-party search results from searchable Smart Links. This change helps you access more relevant content quickly. All our searchable SmartLinks are supported except for Figma, which will be coming soon.

To see the new Smartlink results in Quick Find:

1. Open Confluence and go to the home page.
2. Select the search bar.
3. Look for your recently viewed items, which now include Smartlink results.

A new way to access and create automations in Confluence

Use automations from the Rovo button in Confluence. Now everyone can see and interact with automation rules directly from the Rovo button panel, making it easier to manage and create automations in your space.

To find and use the new Automations feature in Confluence:

1. Open any content type where the Rovo button is present, such as pages, live docs, or whiteboards.
2. Select the Rovo button.
3. Select the Automations button to view all admin-created automation rules.
4. Space admins can select the Create automations button to access the automation rule builder.

Fix broken links after migrating from one cloud site to another

When migrating Jira Cloud or Confluence Cloud to a different site, some links between individual entities may break due to changes in the URL. This typically includes:

• Links to Jira work items that users have pasted as URLs in comments and descriptions.

• Links from other instances to the migrated site, such as links from Confluence pages to your Jira work items.

Previously, the only way to resolve broken links was to contact Atlassian Support, which wasn’t ideal for those who prefer to do it in their own time.

To address this, we’ve included cloud-to-cloud migrations in Link fixing available at admin.atlassian.com. You can now update all broken links in bulk, including local links within your migrated instance and remote links from other instances.

Learn more about fixing links after migration

To get started with link fixing:

1. Go to admin.atlassian.com, and select your organization.
2. Go to Settings > Link fixing.
3. Review the list of instances that were migrated and start updating links on each of them.

Enhanced automation filtering and search experience

We’re making it easier and faster for you to find what you need in Atlassian Automation.

Streamlined template filtering: You can now effortlessly filter templates by app and trigger, allowing you to quickly narrow down your options and find the perfect template for your needs.

Faster and more reliable search: Our enhanced search capability ensures that results are displayed more quickly and reliably, so you can spend less time searching and more time automating.

To find new template filters:

1. Open Automation from your Atlassian app.
2. Select the Templates tab.

The legacy Microsoft Teams connector has been deprecated in Atlassian Automation

As of today, all automation rules that use the legacy Office 365 connector webhook in the Send Microsoft Teams message action can no longer be saved or updated, until they are migrated to the new Microsoft Teams workflow.

To update your automation rules:

1. Go to your Teams channel and select … > Workflows > Post to a channel when a webhook request is received.
2. Copy the new webhook URL.
3. Paste this URL into the Send Microsoft Teams message action in your automation rule.
4. Save your rule.

New suggestions in search box

We're introducing some new personalised and smart suggestions when you open the search box, but before you begin to type. These will more easily help you find information relevant to you.

Confluence lovability survey

We'd love to get user feedback via a contextual survey asking their opinion on Confluence lovability. You may be part of a group of users who have the change to rate Confluence.

If selected, you will see this message when you view a page:

• To what extent do you agree or disagree with the following statement?
  • Confluence is a product I love using.
• You will then have a chance to answer in a range of 1 to 7.

Delete, copy and export rules directly from the automation rulebuilder

We're excited to announce a new feature in Atlassian Automation that enhances your workflow efficiency. You can now quickly copy, delete, and export rules while in the rulebuilder. Previously, you could only complete these actions from the rule list.

This update aims to streamline your rule management process by reducing the number of steps needed to perform these actions. Whether you're setting up new rules or maintaining existing ones, this feature will help you manage your rules more effectively.

Add web links to the top of your team profile

We've consolidated all your team's important links to the "Team links" section at the top of the profile. Now, you'll see connected Jira, Confluence, and Loom spaces alongside any links to external tools or important pages.

To add links to your profile:

1. Go to the team's profile page.
2. Find the "Team links" section at the top, and select the + button.
3. Paste in the link and change the display text if you want it to say something different.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Reconfigure automation rules with Create feature flag in LaunchDarkly Action by June 30, 2025

We are deprecating the “Create feature flag in LaunchDarkly” action in Atlassian Automation on June 30, 2025. As a result, the rules linked to LaunchDarkly and this action will cease to function as intended after this date. To prevent rule failures, all rules employing this action must be reconfigured on or before June 30, 2025. Please note that the reconfiguration can only be completed successfully if you have an account with LaunchDarkly.

More about the deprecation of the LaunchDarkly Action in Atlassian Automation.

To determine if your rules are affected by this update and reconfigure them:

1. Select Automation from project/global settings where you’re an administrator.
2. Select the Action filter, then select the Create feature flag in LaunchDarkly from the list of options
3. Open the rule and select the Action component of the rule
4. Switch to Send web request action to create a feature flag through LaunchDarkly's public API

Find content anywhere on your page with new improvements to Find and Replace

We've improved the Find and Replace feature, allowing you to search for content in more places, including statuses, dates, mentions, smart cards, and titles of expands. While you can now find content in these areas, replacing is not supported for them. We've also made color updates to provide better contrast.

Use third party secret providers in Bitbucket Pipelines

Bitbucket Pipelines is excited to introduce third-party secret integration. This powerful new feature allows you to seamlessly retrieve secrets directly from your preferred secret store. This functionality is now available for Bitbucket Cloud-based runners, and self-hosted runners.

To get started with this feature, you'll need to code your own middleware to let Bitbucket communicate with your third-party secret provider.

Then, you'll need to configure your Bitbucket pipelines to retrieve the appropriate secrets at runtime.

If your pipelines are using a self-hosted runner, you'll also need to point that runner to your middleware.

All of these steps are detailed in our help documentation.

ARM cloud runners in Pipelines

Note: This feature is only available to Standard and Premium Bitbucket Cloud customers.

Our release of Linux-based ARM runners in cloud allows you to build and deploy software for ARM-based systems with all the benefits of our fully managed CI/CD platform.

To use the new cloud ARM runners in your pipeline, make the following modifications to your bitbucket-pipelines.yml file:

• Set the ARM runtime in your pipeline’s YAML file, available as a global option or can be set as a step-level option. Declaring it as a global option will result in all steps in the file running on ARM.
• ARM builds require you to use an image that is ARM compatible, meaning you must explicitly declare an image for your build, and that image must support ARM.

See the help documentation for more details.

Code suggestions are here to help you and your team collaborate on code

Now you or a teammates can suggest a code change when commenting on a line of code in a pull request. The suggested change can then, if desired, be committed directly on the pull request.

Use variables in any part of your Pipelines .yaml

In the past, variables in Bitbucket Pipelines were scoped to only operate within script sections of a Pipelines workflow. This limited their usefulness and restricted users from being able to fully parameterize their workflows.

Today we are releasing an enhancement that will allow variables to be used within any section of a Pipelines .yaml file, and not just within scripts. This new capability will allow you to use variables to parameterize things like cache keys, artifact names, build images, and anything else you might need. For more detailed information, check out the Variables and secrets help document.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Set the Files changed tab as your default pull request view

Now you can set the Files changed tab as your default pull request view, so when you open a pull request, you are able to get right into the diff and continue to collaborate on your code. To set this as your default view, select the Settings cog button above the diff on the right side of any pull request. Once you have opened the Global diff view settings dialog, select the checkbox under the Pull request view heading to set the Files changed tab as your default view for pull requests.

Code suggestions are here to help you and your team collaborate on code

Now you or a teammates can suggest a code change when commenting on a line of code in a pull request. The suggested change can then, if desired, be committed directly on the pull request.

New Jira banner in Bitbucket

Bitbucket and Jira work better when you use them together. If you use Jira, you can see all of your tasks directly in Bitbucket. That means you can see more, prioritize better, do less tool hopping, and ultimately save time.

We've added a banner to the Bitbucket 'your work' page to show people how this integration can work.

The banner will only be shown to Workspace Admins who don't already have Jira. It will disappear once they add Jira, or when they dismiss it using the dots menu in the top right side of the banner.

Upgrade your Compass GitHub app to allow Compass to ingest pull request data

Accept the updated permissions for your Compass GitHub app to authorize Compass to enrich the PR data/insights we show you in Compass.

Upgrade your Compass GitHub app:

1. In GitHub, go to the organization settings for the organization that you've connected the Compass app to.
2. Select GitHub apps on the left sidebar.
3. Select the Review request link.
4. Enter your GitHub password.
5. Select Accept new permissions.

You're now on the latest version of the Compass GitHub app.

Add tags to alerts in Slack for better organization

If you're using the Slack integration with your alert management, you can now add tags to your alerts directly from Slack. This will help you organize, categorize, and filter your alerts based on specific criteria.

• To add tags to a new or an active alert, select the more actions menu (•••), then select Add tags.
• To add tags to a closed alert, select Add tags.

You can add multiple tags at once by separating them with commas.

Use AI-powered support chat on Atlassian support

We are excited to announce a new chat feature on our contact form. This feature uses Atlassian Intelligence on the contact form to streamline the inquiry process and provide real-time assistance.

For more details, visit our website Atlassian Support

To use AI chat in the contact form:

1. Go to support.atlassian.com/contact
2. Fill out the form, and let us know what you need and your URL.
3. Some users might see an AI chat feature (Tell us about your problem) that will help you out by suggesting solutions
4. You can opt out and continue with the traditional form submission if you prefer.

Data residency moves: Choose where to host your Opsgenie data

Opsgenie data residency gives you control over where your Opsgenie account data is hosted. We support data residency moves (moving data across locations) for all Standard, Premium, and Enterprise plans for Opsgenie.

To request a data residency move in Opsgenie, go to Settings > App settings > Data residency.

Learn more about data residency in Opsgenie

Use custom fields as filters in alert processing rules for Syncs

In alert processing rules, you can currently only apply conditions using predefined fields in the alert configuration. This limitation sometimes prevents you from using custom or user-defined fields from these tools as filters. With this new feature (previously available for different types of integrations), you can also use custom fields in Syncs, and Jira Service Management-Jira Software Cloud integrations as filter criteria when setting up your alert processing rules.

Removing ability to delete tables and columns from a schema

Starting April 30, 2025, we're removing the ability to delete tables and columns from a schema. This feature was meant to be a convenient way to maintain a data source's schema, but it hasn't worked as intended. Removing this feature will also help our teams deliver support for data residency faster. Read more about this change in our Community post.

If there are tables or columns that you don’t want to bring into Atlassian Analytics, you’ll need to alter the access of the database user you provide in your data source connection settings.

Support for past and future dates

When creating a chart or filtering your dashboard, you’re no longer limited to selecting just one date. The new date picker lets you select date ranges that include both past and future dates.

Search using Jira Query Language when adding work to a focus area

If a simple keyword search isn't returning the work items you need to add to a focus area, slide the JQL toggle and enter your Jira Query Language (JQL) query.

Find out more about JQL

Bulk connecting Rovo connectors

We've made it easier to see and connect to all the connectors that are available to Rovo users, so you can get the most out of your Search.

To get started, select the connect banner in the top of quick find to see and connect all your available Rovo connectors.

Keep your strategic priorities fresh by archiving focus areas that are no longer relevant

Archiving a focus area lets you remove an outdated investment or priority from the lists of current, active areas. Your views and data will be fresh and organized without losing the information and history that might be helpful later.

You can find archived focus areas on the Archived tab or by searching for them. An archived focus area can't be modified, but people with specific permission can restore it.

When you archive a focus area, you remove it from the following places:

• Tiles and activity on the For you page
• Lists and maps showing:
  • all focus areas
  • your focus areas
  • focus areas you follow
• Views
• Tiles and charts in the sub-focus areas tab
• Goals, Work, Positions tabs

Record and share Loom videos in the details of your focus area

In the About section of your focus area, you can quickly record a Loom video that digs deeper into the details and adds that personal touch. If you already recorded one, you can also include that link.

Loom videos can also be recorded when crafting an update that shares progress with your followers. Links to previously recorded Loom videos can be added there too.

Search for specific sub-focus areas

When looking for a focus area, you can target focus areas that are under a specific one in the hierarchy in the global search.

To try out this change:

1. Enter a search term in the global search of the Focus app, and press the Return/Enter key.
2. Select the Focus area under filter, and find the focus area whose sub-focus areas contain the search term.

Easily spot your company's top priorities with one focus area icon

All focus areas now share the same icon. We thought having different icons for each type would make things easier, but we got feedback that using words to communicate the type was more effective. If you hover over a focus area icon, you can see the name of the Type in the tooltip. If the focus areas are displayed in a table, you'll see a Type column and can filter by the focus area type.

New suggestions in search box

We're introducing some new personalised and smart suggestions when you open the search box, but before you begin to type. These will more easily help you find information relevant to you.

Navigation: App shortcuts migrated to platform component

App shortcuts in the sidebar now use a shared platform component, replacing previously product-specific implementations. There is no change to the user experience, but this update aims to streamline navigation across Atlassian products, improve app discoverability, and support future customization.

Expand all work items from sub-focus areas

When you are looking for work items that roll up to a focus area, you can drill down into the detailed information on the Work tab of that focus area. The table shows you the work items that were added to that focus area and all the work items in its sub-focus areas. Depending on the number of sub-focus areas and work items, you might need to expand several sections to see them all.

To make this easier, a toggle was added to the table's More actions (•••) menu to always expand the work items. This choice is made per focus area and requires that the Show work from sub-focus areas toggle is also turned on.